W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

RE: NFC in HTML5 (was: RE: Slots for Cyrillic Accented Vowels)

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Sat, 28 May 2011 09:01:20 -0400
To: "Michael[tm] Smith" <mike@w3.org>, "Phillips, Addison" <addison@lab126.com>
CC: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0AC29AEA07@MAILR001.mail.lan>
I'm still new to NFC/NFD things so I may be short to think about its side effects, I'm sorry in advance if that's the case, but from CJK point of view, I would like the warnings/errors limited only to id and class attributes if we were doing.

The basic idea is not to validate normalization state of any displayable contents. Attributes like alt in <img> can contain displayable contents.

If emitting warning is important for someone, I can live with warnings. But if we don't have any such situation in mind, I'd like it not to even warn.

For instance, DAISY is required to validate their contents before publish. They can create a new rule to ignore NFC warnings for contents when moving to EPUB3, but it still help them if validator does not emit warnings.


-----Original Message-----
From: public-i18n-core-request@w3.org [mailto:public-i18n-core-request@w3.org] On Behalf Of Michael[tm] Smith
Sent: Saturday, May 28, 2011 2:35 PM
To: Phillips, Addison
Cc: public-i18n-core@w3.org
Subject: Re: NFC in HTML5 (was: RE: Slots for Cyrillic Accented Vowels)

"Phillips, Addison" <addison@lab126.com>, 2011-05-26 09:31 -0700:

[quoting somebody]
> > I complained that HTML5 or validator  http://validator.w3.org/
> > *requires* NFC.
> > This might be a bug in the validator and not actually a requirement of HTML5.
> I believe that the W3C I18N WG does not support or think that it is a
> good idea for HTML5 to require NFC--but I'm not aware of any normative
> language in the HTML5 spec that requires it. This page [1] suggests that
> the normalizer was added to the validator in response to Charmod-Norm
> (which does not actually require NFC). If someone has a pointer to an NFC
> requirement in HTML5, it would be most appreciated if you could forward
> it to www-international@w3.org (or to me privately if you prefer).

For the record: There is no NFC requirement in HTML5. The fact that the
HTML5 facet of the W3C markup validator currently reports non-NFC as a
error is a bug in the validator.nu backend that the HTML5 facet relies on.

I'll fix that bug and push it to the W3C markup validator next week.

The fix is that the same message will be emitted but it will be a
warning-level message instead of an error-level one -- because I'm told
that's what would be consistent with current i18n best-practices guidance
with regard to NFC.  But if anybody thinks the HTML5 validator should not
emit a warning for non-NFC (in content as well as in attributes), please
let me know.


Michael[tm] Smith
Received on Saturday, 28 May 2011 13:01:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:07 UTC