psyke
2nd October 2003 19:52 UTC

translating into 'unsupported' language questions
before i begin i just wanted to say that i looked through the forums and NSIS docs for the answers. if i missed something, i'm sorry, please point me at it.

i'd like to know, step by step, how i should translate an installer into a language that doesn't have .nlf or .nsh files already.

here's what i think i'm suppposed to do, please correct any errors:

in this example i'll pick norwegian. :)[list=1][*]use makelangid to make an id, but which sublang to choose (NORWEGIAN_[BOKM|NYNO]), and if there is no sublang like for AFRIKAANS, then what - choose _NEUTRAL, _DEFAULT, or _SYS_DEFAULT?[*]translate English.nlf and English.nsh, save as Norwegian.nlf (add makelangid's result here), Norwegian.nsh
(are the language files always plain ascii text files?)[*]define installer lang strings like 'LangString TestString ${LANG_NORWEGIAN} "some norwegian text"'
(is LANG_NORWEGIAN based on the filename, or has to be defined somewhere?)[*]use '!insertmacro MUI_LANGUAGE "Norwegian"'
(again, this is based on the filename, Norwegian.nsh?)[/list=1]

thanks for your help! :)

kichik
2nd October 2003 20:03 UTC

Yep, you got it right.

If there are no sublangs you should chose SUBLANG_DEFAULT, though it doesn't really matter as long as there are no other language files with the same main language.

If there are sunlangs you should chose the on that fits best. In English for example there are sublangs for America, UK, Austalia, etc. If you use colour instead of color you should choose UK.

The language files are always plain ASCII (MBCS) and never Unicode.

LANG_NORWEGIAN is automatically defined according to the file name.

MUI_LANGUAGE also works according to the file name.

psyke
2nd October 2003 20:06 UTC

thank you kichik for a swift and helpful reply! :) (i think i should add this to my signature, it would save some typing ;))

i am glad that i got the procedure right - it will come in handy if i'm ever in this situation. :)