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

typos (thanks Jamyn!)

Browse source 
git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@4264 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2005-09-16 11:27:51 +00:00
parent 4d6282546d
commit f8062527fa
30 changed files with 67 additions and 67 deletions
Download patch file Download diff file Expand all files Collapse all files

20
Docs/src/langs.but
View file

@ -12,7 +12,7 @@ After you have inserted the language file $\{LANG_langfile\} will be defined as
\c name language_id string
Defines a multilingual string. This means the its value will be different (or not, it's up to you) for every language. It allows you to easily make your installer multilingual without the need to add massive switches to the script.
Defines a multilingual string. This means its value may be different (or not, it's up to you) for every language. It allows you to easily make your installer multilingual without the need to add massive switches to the script.
Each language string has a name that identifies it and a value for each language used by the installer. They can be used in any runtime string in the script. To use a language string all you need to add to the string is $(LangString_name_here) where you want the LangString to be inserted.
@ -20,9 +20,9 @@ Each language string has a name that identifies it and a value for each language
\b Unlike defines that use curly braces - \{\}, language strings use parenthesis - ().
\b If you change the langauge in the .onInit function, note that language strings in .onInit will still use the detected language based on the user's default Windows language, because the language is initialized after .onInit.
\b If you change the language in the .onInit function, note that language strings in .onInit will still use the detected language based on the user's default Windows language, because the language is initialized after .onInit.
\b Always set langauge strings for every language in your script.
\b Always set language strings for every language in your script.
\b If you set the language ID to 0 the last used language by LangString or \R{loadlanguagefile}{LoadLanguageFile} will be used.
@ -50,15 +50,15 @@ Does the same as \R{langstring}{LangString} only it loads the string from a text
As of version 2 NSIS fully supports multiple languages. The interface of one installer can support multiple languages.
Use \R{loadlanguagefile}{LoadLanguageFile} for every langauge to load the default interface texts and language properties.
Use \R{loadlanguagefile}{LoadLanguageFile} for every language to load the default interface texts and language properties.
The default interface texts can easily be changed using instructions like \R{acomponenttext}{ComponentText} etc.
You can also use the contents of the standard language strings in your own strings (for example, $(^Name) contains the installer's name set using the \R{aname}{Name} instruction). The names of all standard langauges strings are listed as comments just above the strings in the language files. The language files are located in \L{../Contrib/Language files}{Contrib\\Language Files}.
You can also use the contents of the standard language strings in your own strings (for example, $(^Name) contains the installer's name set using the \R{aname}{Name} instruction). The names of all standard language strings are listed as comments just above the strings in the language files. The language files are located in \L{../Contrib/Language files}{Contrib\\Language Files}.
To create your own langauge strings, use \R{langstring}{LangString}.
To create your own language strings, use \R{langstring}{LangString}.
For an example of an installer with multiple langauges, see \L{../Examples/languages.nsi}{languages.nsi}.
For an example of an installer with multiple languages, see \L{../Examples/languages.nsi}{languages.nsi}.
\S1{langselection} Language Selection
@ -66,13 +66,13 @@ When the installer starts up it goes through these steps to select the interface
\n Get user's default Windows language
\n Find a perfect match for the langauge
\n Find a perfect match for the language
\n If there is no perfect match, find a primary language match
\n If there is no match, use the first language defined in the script (make sure your first language is a common one like English)
\n If the langauge variable \R{varconstant}{$LANGUAGE} has changed during .onInit, NSIS goes through steps 2 to 4 again.
\n If the language variable \R{varconstant}{$LANGUAGE} has changed during .onInit, NSIS goes through steps 2 to 4 again.
\S1{langdll} LangDLL Plug-in
@ -82,4 +82,4 @@ For an example of usage see \L{../Examples/languages.nsi}{languages.nsi}.
\S1{rtl} RTL Languages
RTL languages are languages that are written from the right to the left (like Arabic and Hebrew). NSIS fully supports RTL languages. In the language file there is a place to specify if the language is RTL or not. To find out on runtime if the the current langauge is RTL or not check the value of the $(^RTL) language string. It will be 1 if the language is RTL and 0 otherwise. This can be useful when using plug-ins that create dialogs, they usually have RTL settings too.
RTL languages are languages that are written from right to left (e.g. Arabic and Hebrew). NSIS fully supports RTL languages. In the language file there is a place to specify if the language is RTL or not. To find out at runtime if the current language is RTL or not, check the value of the $(^RTL) language string. It will be 1 if the language is RTL and 0 otherwise. This can be useful when using plug-ins that create dialogs, they usually have RTL settings too.