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.

----- Original Message -----
From: "Aurélien Pernoud" <[EMAIL PROTECTED]>
To: "'Jetspeed Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, October 03, 2002 3:01 PM
Subject: RE: Strange Javascript Transfert using Jetspeed : encoding issue ?


>
> Thanks for help, I was getting mad !
>
> I'm reporting a bug right now cause I think it's important and I need
> ISO-8859 in my webapp :/
> Right now i'll just try to rewrite JS Files without accentuated characters
> and see what happens, because I'm afraid of "I'm unsure what other side
> effects this may have." ;)
>
> Hope it will get fixed before 1.4 final though... What you think ?
>
> > -----Message d'origine-----
> > De : Luta, Raphael (VUN) [mailto:[EMAIL PROTECTED]]
> > Envoyé : jeudi 3 octobre 2002 14:48
> > À : 'Jetspeed Users List'
> > Objet : RE: Strange Javascript Transfert using Jetspeed :
> > encoding issue
> > ?
> >
> >
> > Looking at the code, it seems that the issue is in the
> > MimeType class that
> > has been changed to
> > hard code the charset to UTF-8 for text/html (with a FIXME
> > note but that's still not an excuse...)
> >
> > You can try removing the hard-coded UTF-8 reference and
> > recompile. This will
> > probably fix
> > your issue but I'm unsure what other side effects this may have.
> >
> > Otherwise, use HTML entities (&eacute; etc...) to encode your
> > accentuated
> > characters in
> > encoding independent format or simply write your comments in
> > English :/
> >
> > Also filing a bug in Bugzilla about this issue would probably
> > ensure that
> > it's not
> > forgotten somewhere...
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to