Clean up in IsComplexASCIIChar and IsComplexChar in nsLineBreaker
Categories
(Core :: Internationalization, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: m_kato, Assigned: m_kato)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Two issues.
- IsComplexASCIIChar is AL and NU. We can add IS and QU too.
- IsComplexChar is broken. It returns same result of IsComplexASCIIChar. So we can remove it.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
mCurrentWordContainsComplexChar
and wordHasComplexChar
seem to be used
whether a word is non-breakable character. I would like to rename it for clean
up.
Also, nsLineBreaker
has a fast path if character is ASCII, alphabet (AL) and
number (NU). But IS and QU are also unbreakable. So we should add it by using
simple table.
Comment 3•1 year ago
|
||
Backed out changeset d13725dac1c1 (Bug 1856267) for causing failures in markup-src-1.html CLOSED TREE
Log: https://treeherder.mozilla.org/logviewer?job_id=432533160&repo=autoland&lineNumber=22669
Backout: https://hg.mozilla.org/integration/autoland/rev/e8068cf4fa90028d853f6f177070f15863f02b5e
Assignee | ||
Comment 4•1 year ago
|
||
Even if ASCII, old line segmenter rules aren't compatible with UAX#14.
layout/reftests/line-breaking/markup-src-1.html
runs on old segmenter prefs,
so we should use old non-breaking conditions for it with old segmenter.
Also, if word-break is break-all, we might have break opportunity for AL, NU,
IS, and QU combinations. So we should use ICU4X segmenter if break-all.
Depends on D190379
Assignee | ||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/776ad5f12955
https://hg.mozilla.org/mozilla-central/rev/3cbd51f1e91c
Description
•