Message-ID: <1771385119.1901.1425273167897.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1900_1191462421.1425273167897" ------=_Part_1900_1191462421.1425273167897 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Q: I received notification mail of changed language fil= e. Why my modifications look different in my mail as I was edited in the ed= itor? There seem to be wrong characters.
A: First line in language XML file tells the encoding o= f the text. It could be for example "iso-8859-1", "utf-8&quo= t; and so on. When version system sends the notification mail the content m= ay not be in the same format as your modifications. In addition your mail p= rogram will view text with encoding which is in settings and it may differ = from language file encoding. You may change encoding for current viewed mai= l in some mail programs. Changing encoding to correct one should view text = with your language characters. Note that this change might not be permament= .
Q: I have made XML file with UTF-8 encoding. Why it has= extra characters beginning of the file? Another problem may occure too: so= me panes won't be shown.
A: You should use encoding aware editor and save it wit= hout BOM (Byter Order Mark). XML parser which IzPack is using at this momen= t won't work correct with BOM.
In order to have correct encoding to work add following line in very beg= inning of IzPack XML files:
and save them without byte order mark. If you use this for all other enc= odings too, some editors will warn you if you are adding characters which w= on't be able to be encoded with current encoding setting. There is always e= ncoding in language pack files. See them too.
Don't use Windows Notepad.exe editor because it automatically adds BOM i= nto the file when it is encoded with UTF-8. Here is just brief list of the = editors which will handle encodings:
Open Source editors:
Q: How can I execute the a package installer on Mac OSX= from IzPack?
A: You can include a shell script with your IzPack inst= aller that mounts a dmg, then launches the installer within it. The shell s= cript looks something like this:
To execute the shell script from within a <pack> in your install.x= ml file, use the following lines:
The <parsable> line replaces the $INSTALL_PATH token in your shell= script so that IzPack can call the shell script. The <file> line cop= ies the actual dmg to your installation path. The first <executable> = line makes the shell script executable (i.e. chmod a+rx). The second <ex= ecutable> line executes the shell script. This code assumes you've named= your shellscript 'loaddmg.sh'. When you run your installer, you should see= the external installer launch at the end of your installers execution.
Q: How can I get more debug output from an installer? A: You can execute the installer with the following c= ommand to get a full debug stream from IzPack:
Q: How can I debug an uninstaller as it launches itself=
several times to remove file locks and hence we get no console output?
A: For IzPack 5, see Debugging Uninstallers
For IzPack 4, see the solution proposed by Christian = d'Heureuse at http://jira.codehaus.org/browse/IZPACK-= 331