Thiago, Sorry I don't understand your objection. Could you expand on it please? Especially where you say "have a memory and bandwidth penalty using 2 bytes to encode many characters that would be encoded as 1 in UTF-8".
In my experience char encoding can be an absolute nightmare and having as much as possible as UTF-8 is highly desirable. IIRC Java uses UTF-16 internally which does have 2 bytes for each char, but UTF-8 only uses 2 bytes for unusual chars which is why it's the ideal external charset. Andy. > -----Original Message----- > From: Thiago H. de Paula Figueiredo [mailto:[EMAIL PROTECTED] > Sent: 29 July 2008 02:59 > To: Tapestry users > Subject: Re: What if Tapestry's I18N was just "UTF-8"? > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
