FYI, I was actually referring to our application's own language/charset request
mechanism. Due to roaming, we can't rely on browser settings. So we have user
preferences, as well as single logon overrides. But it depends how our
customers (ISPs, companies) set up their servers. If they don't want to serve
UTF-8, then their customers cannot request it. Internally, however, info is
handled in Unicode, via Java methods.
Stephen Holmes wrote:
> Unicode (UTF-8) certaintly appears in my IE 5.0 and support for UTF-8 is documented in the MSDN content.
> "Christopher John Fynn" <email@example.com> wrote:
> > A. Vine <firstname.lastname@example.org> wrote:
> > >I _can_ serve UTF-8 to folks in HTML pages should they choose UTF-8
> > > as their preferred charset (providing our customers gave their customers
> > that
> > > option). But as it turns out, very few folks actually _do_ choose UTF-8,
> > or
> > > request multilingual capabilities which results in our serving them UTF-8.
> > > I think we're moving in that direction. But there's a lot of old HTML
> > browsers
> > > out there, and as we're trying to reach a broad audience, we do a lot of
> > > conversion from our internal Unicode into other charsets.
> > It's not even just old browsers - IE 5 has a large range of languages you
> > can set in
> > order of preference for requesting content but it has no option for UTF-8 so
> > is never
> > going to request it even though it can display UTF-8 text correctly for many
> > languages
> > and scripts.
> > - Chris
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:56 EDT