|
1 <html> |
|
2 <head> |
|
3 <title>ExperienceUI Documentation Content Frame</title> |
|
4 <link rel=stylesheet href=style.css type=text/css> |
|
5 |
|
6 <script type=text/JavaScript> |
|
7 function printemail(email) { |
|
8 var domain = "users.sourceforge.net"; |
|
9 document.write('<a href="mailto:' + email +'@users.sourceforge.net?subject=ExperienceUI comments">'); |
|
10 document.write(email +'@users.sourceforge.net</a>'); |
|
11 } |
|
12 </script> |
|
13 </head> |
|
14 |
|
15 <body bgcolor="#FFFFFF" style="background-color:#FFFFFF;margin:0px;padding:0px"> |
|
16 |
|
17 <table border=0 width=100% height=100%> |
|
18 |
|
19 <tr> |
|
20 |
|
21 <td valign=top style=margin:10px;padding:10px> |
|
22 |
|
23 <h1>Multiple Languages</h1> |
|
24 |
|
25 <p style=margin-left:0.2in> |
|
26 |
|
27 <font face=Verdana style=font-size:8pt color=#000000> |
|
28 Since version 1.04, the ExperienceUI features support for multiple languages. The platform is based on that of the Modern UI's |
|
29 (Joost does it again!) with a few modifications to make it work with the XPUI. To use multiple languges in your installer, simply |
|
30 insert the XPUI_LANGUAGE macro, with 1 parameter, which should be the filename, minus the extension, of the language. |
|
31 (ex: !insertmacro XPUI_LANGUAGE Spanish)<br> |
|
32 <br> |
|
33 To write a language file, you can follow the English language file included with the XPUI, and, if necessary, write an NLF (Nullsoft |
|
34 Language File; the NSIS side of the XPUI multi-language system) and make sure that your .NSH file has the same name as the NLF |
|
35 file.<br> |
|
36 <br> |
|
37 </p> |
|
38 |
|
39 <h1>Translating the ExperienceUI</h1> |
|
40 <p style=margin-left:0.2in> |
|
41 |
|
42 <font face=Verdana style=font-size:8pt color=#000000> |
|
43 If you are fluent a language other than English, I would greatly appreciate it you would spend some time translating the ExperienceUI into your native language. You can edit the strings in <code><NSIS>\Contrib\ExperienceUI\Language Files\English.nsh</code>, and save them in a new file. If you translate the ExperienceUI, I (and the many people that speak your native language) would sincerely appreciate it if you e-mail it to me. <br> |
|
44 <br> |
|
45 Any language you can help with would be appreciated, but the languages I am looking for the most right now are Spanish, French, German, Chinese (Simplified and Traditional), Arabic, and Portuguese. The ExperienceUI already has a Brazilian Portuguese translation, courtesy of Jenner Modesto.<br> |
|
46 <br> |
|
47 You can send translated language files to me at <script language=JavaScript>printemail('dandaman32');</script>. |
|
48 </font></p> |
|
49 |
|
50 <a name=cmd id=cmd></a> |
|
51 |
|
52 <h1>Language Commands</h1> |
|
53 |
|
54 <p style=margin-left:0.2in> |
|
55 |
|
56 <font face=Verdana style=font-size:8pt color=#000000> |
|
57 <b>Macros</b><br> |
|
58 <br> |
|
59 <b>XPUI_LANGUAGE</b> <font color=#294F75>Langfile(no_ext)</font> - Adds a language to your installer. Don't insert the same |
|
60 language twice. (ex: <code>!insertmacro XPUI_LANGUAGE French</code>)<br> |
|
61 <br> |
|
62 <b>XPUI_LANGDLL_DISPLAY</b> <font face=#294F75></font> - Shows the language selection dialog. Use this in .onInit. This should |
|
63 eventually be a page.<br> |
|
64 <br> |
|
65 <b>XPUI_LANGPAGE_DISPLAY</b> <font face=#294F75></font> - Insert this macro in your .onInit function to show a page that asks the user |
|
66 which language to use. At compile time, a custom EXE is built and any visual settings you use are carried over. At runtime this |
|
67 custom EXE is extracted and run. If you insert this anywhere except in .onInit, the page will compile and show but the selected |
|
68 language will not be changed because of limitations in NSIS. To manually change settings with the language page, edit <NSIS>\Contrib\ExperienceUI\LangPage.nsi. |
|
69 <b>Because of a bug in this page, you must only use languages that have 4-digit identifiers. Most languages have 4-digit IDs, but a few |
|
70 do not. The only known language that uses a 5-digit ID is currently Breton. An example of a language with a 4-digit ID is English, whose |
|
71 ID is 1033.</b><br> |
|
72 <br> |
|
73 <b>XPUI_UNGETLANGUAGE</b> - Retrieves the saved language from the user's Registry, and, if the language is invalid, asks the user |
|
74 to select his/her preferred language.<br> |
|
75 <br> |
|
76 <b>Defines</b><br> |
|
77 <br> |
|
78 <p style="margin-left: 0.30in"> |
|
79 <b>XPUI_LANGDLL_REGISTRY_ROOT</b> <font color=#294F75>(HKCR|HKLM|HKCC|HKCU|HKU|HKDD)</font> - The registry root to store the user's |
|
80 language preference in. (ex: HKLM)<br> |
|
81 <br> |
|
82 <b>XPUI_LANGDLL_REGISTRY_KEY</b> <font color=#294F75>My\Registry\Key</font> - The registry key to store the user's |
|
83 language preference in. (ex: SOFTWARE\MyProgram\Setup)<br> |
|
84 <br> |
|
85 <b>XPUI_LANGDLL_REGISTRY_VALUE</b> <font color=#294F75>MyRegValue</font> - The registry value to store the user's |
|
86 language preference in. (ex: LanguagePrefID)<br> |
|
87 <br> |
|
88 </font> |
|
89 </p> |
|
90 |
|
91 </td> |
|
92 |
|
93 </tr> |
|
94 |
|
95 <tr> |
|
96 |
|
97 <td valign=bottom style=margin:0px;padding:0px> |
|
98 |
|
99 <p class=footer>Copyright © 2004-2006 Dan Fuhry. All rights except those explicitly given in the <a href=license_agreement.htm style=color:#A0A0D0 onmouseover="this.style.color='#A0A0A0'" onmouseout="this.style.color='#A0A0D0'">license agreement</a> reserved.</p> |
|
100 |
|
101 </td> |
|
102 |
|
103 </tr> |
|
104 |
|
105 </table> |
|
106 |
|
107 </body> |
|
108 |
|
109 </html> |