W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > July to September 2006

Re: allow US-ASCII as well as UTF-8 for mobileOK documents?

From: Dan Connolly <connolly@w3.org>
Date: Thu, 17 Aug 2006 10:40:41 -0500
To: Sean Owen <srowen@google.com>
Cc: public-bpwg-comments@w3.org
Message-Id: <1155829241.14982.80.camel@localhost.localdomain>

On Thu, 2006-08-17 at 10:21 -0400, Sean Owen wrote:
> Dan we discussed character encoding and US-ASCII at our weekly call.
> One concern was that several Japanese phones would not recognize the
> US-ASCII encoding when called "US-ASCII" and would default to
> Shift_JIS instead of UTF-8. The same may be true of other handsets.
> 
> I think the position of the group would be that a document encoded as
> US-ASCII is also encoded as UTF-8 and so should be declared as "UTF-8"
> instead. We'd not want to tell people to assume that phones know what
> US-ASCII is, as it seems there is enough lack of support to puncture
> that assumption.

Yes, I see. Thanks for looking into it.

> Regards,
> Sean

> > On 7/27/06, Dan Connolly <connolly@w3.org> wrote:
> > > I see:
> > >
> > > "If the request response does specify a character encoding but it is not
> > > "UTF-8", FAIL"
> > >  -- http://www.w3.org/TR/mobileOK/#id4485785
> > >
> > > How about US-ASCII? especially since you can treat US-ASCII
> > > as UTF-8 and preserve the meaning of the bytes.

-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Thursday, 17 August 2006 15:40:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 12:13:30 GMT