#3 l10n/i18n

3.2
open-accepted
nobody
7
2007-07-27
2004-12-02
franjb68
No

I've tryed the Spanish translation of the application
and there are lots of strings still in English.

I've seen there are lots of strings still hardcoded
into PHP code, wich makes translation difficult. żAre
you thinking on taking more strings out of the code and
put them on the right language.php file?

I don't know almost anything about PHP, but I think
that's an easy task and I offer me to do it.

Greetings,
franjb68

Discussion

  • franjb68
    franjb68
    2004-12-02

    • priority: 5 --> 7
     
  • Logged In: YES
    user_id=260615
    Originator: NO

    Removing text strings from the code and putting them in an external resource is a good idea.

    I suggest that the language files each have the name XX.xml, where XX is the three-letter ISO 639-1 language abbreviation. The file name is lowercase.

    The file itself should be a UTF-8 text file with Unix line-endings.

    The structure of the language file should be a series of variable assignments to the $translation array, and variables should be defined using single quotes (e.g., $translation['welcome'] = 'welcome, %s').

    Strings should not be capitalized unless they are proper nouns (e.g., "Idaho"). The system will reformat strings if they need to be capitalized for display purposes.

    Where no language-specific entry is available for a given text string, the system will use the English value instead. Where no value can be found for the given string variable, the system will display the name of the variable index (e.g., if $translation['welcome'] is not defined, the system will display "welcome").

    I am tentatively scheduling this for 3.2. I do not think we will get to it for 3.1.

     
    • milestone: --> 3.2
    • status: open --> open-accepted