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

RE: WOFF metadata - should we require (rather than recommend) the use of UTF-8?

From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
Date: Tue, 31 May 2011 09:43:57 -0400
To: Jonathan Kew <jonathan@jfkew.plus.com>
CC: "public-webfonts-wg@w3.org Group" <public-webfonts-wg@w3.org>, "www-font@w3.org" <www-font@w3.org>
Message-ID: <7534F85A589E654EB1E44E5CFDC19E3D0BE20E1777@wob-email-01.agfamonotype.org>
+1

> -----Original Message-----
> From: www-font-request@w3.org [mailto:www-font-request@w3.org] On
> Behalf Of Chris Lilley
> Sent: Tuesday, May 31, 2011 8:11 AM
> To: Jonathan Kew
> Cc: public-webfonts-wg@w3.org Group; www-font@w3.org
> Subject: Re: WOFF metadata - should we require (rather than recommend)
> the use of UTF-8?
> 
> On Tuesday, May 31, 2011, 11:59:48 AM, Jonathan wrote:
> 
> JK> Hello WG,
> 
> JK> The current text of the WOFF spec says:
> 
> JK>    The extended metadata MUST be well-formed XML encoded in UTF-8
> JK> or UTF-16. The use of UTF-8 encoding is recommended.
> 
> JK> I'd like to suggest that we simplify this by requiring the use of
> JK> UTF-8. I'm not aware that there has been any actual use of UTF-16
> JK> for this purpose in deployed content, and mandating UTF-8 would
> JK> mean that UAs wishing to do something with the metadata (such as
> JK> present a "Font Info"  panel to the user) don't need to sniff the
> JK> data to detect the encoding and then do an appropriate conversion.
> 
> JK> So I propose replacing the text quoted above with:
> 
> JK>    The extended metadata MUST be well-formed XML encoded in UTF-8.
> 
> JK> Comments?
> 
> I agree that this would be a useful simplification and would not affect
> any deployed content.
> 
> 
> 
> 
> 
> --
>  Chris Lilley   Technical Director, Interaction Domain
>  W3C Graphics Activity Lead, Fonts Activity Lead
>  Co-Chair, W3C Hypertext CG
>  Member, CSS, WebFonts, SVG Working Groups
> 
Received on Tuesday, 31 May 2011 13:44:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:11 GMT