Em Mon, 28 Jul 2008 21:17:11 -0300, Howard Lewis Ship <[EMAIL PROTECTED]>
escreveu:
What if there was just a single default application character set,
which would default to UTF-8?
This is not a nice option. Web applications that need accented characters
(most Latin languages), but don't need to support another alphabets, will
have a memory and bandwidth penalty using 2 bytes to encode many
characters that would be encoded as 1 in UTF-8. In addition, I had some
problems with Tapestry 5 using UTF-8 when using an existing ISO-8859-1
MySQL database tables. Accented characters were always store as two
garbled ones. Maybe I didn't spend enough time to solve it (I was doing
some consultancy that had a fixed end date), but this could a huge problem
for Tapestry adoption in Latin-speaking languages.
My two Brazilian (Portuguese-speaking, with many accented characters)
cents,
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
