[izpack-users] shortcutSpec.xml UTF-8 Byte Order Mark breaksIzPackoperation

Hans-Georg Michna hans-georg at michna.com
Wed Oct 18 13:24:30 CEST 2006


On Tue, 17 Oct 2006 17:37:56 +0200, Bartz, Klaus wrote:

>I have not written the shortcut part of IzPack, but if I look
>into the sources it seems for me, that the parsing of the xml
>file will be performed in the java part of the shortcut stuff 
>(see ...panels.ShortcutPanel.readShortcutSpec).
>OK, but why only a crash with the shortcutSpec.xml???
>
>Really good question. The shortcutSpec will be parsed also by
>nanoxml, what else? In opposite to other specs this will be
>directly substituted by the VariableSubstitutor. This uses a
>InputStreamReader which uses StreamDecoder$CharsetSD. 
>If a BOM is there, this will not consumed else read returns
>65259 as first character. I do not know why and I do not know
>whether this is a bug in the VM or not. I have the impression
>that you like to write bug reports. Therefore retrace the bug
>and write a report to sunsoft.

Klaus,

thanks for looking into this!

I fear I'm not in a position to write a bug report to sunsoft,
because I can't retrace or demo the bug for them. I would do it,
if only I could. I'm not a Java developer and don't even have a
Java compiler or debugger ready. (This may change soon, but not
yet.)

In fact I don't like to write bug reports. I strongly prefer
bug-free software. But I do write them, if I have to. If I find
a bug that will affect many other users, I will write a bug
report, even if I already know a workaround. A little bit of
altruism here, in return for the altruism of the developers, who
do all the major work. I hope, of course, that the developers
appreciate bug reports.

By the way, currently I'm stumped by the other apparent bug,
concerning <executable ...> (see other thread). If I cannot
resolve that, my choices are very limited. Going back to 3.8.1
is nearly out of the question, so I'd have to go to another
product altogether, probably install4j. I hope I'm only making a
mistake here and someone can point it out, or perhaps it's
another one of those documentation mismatches. Do you have any
idea about that one? Should go in the other thread, but since
you're reading this one, I thought I might as well ask.

Hans-Georg

-- 
No mail, please.




More information about the izpack-users mailing list