"Nicky Ayoub" <[EMAIL PROTECTED]> writes:
> Thinking out loud: Should TG force unicode everywhere within the framework?
> Since ascii is like a subset, the [english] North Americans shouldn't
> complain...The rest of the world gets what they need... and if we
> standardize on the one encoding scheme this problem simply disappears. Ok
> people: Tell me where I'm wrong...
Why using more memory and storage where you don't need it? If all my clients
are going to use ISO-8859-1 why should I waste resources with UTF-8? :-)
The thing that is interesting with TG is the ability to choose and design your
application with the most freedom possible.
Also, there are reports that UTF-8 isn't enough to handle certain Japanese
needs, for example:
- http://www.jbrowse.com/text/unij.html
-
http://publib.boulder.ibm.com/infocenter/hodhelp/v9r0/index.jsp?topic=/com.ibm.hod9.doc/help/dbcs_jaa.html
- http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode
You can find more on Google. ;-)
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
