Support > cpg1.5 language

[Done]: Dutch translation for English.php 1.5.3

<< < (2/3) > >>

Albe:

--- Quote from: Joachim Müller on March 16, 2010, 07:04:54 am ---Fixed in rev 7315. However, I can't see how those little issues are related to translation.

--- End quote ---

Thanks!

These notes were only indirect related to the translation.
While my first translation didn't work, I was looking for a reason and read thoroughly (like you always advise) your documentation and original file.

Meanwhile I've found why my dutch-language wasn't found in Coppermine.

I had to add the language in: "charsetmgr.php"


--- Code: ---// Displays a menu with a choice of charsets
function form_charset($optionvalue, $selected)
{
    global $CONFIG;


    $charsets = array(//'Default' => 'language file',
        'Arabic' => 'iso-8859-6',
        'Baltic' => 'iso-8859-4',
        'Central European' => 'iso-8859-2',
        'Chinese Simplified' => 'euc-cn',
        'Chinese Traditional' => 'big5',
        'Cyrillic (windows-1251)' => 'windows-1251',
        'Cyrillic (koi8-r)' => 'koi8-r',
        'Dutch' => 'utf-8', //1.5.3 Albert
        'Greek' => 'iso-8859-7',
        'Hebrew' => 'iso-8859-8-i',
        'Icelandic' => 'x-mac-icelandic',
        'Japanese' => 'euc-jp',
        'Korean' => 'euc-kr',
        'Maltese' => 'iso-8859-3',
        'Thai' => 'windows-874',
        'Turkish' => 'iso-8859-9',
        'Unicode' => 'utf-8',
        'Vietnamese' => 'windows-1258',
        'Western' => 'iso-8859-1'
    );

    //$value = strtolower($CONFIG['charset']);


--- End code ---

This weekend I will finnish the translation of dutch.php and (if you approve) send it as an attach in the thread :" [Help wanted]: Translations for CPG1.5.x", like you prescribed in your documentation.

Joachim Müller:

--- Quote from: Albe on March 16, 2010, 07:40:08 pm ---I had to add the language in: "charsetmgr.php"


--- Code: ---// Displays a menu with a choice of charsets
function form_charset($optionvalue, $selected)
{
    global $CONFIG;


    $charsets = array(//'Default' => 'language file',
        'Arabic' => 'iso-8859-6',
        'Baltic' => 'iso-8859-4',
        'Central European' => 'iso-8859-2',
        'Chinese Simplified' => 'euc-cn',
        'Chinese Traditional' => 'big5',
        'Cyrillic (windows-1251)' => 'windows-1251',
        'Cyrillic (koi8-r)' => 'koi8-r',
        'Dutch' => 'utf-8', //1.5.3 Albert
        'Greek' => 'iso-8859-7',
        'Hebrew' => 'iso-8859-8-i',
        'Icelandic' => 'x-mac-icelandic',
        'Japanese' => 'euc-jp',
        'Korean' => 'euc-kr',
        'Maltese' => 'iso-8859-3',
        'Thai' => 'windows-874',
        'Turkish' => 'iso-8859-9',
        'Unicode' => 'utf-8',
        'Vietnamese' => 'windows-1258',
        'Western' => 'iso-8859-1'
    );

    //$value = strtolower($CONFIG['charset']);


--- End code ---

--- End quote ---
That was nonsense - undo that. All Coppermine language files are in Unicode (utf-8), you don't have to apply particular encoding settings. Using the existing option "Western" would have done the trick just as well if you can't use (for whatever obscure reasons) the default and recommended encoding utf-8. You definitely don't have to edit the charset manager or any other core file to create and test a language file.
However, this is yet another issue that is not related to what you reported in your initial posting and therefore shouldn't have gone into this thread.

Albe:

--- Quote from: Joachim Müller on March 18, 2010, 10:08:39 pm ---However, this is yet another issue that is not related to what you reported in your initial posting and therefore shouldn't have gone into this thread.

--- End quote ---

OK, sorry!

Albe:
As promised, in attach my translation from english.php into dutch.php, using Notepad++.
I've tested it on my local computer (in USBWebserver) and in my host.
It works on both places, only accented characters give still a problem? (see attach).

I don't think it has something to do with the translation?
Can I do something about that?

Joachim Müller:
Well, your file is encoded in iso-8859-1 and not in unicode. That's why the accented chars "act up". I have converted your file accordingly and added it to the SVN repository in rev 7328. Thanks for your contribution. To get a valid, working copy, get the converted file from the web SVN.

Navigation

[0] Message Index

[#] Next page

[*] Previous page