Translation
|
Size: 6422
Comment: correction
|
Size: 4422
Comment: simplified
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| * poxml from kdesdk | * gnome-doc-utils |
| Line 15: | Line 15: |
| 0. When English XML document is ready for translation, make a POT file. With {{{pwd trunk/}}} do {{{make pot}}}. | 0. When English XML document is ready for translation, make a POT file. Use the command {{{xml2po --help}}}. |
| Line 17: | Line 17: |
| * Note: BREEZY BADGER (Ubuntu 5.10) is not yet in Rosetta: only hoary is there at the moment. | |
| Line 19: | Line 18: |
| 0. Automatic exporting from Rosetta into the docteam tree is not implemented, and it seems that it will be difficult to implement it in the future. Therefore a member of the docteam will check the status of translations in the documents and when they are ready, export them from Rosetta and commit them to the relevant section of the Docteam Repository. There are some scripts in the teamstuff/ directory that may be used to check (when passed with the -s flag) and download the relevant po files (when passed without), but as of yet they have not been modified to place the po files in the correct directory structure of our trunk repository. * ''Here's the tricky bit.'' * Given that not very many translations of our docs got into Hoary, and given that Rosetta is currently working on Hoary, we thought it would be nice if some translations of the Docteam work could make it into Hoary. This would require a fairly complicated bilateral regime: * HOARY: First of all, new translations for hoary cannot be committed to TRUNK, given that this is already in Breezy mode. Rather, they will be committed to the TAGGED release. Then the xml files can be created using the {{{make po}}} script, and a new package built and uploaded. Note: we need to get permission for uploads of this type. * Update on permission: I have now spoken to MattZimmerman today about the possibility of uploading ubuntu-doc updates to hoary with added translations: he was positive about the idea, and on a side note mentioned that in the end it might be desirable to add translated documentation to language packs. * BREEZY: We will be continuing to work on Breezy documents, and these will be uploaded to Rosetta and translated in the manner described above. However it is also useful if we can avoid translators having to work on things which have already been translated for Hoary (given that some parts of the documentation will remain the same). This will require merging .po files in the hoary/tag branch into the current trunk. |
0. Automatic exporting from Rosetta into the docteam tree is not implemented, and it seems that it will be difficult to implement it in the future. Therefore a member of the docteam will check the status of translations in the documents and when they are ready, export them from Rosetta and commit them to the relevant section of the Docteam Repository. |
| Line 57: | Line 51: |
| * Script "make-po" does not check XML markup (Valid and Well-formed). If nn.po contains errors, the nn.xml will contain errors. Fix nn.po file not nn.xml. Then do {{{make po}}} and check nn.xml with {{{./validate}}} |
Introduction
This page is a description of how the Documentation Team work gets translated and inserted into Ubuntu. It is primarily intended for reference of the Documentation Team: translators do not need to know all this information.
If you are a translator, and are interested in helping out translating the Ubuntu documentation into your language, all you need to know is how to use the [http://launchpad.ubuntu.com/rosetta Rosetta translation system]. You can find out how to use that on the ["Rosetta"] wiki page. Once you have learnt all of this, the docteam documents can be found [https://launchpad.ubuntu.com/distros/ubuntu/hoary/+sources/ubuntu-docs/+translations here] (don't forget to login).
Package Requirements
- gnome-doc-utils
- gettext
Process
When English XML document is ready for translation, make a POT file. Use the command xml2po --help.
Pot files in the source debs uploaded to the hoary archives are automatically imported into [http://launchpad.ubuntu.com/rosetta Rosetta]. The exception to this is where there are more than one .pot file in a directory, in which case automatic upload is not yet implemented.
Documents are translated via the [http://launchpad.ubuntu.com/rosetta Rosetta] interface.
- Automatic exporting from Rosetta into the docteam tree is not implemented, and it seems that it will be difficult to implement it in the future. Therefore a member of the docteam will check the status of translations in the documents and when they are ready, export them from Rosetta and commit them to the relevant section of the Docteam Repository.
File Naming Convention
- English document names may contain one hyphen. Example:
- Correct "xxx-xxx.xml" "release-notes.xml
- Incorrect "xxx-xxx-xxx.xml"
- POT file name is same as English filename but with .pot extension. Example:
- Correct "xxx-xxx.pot" "release-notes.pot"
- Incorrect "xxx-xxx-xxx.pot"
- PO file name must be in the following format
- Correct "nn.po" (where nn = two letter country code) e.g. "fr.po"
- Incorrect "xxxxxx-nn.pot"
Note::
See ISO 639: 2-letter codes at [http://www.w3.org/WAI/ER/IG/ert/iso639.htm]
Problems
Some of the following problems may be encountered while using Rosetta as a translating interface. We are hoping that Rosetta will be a suitable way of getting Docteam documentation translated by the maximum number of people, but it is normal that we will have some teething problems, which may be solved by amending our make pot / make po scripts or by filing bugs with the Rosetta guys. If you come across an error which isn't listed here, please list it here and report it to the [mailto:ubuntu-doc@lists.ubuntu.com Docteam] and [mailto:rosetta-users@lists.ubuntu.com Rosetta-users] lists.
- PO file may contain syntax errors. These are shown when running make-po script. For example:
msgfmt: releasenotes/release-notes-fr.po: some header fields still have the initial default value
msgfmt: releasenotes/release-notes-fr.po: warning: PO file header fuzzy
warning: older versions of msgfmt will give an error on this
msgfmt: found 1 fatal error
124 translated messages.- In this case:
- Check that the header has been modified. Sometimes people forget to complete the "Last-Translator" field.
- Strip the line #, fuzzy from the file.
- Locate and resolve any fatal message string errors.
Languages such as German have special characters such as ü and ß. Instead of using the "Entity" use the "Decimal." For example: replace ß with ß. Use [http://zvon.org/other/charSearch/PHP/search.php] to resolve an "Entity" to a "Decimal."
How to check a translation when another language is installed
sudo dpkg-reconfigure locales
Choose the locale of your choice. Then :
LANG=<locale> yelp ghelp:about-ubuntu
Replace about-ubuntu by either document of your choice.
Todo
Translation of screenshots - The current method that we have for doing this is to install the relevant language packs and to take the screenshots manually (see TakingScreenshots). This is obviously not the easiest way, so any suggestions are welcome. Thanks!
DocumentationTeam/Translation (last edited 2014-07-02 21:01:40 by belkinsa)