W3C home > Mailing lists > Public > public-i18n-core@w3.org > October to December 2010

RE: i18n Polyglot Markup/NCRs (7th issue)

From: Eliot Graff <eliotgra@microsoft.com>
Date: Fri, 1 Oct 2010 20:45:32 +0000
To: Richard Ishida <ishida@w3.org>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <CE3A5BFD1228D84A8D9C158EEC195FD50EBC5D89@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
Hi Richard.

Changed "Character Model for the World Wide Web states" to "Character Model for the World Wide Web recommends" in Named Entity References. This is live now.

Thanks for your help.

Eliot

-----Original Message-----
From: Richard Ishida [mailto:ishida@w3.org] 
Sent: Friday, October 01, 2010 12:58 PM
To: Eliot Graff
Cc: public-i18n-core@w3.org
Subject: RE: i18n Polyglot Markup/NCRs (7th issue)

Thanks Eliot.

> Can someone please edit the information on the Internationalization 
> Comments on Polyglot Markup: HTML-Compatible XHTML Documents [2] to 
> indicate this change is made?

Done.

> (such as &#160; in the previous example); however, the Character Model 
> for the World Wide Web states that content should use the hexadecimal 
> form of

I don't know whether you want to make any more changes to this, but I'd personally be happy with "the Character Model for the World Wide Web recommends that ".

Cheers,
RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/




> -----Original Message-----
> From: public-i18n-core-request@w3.org [mailto:public-i18n-core- 
> request@w3.org] On Behalf Of Eliot Graff
> Sent: 29 September 2010 23:48
> To: Leif Halvard Silli; Henri Sivonen
> Cc: public-html; public-i18n-core@w3.org
> Subject: RE: i18n Polyglot Markup/NCRs (7th issue)
> 
> Per bug 10154  [1] I have edited the section so that it now reads as
follows:
> 
> ]]
> 8. Named Entity References
> 
> Polyglot markup uses only the following named entity references:
> 
>     * amp
>     * lt
>     * gt
>     * apos
>     * quot
> 
> For entities beyond the previous list, a polyglot document uses 
> character references. For example, polyglot markup uses &#xA0; instead of &nbsp;.
> Note that polyglot markup may use decimal values for escape characters 
> (such as &#160; in the previous example); however, the Character Model 
> for the World Wide Web states that content should use the hexadecimal 
> form of character escapes rather than the decimal form when there are both.
> [CHARMOD]
> [[
> 
> I believe that this satisfies the original request and the attempt to
indicate
> that polyglot markup may use either hexadecimal or decimal.
> 
> Can someone please edit the information on the Internationalization 
> Comments on Polyglot Markup: HTML-Compatible XHTML Documents [2] to 
> indicate this change is made?
> 
> Thanks for your help and patience.
> 
> Eliot
> 
> [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=10154
> [2] http://www.w3.org/International/reviews/1007-polyglot/
> 
> -----Original Message-----
> From: Leif Halvard Silli [mailto:xn--mlform-iua@målform.no]
> Sent: Tuesday, July 20, 2010 9:58 PM
> To: Henri Sivonen
> Cc: public-html; Eliot Graff; public-i18n-core@w3.org
> Subject: Re: i18n Polyglot Markup/NCRs (7th issue)
> 
> Henri Sivonen, Mon, 19 Jul 2010 06:35:02 -0700 (PDT):
> > Leif wrote:
> >> First of all, my comment was to Richard, who suggested that 
> >> POlyglot markup should "favor" hexadecimal NCRs.
> >
> > I think neither decimal nor hexadecimal can be preferred over the 
> > other on polyglot grounds, so the publication shouldn't prefer one 
> > over the other.
> 
> Such was my initial reaction as well. And I prefer that direction.  It
also isn't
> the purpose of Polyglot Markup to permit served as HTML things which 
> text/htmll does not open up for.
> 
> (For a reply to the document encoding issues, see separate reply.)
> --
> leif halvard silli
> 
> 
> 
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.856 / Virus Database: 271.1.1/3159 - Release Date: 
> 09/28/10
> 18:41:00
Received on Friday, 1 October 2010 20:46:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 October 2010 20:46:11 GMT