Changes between Version 3 and Version 4 of TranslateIntro


Ignore:
Timestamp:
Jul 4, 2007, 9:56:23 AM (17 years ago)
Author:
Nicolas
Comment:

Changed CVS to SVN; changed links to files to use source:

Legend:

Unmodified
Added
Removed
Modified

  • TranslateIntro

    v3 v4  
    1313
    1414    * Email the translation manager. For BOINC this is '''translation at boinc period berkeley period edu'''. Use this address also for SETI@home translations. For other projects, contact the project.
    15     * Obtain (typically via CVS) the 'authoritative' translation file. Usually this is en.po (English).
     15    * Obtain (typically via SVN) the 'authoritative' translation file. Usually this is en.po (English).
    1616    * Create a translation file for your language. You can do this using a text editor or a specialized tool such as [http://sourceforge.net/projects/poedit/ poedit].
    1717    * Send this to the translation manager, who will then install it on the project's web site. Check all relevant pages and fix as needed.
    1818    * Subscribe to the [http://ssl.berkeley.edu/mailman/listinfo/boinc_loc boinc_loc at ssl.berkeley.edu] email list, which is for translation-related discussion and announcements.
    19     * Because web sites are dynamic, you will have to periodically update your translation. You can do this efficiently by looking at the CVS diffs of the authoritative translation file.
     19    * Because web sites are dynamic, you will have to periodically update your translation. You can do this efficiently by looking at the SVN diffs of the authoritative translation file.
    2020
    2121== Translation files ==
    … …  
    6161You can edit UTF-8 on Windows using [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++].
    6262On Linux, you can use [http://www.vim.org/htmldoc/mbyte.html#UTF-8 vim].
     63{{{
     64#!comment Need to change this, all languages *should* use UTF-8 at least for the website side; other charsets cause problems. Existing translations have been converted already.
     65}}}
    6366
    6467Here are links to the translation files for
    6568
    66     * [http://boinc.berkeley.edu/trac/browser/trunk/boinc/languages/translations/ this web site]
    67     * [http://boinc.berkeley.edu/trac/browser/trunk/boinc/html/languages/translations/ the BOINC-supplied part of project web sites]
    68     * [http://boinc.berkeley.edu/trac/browser/trunk/boinc/locale/client/ the BOINC Manager]
     69    * [source:trunk/boinc/languages/translations/ this web site]
     70    * [source:trunk/boinc/html/languages/translations/ the BOINC-supplied part of project web sites]
     71    * [source:trunk/boinc/locale/client/ the BOINC Manager]
    6972
    7073== Writing translatable web pages ==
    … …  
    8891}}}
    8992
    90 For BOINC projects, the directory html/languages/translations contains a number of 'translation files'. When a person accesses the page, the browser passes a list of languages. The BOINC PHP code finds the first of these languages for which a translation is available, or English if none. As the page is generated, each call to `tr()` replaces the token with the corresponding translated text.
     93For BOINC projects, the directory [source:trunk/boinc/html/languages/translations/ html/languages/translations] contains a number of 'translation files'. When a person accesses the page, the browser passes a list of languages. The BOINC PHP code finds the first of these languages for which a translation is available, or English if none. As the page is generated, each call to `tr()` replaces the token with the corresponding translated text.
    9194
    9295In developing web pages, keep in mind that word order differs between languages, so you should avoid breaking a sentence up into multiple translation units. For example, use constructs like
    … …  
    116119    * Project-specific pages (and BOINC pages that are modified by the project).
    117120
    118 To allow translations of both types of pages, a project can haves its own 'project-specific translation files'. These are stored in a directory html/user/project_specific_translations. Project-specific translation files override BOINC translation files.
     121To allow translations of both types of pages, a project can haves its own 'project-specific translation files'. These are stored in a directory [source:trunk/boinc/html/user/project_specific_translations html/user/project_specific_translations]. Project-specific translation files override BOINC translation files.
    119122
    120123== BOINC Manager translations ==
    121124
    122 Menu names and other text in the BOINC manager are stored in files in '''boinc/locale/client/'''.
     125Menu names and other text in the BOINC manager are stored in files in [source:trunk/boinc/locale/client/ boinc/locale/client/].