Re: [i18n-discuss] Further comments on Unicode FAQ: Unicode and the Web (#26)

Thank you for your input. Very valuable. Here are some notes:

[1] done (in our draft version, pending review by Unicode edcom) -- please suggest phrasing for other "naked" links you'd like to see replaced; 

[2] Again, specific wording would help; the tenor looks fine.  About the word "Yes". Most of the FAQ used to be written with Yes/No as the first word in each answer. We are trying to remove some of the "chattiness" of the FAQ, but in some cases we may have gone too far (or would need different wording for a question).

I've taken the tail end of your comment: "Unicode greatly simplifies the storage of multilingual data, since most non-Unicode encoded database data will be in multiple languages and code pages, and managing or extending that is a pain in the neck. That all goes away with Unicode encoded databases." and will use that verbatim unless better instructions.

[3] Very nice rewrite. I added it to our private review draft, with a fourth paragraph: "Use of NCRs interferes with automatic normalization applied by some editors. This can be desirable in documents that discuss normalization and need to show examples, but should otherwise be avoided." 

It seems to me that the interaction is worth pointing out, so it can be avoided. And while we are at it, we might mention the sole known use case in passing.

[4] We do not have a dedicated FAQ for e-mail. In fact, there used to be much more and we deleted it, because it seemed outdated. We are currently looking for input on what issues should rise to the level that we mention them here or any other FAQ page. BTW, just pointing readers to other standards is fine -- but the group isn't sure what the message should be.

At irregular intervals the contents of the like at the top of your comment will be updated so anyone can check the status of the private draft.

-- 
GitHub Notification of comment by asmusf
Please view or discuss this issue at https://github.com/w3c/i18n-discuss/issues/26#issuecomment-1219472607 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 18 August 2022 13:08:33 UTC