Yes, it definitely fixes the basic issue but not all the issues like the one Santiago tried to fix with his patch: making sure content that comes in different encodings (like iso-8859-1 and iso-8859-2 feeds on the same page) do not conflict with each other...
> -----Message d'origine----- > De : Werner Punz [mailto:werpu@;gmx.at] > Envoy� : lundi 21 octobre 2002 16:29 > � : Jetspeed Users List > Objet : Re: Next Stable Release? > > > Guys have a look at the fixed class I just sent down the mailing list. > It basically fixes the problem (according to an old post in the list) > At least it does it for me on my machine. > > The problem was that the UTF-8 string is hardcoded in the > MimeType class > altering that to load the settings dynamically from the config files > does the job. I set the encoding to ISO-8859-1 and now all the pages > are rendered correctly into ISO as far as I can see. > > I�m not sure if there are other hardcoded UTF-8 settings in the code > but this one definitely solved a big problem for me. > > > > Luta, Raphael (VUN) wrote: > > It's the same issue so I'll try to fix it also. > > > > However, I'd love if you could append to this bug in > bugzilla a set of > > RSS feeds encoded in iso-8859-2 so that I can use them as a > test case. > > > > For iso-8859-1, I should be able to make these test cases myself :) > > > > > > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:jetspeed-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:jetspeed-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:jetspeed-user-help@;jakarta.apache.org>
