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? -- [EMAIL PROTECTED] http://tapestry.sf.net ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
