Talk:Creating language files and integrating with MUI: Difference between revisions
From NSIS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
But "English" means AE. How to use BE? | But "English" means AE. How to use BE? | ||
:Assuming you mean American English and British English, the answer is that there's no British translation available. No one has submitted such a translation. Use the forum for further questions.--[[User:Kichik|kichik]] 11:12, 20 June 2007 (PDT) | |||
---- | |||
Not sure if the example is broken or not, but to get it to work i had to change | |||
!undef LANGLOAD | |||
to | |||
!undef LANG | |||
and the !verbose commands should probably use the push pop stuff | |||
I'ts also not clear that you have to create a folder for your language files | |||
The standard include folder has LangFile.nsh that replicates and expands upon these features. | |||
Latest revision as of 08:46, 2 February 2009
2 Examples:
- !insertmacro MUI_LANGUAGE "English"
- !insertmacro MUI_LANGUAGE "German"
But "English" means AE. How to use BE?
- Assuming you mean American English and British English, the answer is that there's no British translation available. No one has submitted such a translation. Use the forum for further questions.--kichik 11:12, 20 June 2007 (PDT)
Not sure if the example is broken or not, but to get it to work i had to change !undef LANGLOAD to !undef LANG
and the !verbose commands should probably use the push pop stuff
I'ts also not clear that you have to create a folder for your language files
The standard include folder has LangFile.nsh that replicates and expands upon these features.
