> Should I require more information from the UI or is there a way to scan > the data that I am currently being passed and determine the appropriate > charset? If the UI insists on passing non-Unicode text, you must insist on more information...a tag perhaps that identifies the charset encoding. > Since I'm in a Java environment, isn't there be a way to go to UTF-8 and > from UTF-8 determine the corresponding ISO (and other) charset? One can do some statistical analysis on the code values and perhaps determine the language and then the charset encoding. However, this seems unreasonably difficult. If you are in a Java environment, why not pass UTF-8 or UTF-16 values around everywhere? -- John O'Conner
- How-To handle i18n when you don't know charset? Leon Spencer
- RE: How-To handle i18n when you don't know ... Mike Brown
- Re: How-To handle i18n when you don't know ... John O'Conner
- Re: How-To handle i18n when you don't know ... Jim Saunders
- RE: How-To handle i18n when you don't know ... Leon Spencer
- RE: How-To handle i18n when you don't know ... Chris Wendt
- Re: How-To handle i18n when you don't know ... Jim Saunders
- RE: How-To handle i18n when you don't know ... Mike Brown
- Re: How-To handle i18n when you don't know ... Michael \(michka\) Kaplan
- Re: How-To handle i18n when you don't know ... Michael \(michka\) Kaplan
- RE: How-To handle i18n when you don't know ... Chris Wendt
- Re: How-To handle i18n when you don't know ... Antoine Leca
- Re: How-To handle i18n when you don't know ... Michael \(michka\) Kaplan

