- From: asmusf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Apr 2016 15:17:32 +0000
- To: public-i18n-archive@w3.org
It's strictly speaking something like "encoded text elements". Otherwise you'd be working with two meanings of "character" which can get confusing. If you make it an example instead of a general statement, then you could use the word letter. However, let's step back a bit. Repeating the perv. sentence using different words is appropriate, because it emphasizes the point. The surprise is strongest when it comes to identifiers. So, let's use that case to emphasize the general statement. While we are at it, let's take out the two insertions that clutter up the first sentence to streamline it. "Applying a Unicode Normalization Form does not guarantee that two identical-looking strings always use the same underlying Unicode code points. This is sometimes surprising to software developers and others who expect that applying Unicode Normalization, will make sure that two different strings can never result in two identical-looking identifiers, for example. Normalization is, at best, only part of a string matching solution." -- GitHub Notification of comment by asmusf Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/86#issuecomment-206422692 using your GitHub account
Received on Wednesday, 6 April 2016 15:17:35 UTC