- From: hfhchan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Mar 2018 05:51:06 +0000
- To: public-css-archive@w3.org
> The feature would, for instance, would give copying web text with variation selectors unexpectedly differ, when pasted into some destination (as well as when the text is interpreted by crawlers and other plain-text-processing applications), from how it is visually rendered by a web browser. That happens with text-transform: uppercase too. > The author therefore expects their ideographs to always render with that specific style, as long as that style is able to be rendered. Not exactly. In China some users will prefer a more accurate representation of the text but more will prefer the characters to be rendered in the modern orthography. For many digitization projects that means building two different strings, one often using PUA (because ideographic variation selectors are not well supported). The point is, Han variants could both indicate gloss and could indicate semantic intention. The person doing the digitization may not be able to make a good guess - so they have to preserve it in some way and provide a client side toggle. Just like choosing between serif and sans-serif in a browser's reading mode. -- GitHub Notification of comment by hfhchan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1710#issuecomment-371030751 using your GitHub account
Received on Wednesday, 7 March 2018 05:51:09 UTC