- From: aphillips via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Aug 2015 13:02:35 +0000
- To: public-i18n-archive@w3.org
http://www.w3.org/TR/css-fonts-3/#font-family-casing ... is an example. Actually, it is helpful to read the section holistically. We start by recommending case sensitivity. For ASCII-only namespaces, ASCII case fold matching a la HTML is suggested and you'd be most familiar with this in the platform. Most new namespaces permit Unicode identifiers. Spec authors need to be aware that, Unicode being what it is, case insensitivity is not a trivial operation. By documenting this in Charmod, we hope to avoid recreating the material each time this arises---in practice most spec authors come to their senses and use case sensitive matching as a result. When they can't (or won't be dissuaded), the documentation is ready as well. -- GitHub Notif of comment by aphillips See https://github.com/w3c/charmod-norm/issues/6#issuecomment-127597274
Received on Tuesday, 4 August 2015 13:02:37 UTC