> The initial default encoding for documents is the same as
> the Windows system code page (GetACP()). As user chooses an
> encoding from the View.Encoding menu, it becomes the new
> default.
My own experimentation with IE5 indicates that it only becomes the new
default if the user has Auto-Selec
: Unicode List
Subject: RE: How-To handle i18n when you don't know charset?
Mike Brown kindly supplied some JavaScript to determine the current and
default encoding for Internet Explorer 4+.
This gives some interesting results for default encoding:
Mac IE 4.5 - utf-8
Mac IE 5 - utf-8
Win IE
1, 2000 8:36 AM
Subject: RE: How-To handle i18n when you don't know charset?
> Mike Brown kindly supplied some JavaScript to determine the current and
> default encoding for Internet Explorer 4+.
>
> This gives some interesting results for default encoding:
>
> Mac IE 4.5
Mike Brown kindly supplied some JavaScript to determine the current and
default encoding for Internet Explorer 4+.
This gives some interesting results for default encoding:
Mac IE 4.5 - utf-8
Mac IE 5 - utf-8
Win IE 5.01 - x-user-defined
Win IE 5.01 SP1 - big5
Would anyone from Microsof
[EMAIL PROTECTED] wrote:
>
> > > > Now you take the case of my friend M. Lebœuf,
> > > > whom name includes a
> > > > character not easily available in common charsets,
> > > > trying to answer such
> > > > a form included in a iso-8859-1 html page...
> > > > I am not sure he will
> > > > appreci
a Java application
with a default locale of en_US and charset Cp1252.
Leon
> -Original Message-
> From: Mike Brown [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 07, 2000 4:31 PM
> To: Unicode List
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: How-To handle i18n when y
11digitboy wrote, in a gratuitously quoted contribution:
> > > > Now you take the case of my friend M. LebÅ"uf,
> [...]
> Over here, his name looks like garbage.
> What is that? Ell ee bee something something you
> eff.
The message headers on his email included:
Content-Type: text/plain; charset
Jonathan Rosenne" <[EMAIL PROTECTED]>
> To: "Unicode List" <[EMAIL PROTECTED]>
> Sent: Friday, July 07, 2000 9:37 AM
> Subject: RE: How-To handle i18n when you don't
> know charset?
>
>
> > Unfortunately, there are many Hebrew pages wrongly
> ma
t; <[EMAIL PROTECTED]>
To: "Unicode List" <[EMAIL PROTECTED]>
Sent: Friday, July 07, 2000 9:37 AM
Subject: RE: How-To handle i18n when you don't know charset?
> Unfortunately, there are many Hebrew pages wrongly marked as 8859-1, and
many more unmarked. So letting the us
[EMAIL PROTECTED]]
> Sent: Friday, July 07, 2000 2:06 PM
> To: Unicode List
> Subject: Re: How-To handle i18n when you don't know charset?
>
>
> Michael Kaplan wrote:
> >
> > > My experimentation indicated that if the user did not have
> their browse
> Now you take the case of my friend M. Lebœuf, whom
> name includes a character not easily available in common
> charsets, trying to answer such a form included in a
> iso-8859-1 html page... I am not sure he will appreciate
> to see his name considered as garbage...
Ah, this is why UTF-8 can be
Michael Kaplan wrote:
>
> > My experimentation indicated that if the user did not have their browser
> > set to auto-select encoding, or if they manually overrode the encoding
> > selection, the form data would be sent in whatever they had chosen,
> > regardless of what charset may be in the > .
Mike Brown [mailto:[EMAIL PROTECTED]] wrote
>My experimentation indicated that if the user did not have their browser
set
>to auto-select encoding, or if they manually overrode the encoding
>selection, the form data would be sent in whatever they had chosen,
>regardless of what charset may be in t
> My experimentation indicated that if the user did not have their browser
set
> to auto-select encoding, or if they manually overrode the encoding
> selection, the form data would be sent in whatever they had chosen,
> regardless of what charset may be in the ...> in the HTML document head.
My
; <[EMAIL PROTECTED]>
Sent: Thursday, July 06, 2000 12:24 PM
Subject: RE: How-To handle i18n when you don't know charset?
>
> If I'm dealing with e-mail (POP3 and SMTP), do I necessarily
> want to respond to the user in the same charset as their original
> message to
[EMAIL PROTECTED] wrote:
> Have all the pages generated include a META-CHARSET tag
> in the HTML Header. This will insure that the browser(s)
> submit form post data in the same encoding as the
> original html page.
and Chris Wendt at microsoft.com wrote:
> Simplest is to use UTF-8 throughout and
gt; > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, July 06, 2000 12:12 PM
> > To: Unicode List
> > Cc: Unicode List
> > Subject: Re: How-To handle i18n when you don't know charset?
> >
> >
> &
just need to block browsers below version 4 or code specially for them.
-Original Message-
From: Mike Brown [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 06, 2000 11:19 AM
To: Unicode List
Subject: RE: How-To handle i18n when you don't know charset?
> What is the best way t
: Thursday, July 06, 2000 12:12 PM
> To: Unicode List
> Cc: Unicode List
> Subject: Re: How-To handle i18n when you don't know charset?
>
>
> Here are some general guidelines you might like to consider :-
>
> o Have the UI layer pass a tag identifying the character
&
Here are some general guidelines you might like to consider :-
o Have the UI layer pass a tag identifying the character encoding unless the
UI layer maps the data to one of the Unicode representations (UTF-8, UTF-16)
before passing the data on.
o Have the UI layer pass a tag identifying the loca
> 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.
> What is the best way to handle i18n when you are passed a string and
> you don't know the charset? I assume iso-8859-1 when I don't know the
> charset BUT on some Spanish environments my data is coming out
> garbage. It seems some of the characters are coming from iso-8859-2
> (at least that's m
What is the best way to handle i18n when you are passed a string and
you don't know the charset? I assume iso-8859-1 when I don't know the
charset BUT on some Spanish environments my data is coming out
garbage. It seems some of the characters are coming from iso-8859-2
(at least that's my first
23 matches
Mail list logo
