Changes between Version 5 and Version 6 of OSGeoLive_Translation_Process
- Timestamp:
- 20 Dec 2017, 14:04:37 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OSGeoLive_Translation_Process
v5 v6 43 43 <li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li> 44 44 <li>Translator works with those strings using the process bellow.</li> 45 <li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li> 45 <li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</ 46 li> 46 47 <li><p>Users can create their translation using:</p> 47 48 <p>tools/transifex/create_translation.sh fr</p></li></ul> … … 68 69 }}} 69 70 71 70 72 == Downloading translation == 71 73 … … 108 110 The French documentation would be in 109 111 110 {{ 111 {build/doc/html/fr/doc/index.html112 {{{ 113 build/doc/html/fr/doc/index.html 112 114 }}} 113 115 114 116 == Transifex files that are not accepting translations. == 115 117 116 Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused. 118 Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system s 119 o any translated string can be reused. 117 120 118 121 == English spelling and grammar == 119 122 120 Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the "instructions" for the string. 123 Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the transla 124 tion with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the En 125 glish string. If a change has been considered, the string to be translated will be posted on the "instructions" for the string. 121 126 122 127 = Working with small strings = … … 124 129 == Choose the small files first. == 125 130 126 For "small" I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a "small" file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings. 131 For "small" I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a "small" file go to the list o 132 f [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings. 127 133 128 134 == Use "translate" button == 129 135 130 The "translate button" comes quite handy, you still have to check the translation, and there is an "undo" button if you think that its better for you to type the translation than to modify the machine's translation. 136 The "translate button" comes quite handy, you still have to check the translation, and there is an "undo" button if you think that its better for you to type the translation than to modify the machine's tr 137 anslation. 131 138 132 139 Don't use "translate" button on stand alone references like … … 136 143 ja: :ref:`サンプル` <--- wrong 137 144 }}} 138 139 == Use a "suggestion" == 140 141 When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example: 142 143 {{{en: :ref:`pgr_astar<pgr_astar>` - Shortest Path A* 145 == Use a "suggestion" == 146 147 When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of th 148 e string. Example: 149 150 {{{ 151 en: :ref:`pgr_astar<pgr_astar>` - Shortest Path A* 144 152 Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索 145 Modify to: :ref:`pgr_astar<pgr_astar>` - A*アルゴリズムを用いた最短経路探索}}} 146 == Use "copy button" == 153 Modify to: :ref:`pgr_astar<pgr_astar>` - A*アルゴリズムを用いた最短経路探索 154 }}} 155 == Use "copy button" == 147 156 148 157 Copy the the stand alone references like … … 152 161 ja: :ref:`sample` 153 162 }}} 154 155 163 == Type a translation == 156 164 … … 274 282 html: 上記クエリは Sample Data のネットワークを使用しています。 275 283 }}} 276 277 284 Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok. 278 285 … … 286 293 html: The queries use the サンプルデータ network. 287 294 }}} 288 289 295 Maybe you navigated into an untranslated page that has a reference to a translated page. 290 296 … … 299 305 html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 300 306 }}} 301 302 307 The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version: 303 308 … … 306 311 ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 307 312 html: 上記クエリは サンプルデータ のネットワークを使用しています。 308 or: 上記クエリは Sample Data のネットワークを使用しています。}}} 313 or: 上記クエリは Sample Data のネットワークを使用しています。 314 }}} 309 315 310 316 == WARNING: Inline literal start-string without end-string. == 311 317 312 You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1. 318 You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in li 319 ne 1. 313 320 314 321 Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in: … … 320 327 ``int4`` 型の始点ノードのID <--- a space is (before as a new line and) after the inline literal 321 328 }}} 322 323 329 = Tools for the Reviewer = 324 330 … … 340 346 tools/transifex/download_translation.sh 341 347 }}} 348 342 349 To download all the translations of a particular language: 343 350 … … 345 352 tools/transifex/download_translation.sh [es|ja|fr|de] 346 353 }}} 354 347 355 To download the translation of a specific file you need to state the language also 348 356 … … 362 370 To create the documentation of all the languages 363 371 364 {{{tools/transifex/create_translations.sh}}} 372 {{{ 373 tools/transifex/create_translations.sh 374 }}} 365 375 To create the documentation of a particular language: 366 376 367 {{{tools/transifex/create_translations.sh [es|ja|fr|de]}}} 377 {{{ 378 tools/transifex/create_translations.sh [es|ja|fr|de] 379 }}} 368 380 The main index.html of the documentation will be located at: 369 381 370 {{{build/doc/html/[es|ja|fr|de]/doc/index.html}}} 382 {{{ 383 build/doc/html/[es|ja|fr|de]/doc/index.html 384 }}} 371 385 372 386 = Main wiki page = 373 387 374 * [https://trac.osgeo.org/osgeolive/wiki/WikiStart] 375 376 377 [[Category: OSGeoLive]] 388 * [https://trac.osgeo.org/osgeolive/wiki OSGeoLive wiki]
