W3C home > Mailing lists > Public > www-font@w3.org > April to June 2011

Re: [www-font] WOFF metadata - should we require (rather than recommend) the use of UTF-8?

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 1 Jun 2011 16:35:54 +1200
Message-ID: <BANLkTinnip6=gSw=AYdwouDetH=F3Et_fg@mail.gmail.com>
To: mpsuzuki@hiroshima-u.ac.jp
Cc: jonathan@jfkew.plus.com, public-webfonts-wg@w3.org, www-font@w3.org
On Wed, Jun 1, 2011 at 4:20 PM, <mpsuzuki@hiroshima-u.ac.jp> wrote:

> On Wed, 1 Jun 2011 16:13:12 +1200
> "Robert O'Callahan" <robert@ocallahan.org> wrote:
> >What Jonathan is actually doing is creating
> >a Javascript API that returns a string containing
> >the WOFF metadata. So that code isn't going
> >to be parsing the XML, but it does need to
> >know the encoding so the text can be correctly
> >converted to a Javascript string.
> I see. The requirement comes from non-XML field.

Not really. It's just that depending on how your software is structured, you
often need to know the encoding of text before you're ready to do XML

The description "well-formed" came from similar
> usecase?

I don't know.

>Any consumer that needs to convert the WOFF
> >metadata to some kind of string (and isn't
> >immediately parsing the XML) will have the same
> >problem.
> Indeed. A request to restrict the metadata
> content to ASCII charset is overkill?

That would prevent most of the world's languages from being used in the
metadata, so yes.

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Wednesday, 1 June 2011 04:37:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:43 UTC