Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

translators.en.xhtml 7.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <title>Information for Translators - FSFE</title>
  5. </head>
  6. <body class="article" id="translators">
  7. <p id="category"><a href="/contribute/">Contribute</a></p>
  8. <h1>Translations</h1>
  9. <p id="introduction" class="p-summary">
  10. Free Software Foundation Europe is an international organisation.
  11. Our goal is to <strong>reach as many people as possible</strong>
  12. and include them in our activities to promote, help and support
  13. the Free Software movement. To achieve this, we want to make our
  14. published texts and website available in several languages.
  15. </p>
  16. <p>
  17. A major part of the translation effort applies to the web pages,
  18. especially the frequently updated pages like the <a href="/">front
  19. page</a>, the <a href="/news/">news page</a> and the <a
  20. href="/events/">events page</a>. But not only web pages have to be translated: <a
  21. href="/press/">Press releases</a>, <a
  22. href="/news/newsletter.html">newsletters</a>, <a
  23. href="/contribute/spreadtheword.html#promo-material">brochures and leaflets</a>
  24. and other texts also become more wide-spread with every additional
  25. language they are available in.
  26. </p>
  27. <p>
  28. This page gives you a rough overview of our translation processes. More detailed information how to contribute translations can be found on our <a href="https://wiki.fsfe.org/TechDocs/Mainpage/Translations">translators' wiki pages</a>.
  29. </p>
  30. <h2>Priorities</h2>
  31. <p>
  32. As FSFE is active in many different countries, texts are also
  33. often written in different languages. However, we generally use
  34. English as a starting point for sharing these texts with other
  35. parts of the organisation and for further translations.
  36. Therefore, we especially need help to
  37. </p>
  38. <ul>
  39. <li>translate from other languages <em>to</em> English,</li>
  40. <li>proofreading English texts written by non-native English
  41. speakers, and</li>
  42. <li>translating from English to other languages.</li>
  43. </ul>
  44. <p>
  45. Experience shows that the best translation results are achieved
  46. when people translate from a foreign language to their mother
  47. tongue. Having a good idea about <a href="/about/">what the
  48. FSFE is</a> and about <a href="/about/principles.html">our
  49. concepts and values</a> is a good idea before starting
  50. translating. To help you out with difficult words and phrases, we
  51. maintain a <a
  52. href="/contribute/translators/wordlist.html">wordlist in over 15
  53. languages</a> that you can rely on when facing technical
  54. terminology or just standard ways of expressing oneself when
  55. speaking on behalf of FSFE.
  56. </p>
  57. <h2>Coordination</h2>
  58. <p>
  59. Translations are generally coordinated on the <a
  60. href="https://lists.fsfe.org/mailman/listinfo/translators">translators
  61. mailing list</a>, and everyone wanting to contribute to
  62. translations efforts can subscribe to this list. It is also a place
  63. to seek help when in doubt or cooperating with other translators on
  64. larger projects. As we have material available in over 30
  65. languages already, the chance is that you will always find
  66. somebody in the organization willing to help you.
  67. </p>
  68. <p>
  69. Texts to be translated or proofread are sent to this list along
  70. with a reference to the desired languages. Whoever starts with a
  71. translation sends an answer to the list to avoid duplicate work.
  72. Finished translations are also sent to the list to allow others to
  73. proofread the translation and propose possible improvements. Both
  74. original texts and translations are usually sent around as plain
  75. text file attachments to minimize copy and paste efforts.
  76. </p>
  77. <p>
  78. Ideally, the translation team for a specific language has several
  79. members that relieve and support each other, so translations to
  80. a language would not depend on a single person.
  81. </p>
  82. <h2>Your contribution makes a difference!</h2>
  83. <p>
  84. Many of our translators are already active in other Free Software
  85. projects in addition to FSFE. Helping with translation efforts in
  86. the FSFE strengthens the Free Software community at large and gives
  87. people, no matter the language or nationality, a chance of learning
  88. more about Free Software.
  89. </p>
  90. <p>
  91. Translating and proofreading texts is a precious contribution to the work
  92. of the FSFE and an excellent chance to spontaneously take part in
  93. the activities of the FSFE without long-term obligations.
  94. </p>
  95. <h2 id="subpages">Navigation</h2>
  96. <ul>
  97. <li>
  98. <h3><a href="https://wiki.fsfe.org/TechDocs/Mainpage/Translations">Translating for web</a></h3>
  99. <p>
  100. How to translate <em>fsfe.org</em>, <em>freeyourandroid.org</em>, <em>pdfreaders.org</em>, and <em>drm.info</em>.
  101. </p>
  102. </li>
  103. <li>
  104. <h3><a
  105. href="/contribute/translators/wordlist.html">Wordlist</a></h3>
  106. <p>
  107. Words and expressions commonly used in the FSFE.
  108. </p>
  109. </li>
  110. <li>
  111. <h3><a
  112. href="https://lists.fsfe.org/mailman/listinfo/translators">Mailing
  113. list</a></h3>
  114. <p>
  115. Coordination and help on translation efforts.
  116. </p>
  117. </li>
  118. </ul>
  119. <h2>Translation Teams</h2>
  120. <p>
  121. If you require more information regarding our translation activities
  122. and do not feel confident in public, you are welcome to contact the
  123. translation coordinators. Information about the various language-specific teams can be found on the <a href="https://wiki.fsfe.org/Teams/Translators/">translators' wiki pages</a>.
  124. </p>
  125. <div id="team" class="section grid-100">
  126. <translation-coordinators-list />
  127. </div>
  128. </body>
  129. <sidebar promo="about-fsfe">
  130. <div id="related-content">
  131. <h3>Quick Links:</h3>
  132. <ul>
  133. <li>
  134. <a href="https://wiki.fsfe.org/TechDocs/Mainpage/Translations">How to translate</a> fsfe.org, freeyourandroid.org, pdfreaders.org, and drm.info
  135. </li>
  136. <li>
  137. <a href="https://status.fsfe.org/translations.html">Outdated translations</a> and other useful information for all languages.
  138. </li>
  139. <li>
  140. <a href="/contribute/translators/wordlist.html">Wordlists and expressions</a> commonly used in the FSFE.
  141. </li>
  142. <li>
  143. <a href="https://lists.fsfe.org/mailman/listinfo/translators">Mailing list</a> for coordination and help
  144. </li>
  145. <li>
  146. <a href="https://wiki.fsfe.org/Teams/Translators/">The translation teams</a> in our wiki
  147. </li>
  148. <li>
  149. <a href="https://fsfe.org/contribute/web/web.html">Information on webmastering</a> for translators who want to have a better understanding of our website system
  150. </li>
  151. </ul>
  152. </div>
  153. </sidebar>
  154. <timestamp>$Date$ $Author$</timestamp>
  155. </html>
  156. <!--
  157. Local Variables: ***
  158. mode: xml ***
  159. End: ***
  160. -->