[Tapestry-developer] Outcome of problem with UTF-8 vs ISO-8859-1

[h***@public.gmane.org]

Since I'm lucky enough to live in US, I don't have to deal with localization
and code pages, so I'm a little fuzzy on the actual problem.

What I've seen is that when I change the character encoding to UTF-8 (you can
do this in BasePage when creating the IMarkupWriter instance) some characters
don't render properly in IE. This could end up being anything in the stack
anywhere between my code, Jetty, java.io, IE or elsewhere ... or simply a
missing font.


If someone would take the time to document, on the Wiki, what they need
Tapestry to do and why we can see how to address it. I've been thinking that
applications and/or individual pages may want to override the default character
encoding for responses, this could be accomplished via a specification property
(a <property> element in the specification).

I'm sure someone out there deals with true localization/character set/code
page/character encoding issues daily and can educate us on what the ideal
solution would be.

--
hlship-***@public.gmane.org

http://tapestry.sf.net

Hi there,
subclass the ApplicationServlet
and insert this method
protected void doService(HttpServletRequest request, HttpServletResponse
response)
throws IOException, ServletException
{
request.setCharacterEncoding("UTF-8");
super.doService(request, response);
}
-----Original Message-----
Sent: Freitag, 20. Dezember 2002
Subject: [Tapestry-developer] Outcome of problem with UTF-8 vs ISO-8859-1
AG> I have managed to figure out how to do UTF-8 for everyting except input
AG> I input "étre" into a text field, if I use JavaScript to display the value
AG> of the field, it says "étre". But when it arrives at the server, it is
AG> converted to UTF-8, which ends up converting the é into a two byte
AG> character, but not the right ones (it is actually a ISO-8859-1 conversion,
AG> not a UTF-8. You can see the same effect by switching Eclipse into
AG> ISO-8859-1 mode, create an HTML, put in an é, save it and reload it, you
AG> great screwed up text. Switch into UTF-8 mode, delete the garbage and
AG> re-insert the é, save, reload, everything fine).
AG> What I'm wondering is: Does anyone know how to get the result of input
AG> fields in UTF-8, encoded properly. I can switch the charset of the page to
AG> ISO-8859-1 and have it return proper values, but then the dynamic data will
AG> not display properly on the UTF-8 pages (which is the mode I need to edit
AG> them in inorder to use Eclipse).
AG> -------------------------------------------------------
AG> This SF.NET email is sponsored by: The Best Geek Holiday Gifts!
AG> Time is running out! Thinkgeek.com has the coolest gifts for
AG> your favorite geek. Let your fingers do the typing. Visit Now.
AG> T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
AG> _______________________________________________
AG> Tapestry-developer mailing list
AG> https://lists.sourceforge.net/lists/listinfo/tapestry-developer
--
with best regards
homburg Softwaretechnik
Sven Homburg
Ohlendorfer Stieg 4
21220 Seevetal
Tel.: [phone]
Fax.: [phone]
WWW.: http://www.hsofttec.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-developer

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf