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.

web.en.xhtml 9.3KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  1. <?xml version="1.0" encoding="utf-8" ?>
  2. <html>
  3. <head>
  4. <title>
  5. FSFE - Contribute - Information for translators - Web pages
  6. </title>
  7. <style type="text/css">
  8. .clear {
  9. clear: both;
  10. }
  11. </style>
  12. </head>
  13. <body>
  14. <h1>Translating web pages</h1>
  15. <h2>Short Step by Step Guide</h2>
  16. <p>
  17. This little guide should only be used if you already know the
  18. background of translations: How our pages are generated, how to find
  19. out which translations are missing or outdated and so on.
  20. </p>
  21. <p>
  22. In this example, we want to translate
  23. https://fsfe.org/contribute/spreadtheword.en.html into Spanish. Please
  24. click the images to enlarge the pictures.
  25. </p>
  26. <ol>
  27. <li>
  28. <div style="max-width: 100px; width: 100px" class="captioned left">
  29. <a href="/graphics/translators-shortguide1.png"><img width="100%" alt="Find the source code" src="/graphics/translators-shortguide1.png" /></a>
  30. </div>
  31. Scroll down the page which you want to translate and find "Source code"
  32. in the footer.
  33. </li>
  34. <p><br class="clear" /></p>
  35. <li>
  36. Download the .xhtml file with "Save As..." in your browser or other
  37. tools (in this case
  38. https://fsfe.org/source/contribute/spreadtheword.en.xhtml).
  39. </li>
  40. <li>
  41. <div style="max-width: 100px; width: 100px" class="captioned left">
  42. <a href="/graphics/translators-shortguide3.png"><img width="100%" alt="Write an email to the translators list" src="/graphics/translators-shortguide3.png" /></a>
  43. </div>
  44. Write a short e-mail to translators@fsfeurope.org (you should already
  45. be subscriber of this mailing list) and tell them that you start with
  46. the translation.<br />
  47. Please open for each new page a new thread and add your <a
  48. href="https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">two letter
  49. Language Code</a> in the subject.
  50. </li>
  51. <p><br class="clear" /></p>
  52. <li>
  53. Open the downloaded file with a text editor (gedit, Kate, Mousepad etc
  54. on Free operating systems, Notepad++ on Windows).
  55. </li>
  56. <li>
  57. <div style="max-width: 100px; width: 100px" class="captioned left">
  58. <a href="/graphics/translators-shortguide5.png"><img width="100%" alt="Translate text to your language" src="/graphics/translators-shortguide5.png" /></a>
  59. </div>
  60. Translate all english text outside the HTML tags into your language.
  61. For example:<br />
  62. <em>&lt;p&gt;&lt;a href="/contribute/"&gt;Contribute&lt;/a&gt;&lt;/p&gt;</em>
  63. should become<br />
  64. <em>&lt;p&gt;&lt;a href="/contribute/"&gt;Colabore&lt;/a&gt;&lt;/p&gt;</em><br />
  65. Please change the <a
  66. href="https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">two letter
  67. Language Code</a> of the translated file from "en" to the one of your
  68. language (for example Spanish = "spreadtheword.es.xhtml").
  69. </li>
  70. <p><br class="clear" /></p>
  71. <li>
  72. <div style="max-width: 100px; width: 100px" class="captioned left">
  73. <a href="/graphics/translators-shortguide6.png"><img width="100%" alt="Send file and ask for proofreading" src="/graphics/translators-shortguide6.png" /></a>
  74. </div>
  75. Afterwards, please reply to your thread in translators@fsfeurope.org
  76. and ask other people to proofread your file. If everybody agrees, it
  77. will be uploaded by others on the mailing list.
  78. </li>
  79. <p><br class="clear" /></p>
  80. </ol>
  81. <h2>Detailed guide: Understanding how the web pages are built</h2>
  82. <p>
  83. The web pages of fsfe.org are maintained as a set of XML files.
  84. The web server generates the HTML pages from these XML files
  85. automatically every ten minutes. Consequently, all editing of the pages is
  86. done in the XML files, and the HTML is never edited directly.
  87. </p>
  88. <p>
  89. Every page on fsfe.org is named
  90. <var><em>pagename</em>.<em>language</em>.html</var> (<em>language</em>
  91. being the <a
  92. href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">two-letter
  93. ISO-639-1 code</a> of the language, like "en" for English or "de" for
  94. German). The source files are named
  95. <var><em>pagename</em>.<em>language</em>.xhtml</var>.
  96. </p>
  97. <p>
  98. Some pages have a dynamic part. Apart from the fixed texts taken from the
  99. XHTML file, they include information from one or several XML files.
  100. Whenever such a page is built, the build system takes the translated XML
  101. files where available, and falls back to the English version of those
  102. XML files that have not yet been translated. This way, such pages
  103. can end up with parts of the text being translated and other parts still
  104. showing in English. Examples of such pages include the
  105. <a href="/index.html">start page</a>, the
  106. <a href="/news/news.html">news page</a>, and the
  107. <a href="/events/events.html">events page</a>.
  108. </p>
  109. <h2>Everybody can contribute translations</h2>
  110. <p>
  111. All source files (i.e. all XHTML and XML files) are publicly available
  112. for download, so everybody can spontaneously contribute a translation
  113. without having to register anywhere. However, whenever you start a
  114. translation and expect it to take longer, please write a short note to
  115. the <a href="https://lists.fsfe.org/mailman/listinfo/translators">Translators
  116. mailing list</a> to avoid that somebody else starts to work on the same
  117. text simultaneously.
  118. </p>
  119. <h3>Contributing missing translations</h3>
  120. <p>
  121. If you have a page open in your web browser that has not yet been
  122. translated to your language, scroll to the end of the page, click on the
  123. <strong>Source code</strong> link and save the file you get there. You will
  124. get the English XHTML file. Rename the file to carry your language code
  125. instead of the "en" code, and open it in a text editor. Now, translate
  126. all text in the file that is outside the "&lt;…&gt;" marks; do not
  127. change anything inside these marks (the text inside the marks are XHTML
  128. commands that influence the structure of the resulting web page).
  129. </p>
  130. <!--
  131. Note to translators for the above sentence:
  132. _structure_ not _appearance_. XHTML = structure, CSS = appearance.
  133. -->
  134. <p>
  135. At the end of the file there will be a line saying <var>&lt;/html&gt;</var>.
  136. Immediately <em>above</em> this line, add a line saying
  137. <var>&lt;translator&gt;<em>your name</em>&lt;/translator&gt;</var>.
  138. </p>
  139. <p>
  140. When you are done, send the translated file to the
  141. <a href="https://lists.fsfe.org/mailman/listinfo/translators">Translators
  142. mailing list</a>. Other members of this list can proofread the
  143. translation, and somebody on that list will ultimately post it to the
  144. server.
  145. </p>
  146. <h3>Updating outdated translations</h3>
  147. <p>
  148. If you have a page open in your web browser of which the translation is
  149. outdated (indicated by a note at the top of the page), scroll to the end
  150. of the page, click on the <strong>Source code</strong> link and save the file
  151. you get there. This file is the (outdated) translated version. Next, use
  152. the <strong>English</strong> link at the top of the page to jump to the
  153. English version of the page and click on the <strong>Source code</strong>
  154. link there, too. The file you get there is the (up to date) English
  155. version. Now you can compare both files and update the translation.
  156. Please notice that everything inside the "&lt;…&gt;" marks may not
  157. be translated.
  158. </p>
  159. <p>
  160. Alternatively, you may also use <a
  161. href="https://trac.fsfe.org/fsfe-web/browser/trunk">the web-based source
  162. repository</a> on the <a href="https://trac.fsfe.org/fsfe-web">fsfe-web
  163. trac site</a> to create diffs, and to see the latest updates for all
  164. source files.
  165. </p>
  166. <p>
  167. When you are done, send the translated file to the
  168. <a href="https://lists.fsfe.org/mailman/listinfo/translators">Translators
  169. mailing list</a>. Other members of this list can proofread the
  170. translation, and somebody on that list will ultimately post it to the
  171. server.
  172. </p>
  173. <h3>Finding out what needs work</h3>
  174. <p>
  175. There is an
  176. <a href="http://status.fsfe.org/web/translations.html">autogenerated
  177. list of all languages</a> available. On that page, each language code
  178. is a link to a separate page that lists all outdated and missing
  179. translations for that language.
  180. </p>
  181. <p>
  182. The list of outdated translations provides an extra feature helpful for
  183. updating: you can not only downlad the (outdated) translated file and the
  184. (up to date) English original; you can also view the changelog of both
  185. files, a protocol of all modifications done to the respective file.
  186. Comparing the two changelogs usually makes it easy to find out which
  187. parts of the original were altered since the translation was last
  188. updated.
  189. </p>
  190. <p>
  191. This translation status page is also the only way to download the XML
  192. files that are built into the dynamic pages, like files containing news
  193. items or event entries.
  194. </p>
  195. <h3>Downloading the complete source file tree with subversion</h3>
  196. <p>
  197. If it is possible for you to use subversion, you can also download the complete
  198. source file tree at once. Please see the <a
  199. href="/contribute/web/web.html">FSFE webmaster information page</a> for
  200. detailed instructions.
  201. </p>
  202. </body>
  203. <timestamp>$Date$ $Author$</timestamp>
  204. </html>
  205. <!--
  206. Local Variables: ***
  207. mode: xml ***
  208. End: ***
  209. -->