Re: [jlreq] Digital native version of JLReq, discuss goals and changes from the current version (#281)

> diagram describing engine issue with ambiguous Unicode that is not solved with UAX50 but could be solved with CDEF?

On this  point is there anything that JLReq TF can do to solve the issue? These are a part of 9 code points where many text editing applications defaults to proportional while they are also used in Japanese layout.

Unicode|Character name
-- | --
U+2018 | LEFT SINGLE QUOTATION MARK
U+201C | LEFT DOUBLE QUOTATION MARK
U+2019 | RIGHT SINGLE QUOTATION MARK
U+201D | RIGHT DOUBLE QUOTATION MARK
U+2010 | HYPHEN
U+2013 | EN DASH
U+2014 | EM DASH
U+2025 | TWO DOT LEADER
U+2026 | HORIZONTAL ELLIPSIS



-- 
GitHub Notification of comment by kidayasuo
Please view or discuss this issue at https://github.com/w3c/jlreq/issues/281#issuecomment-903214029 using your GitHub account


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

Received on Sunday, 22 August 2021 05:02:44 UTC