dragonleo/NSIS
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Clarified LangStringUP a bit more

Browse source 
git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@2153 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2003-02-13 14:53:18 +00:00
parent 6e05822383
commit 23637d7232
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Docs/src/langs.but
View file

@ -16,7 +16,9 @@ Defines a multilingual string and spares the comparing of $LANGUAGE to every lan
LangStrings can you only be used on their own. You can't include them in other strings. "look at my $(string)! isn't it beautiful?" will be seen exactly as written, $(string) will not be expanded. If you want to use LangStrings in other strings you can first copy the LangString to a variable and then use the variable wherever you want. This is a temporary situation, it will be changed before NSIS 2 final.
Note that unlike defines that use curly braces - \{\}, multilingual strings use parenthesis - ().
\\<b\\>Note #1:\\</b\\> Unlike defines that use curly braces - \{\}, multilingual strings use parenthesis - ().
\\<b\\>Note #2:\\</b\\> If you see weird characters between letters in the string when you use LangString, use LangStringUP (LangString for unprocessed string such as InstType)
For example, instead of:
@ -35,8 +37,6 @@ Use:
\c
\c MessageBox MB_OK $(message)
\\<b\\>Note:\\</b\\> If you see squares between letters in the string when you use LangString use LangStringUP (LangString for unprocessed string such as InstType)
\S0{langs} Multiple Languages
As of version 2 NSIS fully supports multiple languages. An installer can have more than one language. Each string in the installer can be easily translated, and so can script strings such as messages in a message box.