Yes that's it. Currently Jetspeed is hard-coded to use UTF-8 encoding when responding to a browser, but I just reported the bug (thanks to Raphael who found the bug !).
I think it should be fixed soon, depends on the consequences of this hard-coded part. > -----Message d'origine----- > De : Marian Skalsky [mailto:[EMAIL PROTECTED]] > Envoyé : vendredi 4 octobre 2002 11:25 > À : Jetspeed Users List > Objet : Re: Strange Javascript Transfert using Jetspeed : > encoding issue > ? > > > Hi there! > I want my velocity templates, properties files and .xreg > files to be encoded > in ISO-8859-2, but it does not work for me. > I encoded properties files, templates and xml .xreg files > with this encoding > and set up turbine, velocity and js properties files on every > place I've > found something related to *encoding*, but with no success. > When I open the JS in browser, I got always UTF-8 ... > .. I'm not sure if I understand this right, may be this issue > related to > stuff you are talking about ? (some hardcoded UTF-8..) ? > Thx. > $kala. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
