Difference between revisions of "Become a Translator/9.2"

From PC-BSD Wiki
Jump to: navigation, search
m (Replaced content with "{{NavHeader|back=Become a Beta Tester|forward=Become a Developer}} ==Localizing PC-BSD== {{:localizing PC-BSD}} ==Handbook Translating== {{:handbook translating}}")
Line 1: Line 1:
 
{{NavHeader|back=Become a Beta Tester|forward=Become a Developer}}
 
{{NavHeader|back=Become a Beta Tester|forward=Become a Developer}}
PC-BSD uses [http://en.wikipedia.org/wiki/Pootle Pootle] for managing localization of the menu screens used by the installer and the PC-BSD utilities. Pootle makes it possible to find out if your native language has been fully localized for PC-BSD. Pootle also makes it easy for users to check and submit translated text as it provides a web editor and commenting system. This means that translators can spend their time making and reviewing translations rather than learning how to use a translation tool.
+
==Localizing PC-BSD==
 
+
{{:localizing PC-BSD}}
To see the status of a localization, open up the [http://pootle.pcbsd.org/ PCBSD Translation System] in your browser, as seen in Figure 9.2a:
+
==Handbook Translating==
 
+
{{:handbook translating}}
'''Figure 9.2a: The PC-BSD Pootle Translation System'''
+
 
+
[[Image:Pootle1.png]]
+
 
+
The localizations PC-BSD users have requested are listed alphabetically on the left. If your language is missing and you would like to help in its translation, send an email to the [http://lists.pcbsd.org/mailman/listinfo/translations translations mailing list] so it can be added.
+
 
+
The green bar in the Overall Completion column indicates the percentage of PC-BSD menus that have been localized. If a language is not at 100%, it means that the menus that currently aren't translated will appear in English instead of in that language.
+
 
+
If you click on a language name then click on the pcbsd hyperlink under the "Name" column, you'll see each menu item that is available for translation. The example shown in Figure 9.2b is for the Greek localization:
+
 
+
'''Figure 9.2b: Viewing a Language's Available Menus'''
+
 
+
[[Image:Pootle2.png]]
+
 
+
In this example, the menu for CrashHandler is complete, but the one for LifePreserver is not.
+
 
+
If you click on the Review tab, you'll see a list of statistics as seen in Figure 9.2c. This page will indicate the results of Pootle's quality checks, helping translators to notice any problematic items. A description of each quality check can be found [http://translate.sourceforge.net/wiki/toolkit/pofilter_tests here].
+
 
+
'''Figure 9.2c: Reviewing a Language's Quality Checks'''
+
 
+
[[Image:Pootle3a.png]]
+
 
+
If you wish to help localize your language, you should first join the [http://lists.pcbsd.org/mailman/listinfo/translations translations mailing list] and introduce yourself and which language(s) you can assist with. This will allow you to meet other volunteers as well as keep abreast of any notices or updates that may affect the translations. You will also need to create a Pootle login account.
+
 
+
Once you are logged in to Pootle, navigate to the menu item that you wish to translate. Figure 9.2d continues the earlier example by clicking on the link for the Greek version of LifePreserver.po.
+
 
+
'''Figure 9.2d: Using the Pootle Interface to Edit a Translation String'''
+
 
+
[[Image:Pootle4.png]]
+
 
+
In this example, the first string (the word Disabled) has been translated but is failing 2 of the quality checks. The translator can check the correctness of the translation as well as fix the whitespace and double-spacing issue. Once finished, the translator can click the "Add Comment" link to type in an optional comment then press the "Submit" button to save any changes. Each text field (string) in the menu is numbered--click on the hyperlink associated with the number to open that text field in the Pootle editor, or use the Next and Previous links to navigate between text fields.
+
 
+
If you need help with a translation or using the Pootle system, you can ask for help on the translations mailing list or in the [http://forums.pcbsd.org/forumdisplay.php?f=19 PC-BSD Translations Forum].
+

Revision as of 14:39, 30 June 2011

(Sorry for the inconvenience)

Contents

Localizing PC-BSD

Localizing PC-BSD

Handbook Translating

<translate>

Template:Word-note This page may be incomplete. Further instructions may be added to this page or linked from here to an entirely new page as needed.

Anyone is welcome to help with translating the handbook into other languages. MediaWiki can now be used for the translation work of version 9.2 and may be the method used in the future, although the old method could still be used but at a cost of delayed access. The mediawiki method may be the quickest to make available to the public.

Mediawiki

The task should be as simple as choosing through the mediawiki link "translate this page" and selecting the desired language. Then use the mediawiki mechanism to do your work.

  • leave the UseTOC line as is (paste source text and "save translation" for that line) if there is no "title=translate what is here" portion.
  • It may be considered the most important step, to localize all of the page titles for those pages listed in the Table of Contents of the PC-BSD®_Users_Handbook because that section will automagically "import" those translated page titles.
  • Page links that use template:local such as {{local|link=handbook translating}} will appear as localized links if their page title has been translated, and more complex links also work, such as {{local|static=Warden®/{{release}}|anchor=Using Template Manager|Template Manager}} are displayed as Template Manager.
  • Application names should not be translated (AppCafe, LifePreserver, etc)
NOTE: Although no explanation may be given, if a page previously marked to be translated (especially the templates for "word-.." or "phrase-.." which are used by the Navigation and other templates) gets marked as discouraged on the Special:PageTranslation page let someone know that you wish to be able to translate it.

Earlier methods

Since at that time we were not able to get MediaWiki to provide a working translation plugin, and other structures (templates) were not yet in place, below is how our translation process had worked.

Handbook v9.1

  • Documentation in the wiki gets "frozen" a few weeks before release so that they can be translated.
  • The text (in odt format) is sent to the translations mailing list and emailed back when it is finished.

An expected "Freeze" date depends on the results of FreeBSD's RC process.

Some teams may use Google Docs™ or other sharing mechanisms to work on the translation, other teams might have only one person or divide up who does which sections. Use the method that works best or makes the task easiest.

Older versions (9.0 and 8.2)

For those who desire to translate them, we welcome your contributions and ask that you notify us so that we can help make them available. Additional formats including HTML, ODF (for OpenOffice and other software), EPUB (for e-readers), and PDF formats are available as downloads from the PC-BSD® ftp server. Translations of the Handbook are added to the ftp server as they become available, its file name indicating the language with a 2-letter ISO code.

</translate>

Other languages:German 60% • ‎English 100% • ‎French 24%