- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Jul 2021 04:00:02 +0000
- To: public-i18n-archive@w3.org
I think features that do not affect the normal text flow should be available in plain text (for example, [adjustment of adjacent punctuation marks](https://w3c.github.io/clreq/#h-adjustment_of_adjacent_punctuation_marks) in Chinese), but the premise is that the text has the correct language metadata, since the default behavior of the same text in different language environments may be different. 1. For features such as images, videos, and forms are no longer text, so markup language may be required. 2. About metadata such as language and direction markers, although they can work in plain text to a certain extent (like using Unicode language tag characters and UBA markers), there are many problems, so it is usually recommended to use a markup language. 3. For features like ruby, although they're text, they are not in the "normal text flow", so I think they still need to be tagged. The markup language is not necessarily HTML/XML, it can also be other lightweight markup languages, so the cost of manual tagging may be reduced. -- GitHub Notification of comment by xfq Please view or discuss this issue at https://github.com/w3c/jlreq/issues/286#issuecomment-877558687 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 July 2021 04:00:05 UTC