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.
 
 
 
 
 
 

187 lines
6.9 KiB

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