Changes between Version 14 and Version 15 of i18n/UserGuide

Sep 10, 2019, 5:40:44 PM (21 months ago)

fix in-page anchors


  • i18n/UserGuide

    v14 v15  
    1212* [#quicktour Quick Tour localization]
    14 = [#help Help with translations] =
     14= [=#help Help with translations] =
    1616If you have a good grasp of the English language and enough knowledge of HTML to recognize what's a tag (<i>,<b> etc.) and what's translatable contents, here is how to get involved:
    2020Subscribe to the [ localisation mailing list] ([ message archive]) and the language-specific [ haiku-i18n-*] discussion list and introduce yourself. The respective "Language Manager" will provide you with login information for the online translation tool after your application has been discussed/voted on by the other volunteers. You may have to do a few sample block translations handed to you by your Language Manager.
    22 = [#startNew Starting a new translation] =
     22= [=#startNew Starting a new translation] =
    2424If you would like to start a completely new translation, follow these steps:
    3232 4. When the above is done, announce it on the i18n mailing list and the Language Manager receives his account after providing his desired username and email address. He can then create more accounts for "his" translators on-site. Passwords are generated automatically and send via email (check your spam folder!).
    34 = [#onlineTool The online translation tool] =
    35 == [#statusPage The status page] ==
     34= [=#onlineTool The online translation tool] =
     35== [=#statusPage The status page] ==
    3636Thanks to a very nice online tool originally written by Vincent Duvert and improved upon since, the translating process is easy as can be. Starting point is the page with the [ current translation status] of all documents.
    4848You can sort the columns by clicking on its heading, allowing you to quickly show all unfinished pages at the top.
    50 == [#translatePage Translating a page] ==
     50== [=#translatePage Translating a page] ==
    5151Clicking "Translate" will open the document for translation:
    6060||yellow:||"fuzzy", review needed - either the English original has been changed or a translator has set the block as incomplete.||
    62 == [#translateBlock Translating a block] ==
     62== [=#translateBlock Translating a block] ==
    6363If you click a block, the translation panel opens:
    7474This "fuzzy" flag indicates that a translation for a particular block may be imprecise or unfinished, and needs review. When a part of the original English document changes, translations associated to this part are automatically marked as fuzzy, so the translators can easily spot what needs to be updated.
    76 == [#localizeImage Localizing images] ==
     76== [=#localizeImage Localizing images] ==
    7878Images of the GUI which contain strings that are translatable and change when you switch to another language with the Locale preferences, can be "translated" by uploading a localized version. Simply click on it and a window pops open to choose the image to transfer to the online tool.
    8585- all background pixels are transparent (Haiku's Screenshot already does that for the area beside the yellow tab, but you may have to edit/compose in WonderBrush. Tip: In WonderBrush, use the ''Fill'' or ''Rectangle'' tool and set in its ''Properties'' the ''Mode'' to ''Erase''.)
    87 = [#quicktour Quick Tour localization] =
     87= [=#quicktour Quick Tour localization] =
    8888The Quick Tour is a bit of a special case. Each topic should be short enough to fit on one page in the browser, so we try to keep the text short and the accompanying screenshort small and significant. Keep that in mind when translating and take special care when "re-screenshooting":
    8989* Use Haiku's default GUI settings in the Appearance preferences, but use a font size of 10.