Unify Intl APIs in gfx/thebes/gfxScriptItemizer.cpp
Categories
(Core :: Internationalization, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox96 | --- | fixed |
People
(Reporter: gregtatum, Assigned: allstars.chh)
References
Details
(Whiteboard: [i18n-unification], [i18n-unification-help-wanted] )
Attachments
(4 files)
Work: Small
What it is: uscript_getScriptExtensions
Updated•4 years ago
|
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
| Assignee | ||
Comment 1•4 years ago
|
||
Hi Greg
I notice in Gecko we already have mozilla::unicode::Script defined in https://searchfox.org/mozilla-central/source/intl/unicharutil/util/nsUnicodeScriptCodes.h, though it is generated by script https://searchfox.org/mozilla-central/source/intl/unicharutil/tools/genUnicodePropertyData.pl.
Should I reuse the mozilla::unicode::Script enum in the Mozilla::intl ? Or should I define new enums in intl/component/src/ ?
This should be the Script defined in ICu4X in https://github.com/unicode-org/icu4x/blob/bf4b5dfc496f5580ebd8d8d5610b3e4bbacee625/components/properties/src/props.rs#L258
| Reporter | ||
Comment 2•4 years ago
|
||
Sorry for the delay in the response, I was out of office last week.
It seems reasonable to re-use the nsUnicodeScriptCodes.h enum for now. I don't believe we've scoped out removing that build script, so it should be fine to just get rid of the ICU specific include here. In the if/when we look at unifying the mozilla::unicode::Script it should be obvious where the includes need to be updated.
| Assignee | ||
Comment 3•4 years ago
|
||
| Assignee | ||
Comment 4•4 years ago
|
||
| Assignee | ||
Comment 5•4 years ago
|
||
| Assignee | ||
Comment 6•4 years ago
|
||
Comment 8•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/c23e1bc87eb8
https://hg.mozilla.org/mozilla-central/rev/6d96c65d9186
https://hg.mozilla.org/mozilla-central/rev/b501cf0be072
https://hg.mozilla.org/mozilla-central/rev/701d8641d9f7
Description
•