search

notofonts / balinese

Noto Balinese
SIL Open Font License 1.1
4 stars 2 forks source link

No Kawi repha in Noto Sans Balinese #2

Closed dscorbett closed 1 year ago

dscorbett commented 6 years ago

Font

NotoSansBalinese-Regular.ttf

Where the font came from, and when

Site: https://noto-website-2.storage.googleapis.com/pkgs/NotoSansBalinese-unhinted.zip Date: 2018-04-02

Font version

Version 1.03 uh

Issue

Noto Sans Balinese does not support the Kawi repha as described in The Unicode Standard. This is presumably because OpenType has no language system tag for Kawi.

Character data

ᬭ᭄ᬫ U+1B2D BALINESE LETTER RA U+1B44 BALINESE ADEG ADEG U+1B2B BALINESE LETTER MA

marekjez86 commented 6 years ago

@dscorbett : do you know if this is the case with https://github.com/googlei18n/noto-fonts/blob/master/phaseIII_only/unhinted/otf/serif/NotoSerifBalinese/NotoSerifBalinese-Regular.otf (we renamed it from Sans to Serif)? Is the text string above a test case that we could use to check for Kawi repha support?

dscorbett commented 6 years ago

Noto Serif Balinese doesn’t support it either. The text string above, which I copied from The Unicode Standard, can be used to check for Kawi repha support, but I should clarify that the repha should not be formed by default: it should only be formed when the text is Kawi. This requires either a new OpenType language system tag (probably 'KAW ') or an ad hoc tag like 'ss01'.

punchcutter commented 6 years ago

It's possible to add a KAW tag to the lookups even though there seems to be no officially registered OpenType KAW tag. I just tried it and I can switch between default and KAW with html lang tags and it works fine.

punchcutter commented 6 years ago

Here's the quick proof of concept in Firefox with lang tags kawi_repha_test

NorbertLindenberg commented 4 years ago

The UTC has decided to remove the special handling of Kawi repha from the Unicode Standard. https://www.unicode.org/L2/L2020/20150-balinese-syllabic-category.pdf https://www.unicode.org/L2/L2020/20172.htm

dscorbett commented 3 years ago

The Unicode Standard version 14.0 still describes the Kawi repha as in previous versions. @NorbertLindenberg, do you know if that was intentional?

NorbertLindenberg commented 3 years ago

The Unicode editorial committee didn't get around to making the changes to the core specification in 14.0 and postponed them to Unicode 15.0.

simoncozens commented 2 years ago

If Kawi Repha is gone, is there still an issue here?

dscorbett commented 2 years ago

Yes, but now it is the opposite issue. The font was changed to support the Kawi repha as formerly described in The Unicode Standard, but now that Unicode no longer recommends that, it needs reverting.

verdy-p commented 1 year ago

The newly encoded Kawi script (since Unicode 15.0 released on September 2022) is separate from Balinese, due to its complex composition and layout.

So this bug may be closed or renamed for "no font for Kawi" and tracked (with a separate bug also created for "no font for Nag Mundari").

An additional tracking bug should be created for needed updates for Unicode 15.0 (Kawi, Nag Mundari, additional sets of digits in other scripts, some letters added in various scripts, addition of new emojis, new symbols, and a new CJK ideographs...). This adds 7 new blocks in the UCD (including the 2 blocks for the 2 newly encoded scripts). The summary of additions and changes is on https://unicode.org/versions/Unicode15.0.0/

simoncozens commented 1 year ago

We don't need tracking issues for Noto gaps; we track these at the Noto overview page. (There is another Python script which produces the gap list as a textual summary, but I haven't checked that in yet.) Kawi will be one of the scripts we are commissioning in 2023. It's in hand. :-)

So what we need to do here is remove the premature support for the kawi repha that was added.