Message-ID: <104925668.23576.1406894742004.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_23575_361220991.1406894742003" ------=_Part_23575_361220991.1406894742003 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
IzPack is available in several languages. However you might want to inte= rnationalize some additional parts of your installer. In particular you mig= ht want this for the InfoPanel and LicencePanel. This is actually pretty easy to do. You just have to add one resour= ce per localization, suffixed with the ISO3 language code. At runtime these= panels will try to load a localized version.
For instance let's suppose that we use a HtmlInfoPanel.= Suppose that we have it in English, French and German. We want to have a F= rench text for french users. Here we add a resource pointing to the French = text whose name is HtmlInfoPanel.info_fra. And that's it! = English and German users (or anywhere other than in France) will get the de= fault text (denoted by HtmlInfoPanel.info) and the French = users will get the French version. Same thing for the other Licence= and Info panels.
To sum up: add _iso3code to the resource name for
You can customize any of the strings defined by the built-in langpacks. Add a resource(s) named "
CustomLangPack.xml" and/or "
_iso3code" to your
The CustomLangPac= k.xml file should look something like this: