- From: Behnam Esfahbod via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Jun 2017 22:16:07 +0000
- To: public-i18n-archive@w3.org
Yeah. These code-points, specially U+FDF2, do appear in text because of a valid reason: wanting fallback to next font with the "ligature" (sign, I would call them myself), instead of falling back to text representation. And, when doing that, I think we actually can enlist the codepoints (the ranges) of the actual *ligature* characters, which we don't expect in text at all, and no font is necessitated to support them. This would make it clear what's *out of the loop* more easily for everyone: this spec and font developers. And, "Currency" is a special case to talk about in general, which can cover the case for RIAL (and AFGHANI). -- GitHub Notification of comment by behnam Please view or discuss this issue at https://github.com/w3c/alreq/issues/128#issuecomment-311501774 using your GitHub account
Received on Tuesday, 27 June 2017 22:16:13 UTC