- From: Nat McCully via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2020 05:01:19 +0000
- To: public-i18n-archive@w3.org
> It is rather a complex task as Shimono-san outlined. JLReq's character class is a combination of static property of characters and the context, where the character is used. We need to separate the context from the static property. It is a major architectural conversion which requires many rewrites. I agree that one way we can make the classifications of characters in JLReq more compatible with those in Unicode is to separate the static property so that the static properties necessary for Japanese layout can be expressed in more universal (or Unicode-compatible) terms. This would seem to mean the Unicode terms should be expanded to include such nuances for Japanese, and then for other languages with specific or unique layout rules as well. As to revising the description of how the contextual nature of Japanese layout rules work, that would seem something that can be expressed in JLReq similarly to how they are already for traditional printing and book typography. We can expand their scope into dynamic digital layout, expressing to an international audience what informs the practices of experts of Japanese layout in any medium, for example, the role of white space between characters, between lines, and flowing around objects as it relates to text. -- GitHub Notification of comment by macnmm Please view or discuss this issue at https://github.com/w3c/jlreq/issues/240#issuecomment-714912496 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 October 2020 05:01:21 UTC