On Wed, 2002-09-11 at 05:12, [EMAIL PROTECTED] wrote: > I want to open the discussion about localization in > Tapestry. > > I've gotten a steady trickle of feedback from beyond > western europe where they are using Tapestry, and it > isn't all good. > > The stuff Tapestry does well, such as localizing assets > and providing access to localized string properties, is > perfectly ok. > > The problem is that when you get beyond latin-1 charset, > things aren't as good. There's so much going on ... > browsers, fonts, UTF-8, HTML, HTML entities ... it's > hard to figure out what's going wrong. > > I just tried an experiment, opening the response stream > as "text/html; charset=UTF-8" and got mixed results > (some characters in the french and italian render as > boxes rather than characters). I have no idea what I'd > get if I was using a Chinese or Japanese character set. > > So ... who out there has the expertise to identify whats > right and what's wrong in Tapestry's localization?
I'm having good success with Tapestry and UTF-8, although my testing is not complete. I've put some notes up at http://tapestry.sourceforge.net/wiki/index.php/EnablingUnicode Tom -- "Optimism is a duty. The future is open. It is not predetermined. No one can predict it, except by chance. We all contribute to determining it by what we do. We are all equally responsible for its success." Karl Popper ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
