over 0xff. What I understand is, that it works on your WinBox
change some formats. May be than we can remove the workaround
instead of xml files for langpacks. Unfortunately chars behind
Therefore I try to write a simple editor for it. No problem to convert
I have the same problem e.g. with JEdit. What is the common way
> -----Original Message-----
> From:
izpack-users-bounces@...
> [mailto:
izpack-users-bounces@...] On Behalf Of guan
> Sent: Wednesday, April 18, 2007 2:06 AM
> To:
izpack-users@...
> Subject: Re: [izpack-users] 2 Bugs Report
>
>
>
> Hi Klaus,
> Thank you very much for your answer.
> I have tested the shortcutSpec.xml without the if(c > 0xFF)
> sequence (i.e. delete it), and the created shortcut can work
> well in Windows and Linux. And the "some quaint bytes " that
> you referred to maybe "1070,1087,1074,1070,1101" which will
> be generated right after the installPanel in windows, however
> this "some quaint bytes " will not be generated in Linux.
> Till now, I donot know the reason.
>
> Cheers
>
> Guan
>
>
> Bartz, Klaus wrote:
> >
> > Hi Guan,
> > last october I have implemented it after a longer search why a
> > shortcutSpec.xml does not work. In the special situation a
> BOM (Byte
> > Order Mark) of an utf-8
> > file will tgrigger a fail at parsing. In the moment I do
> not rember why I
> > have written the
> > additional line with the if(c > 0xFF) sequence; may be I
> have seen some
> > quaint
> > bytes in debugger.
> > Therfore I do not really know whether it works with BOMbed
> utf-8 files or
> > not.
> > Will be nice if you can test it.
> >
> > Cheers
> >
> > Klaus
> >
> >> -----Original Message-----
> >> From:
izpack-users-bounces@...
> >> [mailto:
izpack-users-bounces@...] On Behalf Of guan
> >> Sent: Tuesday, April 17, 2007 10:21 AM
> >> To:
izpack-users@...
> >> Subject: Re: [izpack-users] 2 Bugs Report
> >>
> >>
> >>
> >> Hello Julien,
> >>
> >> Thank you very much for your answer.
> >>
> >> It is really an encoding problem, In fact, there existes the
> >> same problem in Chinese Version. Now I can resolve the
> >> problem by the following way : In (IzPack3.10.1) line 292 of
> >> com.izforge.izpack.util.VariableSubstitutor.substitute
> >> substitute(Reader,Writer,String)
> >> modify [ if(c>0xFF) ] -> [ if(c==0xFF) ] , or delete
> this segment.
> >> because: the value of the missed charactor is "12452" which
> >> is bigger than oxFF. -------------------the original
> >> code------------------------ // Ignore quaint return values
> >> at UTF-8 BOMs.
> >> if( c > 0xFF )
> >> c = reader.read();
> >> ---------------------------------------------------------------
> >> But I am not sure whether it is the right way to solve the
> >> problem. and now I am learning the knowlege about encoding problem.
> >>
> >> By the way, could you tell me how to solve the 2nd question.
> >> Bug2. In UserInputPanel, during the installation proccess,
> >> when I select the "previous" button to see the previous
> >> UserInputPanel again, the previous UerInputPanel cannot show
> >> in right layout.
> >>
> >> Regards,
> >> Guan
> >>
> >>
> >>
> >>
> >> Julien Ponge-3 wrote:
> >> >
> >> > Guan,
> >> >
> >> > I don't know how to handle your report since I think your
> >> message has
> >> > encoding problems and I cannot read Japanese, so I am
> not sure what
> >> > the problem really is :-(
> >> >
> >> > On 4/11/07, guan <
enzheng.guan@...> wrote:
> >> >>
> >> >> Bug1. When I selcect "Quit" button during an installation
> >> proccess.
> >> >> In the Japanese Version there exists such a bug: the right
> >> message to
> >> >> show is
> >> >> :"インストール中止", but IzPack shows a wrong message "ンストール中止"
> >> which missed
> >> >> the
> >> >> "イ". The image is like the following picture: [image: 2
> >> Bugs Report] I
> >> >> think the reason causes in line 1179. 1180 of
> >> >> com.izforge.izpack.installer.InstallerFrame.java. And I
> >> think the bug is
> >> >> in method substitute() which exists in Line 267 of
> >> >> com.izforge.izpack.util.VariableSubstitutor.substitute.
> >> But now I dont
> >> >> know how to correct it. Bug2. In UserInputPanel, during
> >> the installation
> >> >> proccess, when I select the "previous" button to see
> the previous
> >> >> UserInputPanel again, the previous UerInputPanel cannot
> >> show in right
> >> >> format. the first time to see the UerInputPanel： [image: 2 Bugs
> >> >> Report]the second time to see it when click the
> "previous" button:
> >> >> [image:
> >> >> 2 Bugs Report] Till now I do not konw the reasons, would
> >> you like to help
> >> >> me. Very Very Thanks!
> >> >> ------------------------------
> >> >> View this message in context: 2 Bugs
> >> >>
> Report<
http://www.nabble.com/2-Bugs-Report-tf3556704.html#a9931343> >> >> >
> >> >> Sent from the izpack users mailing list
> >> >> archive<
http://www.nabble.com/izpack-users-f15508.html>at
> >> >> Nabble.com.
> >> >>
> >> >> _______________________________________________
> >> >> izpack-users mailing list
> >> >>
izpack-users@...
> >> >>
https://lists.berlios.de/mailman/listinfo/izpack-users> >> >>
> >> >>
> >> >
> >> > _______________________________________________
> >> > izpack-users mailing list
> >> >
izpack-users@...
> >> >
https://lists.berlios.de/mailman/listinfo/izpack-users> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
http://www.nabble.com/2-Bugs-Report-tf3556704.html#a10031113> >> Sent from the izpack users mailing list archive at Nabble.com.
> >>
> >> _______________________________________________
> >> izpack-users mailing list
> >>
izpack-users@...
> >>
https://lists.berlios.de/mailman/listinfo/izpack-users> >>
> > _______________________________________________
> > izpack-users mailing list
> >
izpack-users@...
> >
https://lists.berlios.de/mailman/listinfo/izpack-users> >
> >
>
> --
> View this message in context:
>
http://www.nabble.com/2-Bugs-Report-tf3556704.html#a10050076> Sent from the izpack users mailing list archive at Nabble.com.
>
> _______________________________________________
> izpack-users mailing list
>
izpack-users@...
>
https://lists.berlios.de/mailman/listinfo/izpack-users>
Some parts of this message have been removed.
Learn more about Nabble's security policy.
