GithubHelp home page GithubHelp logo

ahom's People

Contributors

punchcutter avatar simoncozens avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

ahom's Issues

Ahom i–u ligature is not always formed

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/4bff97c612daf65d4409c9ebc26dfbd6a3d83a7e/phaseIII_only/unhinted/ttf/NotoSerifAhom/NotoSerifAhom-Regular.ttf
Date: 2019-04-18

Font version

Version 2.002

Issue

U+11722 AHOM VOWEL SIGN I and U+11724 AHOM VOWEL SIGN U generally ligate, except after the consonants nga, na, da, and nya, but in Noto Serif Ahom, when a glyph comes between one of the other consonants and those two vowels, the vowels do not ligate.

I have given three example syllables. In the second, the medial -l and the -u overlap cleanly, so it might be intentional; but the Unicode proposal doesn’t say anything about that, so it might not. The third uses a vowel sequence that I don’t know is attested.

Character data

𑜁𑜟𑜢𑜤
U+11701 AHOM LETTER KHA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U
𑜀𑜝𑜢𑜤
U+11700 AHOM LETTER KA
U+1171D AHOM CONSONANT SIGN MEDIAL LA
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U
𑜀𑜦𑜢𑜤
U+11700 AHOM LETTER KA
U+11726 AHOM VOWEL SIGN E
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U

Screenshot

𑜁𑜟𑜢𑜤 𑜀𑜝𑜢𑜤 𑜀𑜦𑜢𑜤

Non-ligating U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlei18n/noto-fonts/blob/d7af81e614086435102cca95961b141b3530a027/hinted/NotoSerifAhom-Regular.ttf
Date: 2018-10-24

Font version

Version 2.001;GOOG;noto-source:20181019:f8f3770

Issue

According to L2/12-0309R, U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA represents the medial ra in two archaic ligatures of khra and phra. However, the font only forms those ligatures when 'dlig' is enabled. The ligatures should always be formed: that is why U+1171F is called “LIGATING”.

Character data

𑜁𑜟𑜇𑜟
U+11701 AHOM LETTER KHA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA
U+11707 AHOM LETTER PHA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA

Screenshot

𑜁𑜟𑜇𑜟

Inconsistent 'dist' in Ahom

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/4bff97c612daf65d4409c9ebc26dfbd6a3d83a7e/phaseIII_only/unhinted/ttf/NotoSerifAhom/NotoSerifAhom-Regular.ttf
Date: 2019-04-18

Font version

Version 2.002

Issue

'dist' kerns Ahom na and -aa apart, except when there is a mark glyph between them like -l. The mark does not modify or appear between the other two glyphs, so I’d expect it to have no effect on their spacing.

Character data

𑜃𑜡
U+11703 AHOM LETTER NA
U+11721 AHOM VOWEL SIGN AA
𑜃𑜝𑜡
U+11703 AHOM LETTER NA
U+1171D AHOM CONSONANT SIGN MEDIAL LA
U+11721 AHOM VOWEL SIGN AA

Screenshot

𑜃𑜡 𑜃𑜝𑜡

Ahom spacing vowel signs are not always spacing

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/4bff97c612daf65d4409c9ebc26dfbd6a3d83a7e/phaseIII_only/unhinted/ttf/NotoSerifAhom/NotoSerifAhom-Regular.ttf
Date: 2019-04-18

Font version

Version 2.002

Issue

After the glyphs medialLigaRa_ahom, khra_ahom, phra_ahom, and t_ja_ahom, vowel signs that should be spacing are not spacing.

Character data

𑜀𑜟𑜢𑜂
U+11700 AHOM LETTER KA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA
U+11722 AHOM VOWEL SIGN I
U+11702 AHOM LETTER NGA
𑜁𑜟𑜢𑜂
U+11701 AHOM LETTER KHA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA
U+11722 AHOM VOWEL SIGN I
U+11702 AHOM LETTER NGA
𑜇𑜟𑜢𑜂
U+11707 AHOM LETTER PHA
U+1171F AHOM CONSONANT SIGN MEDIAL LIGATING RA
U+11722 AHOM VOWEL SIGN I
U+11702 AHOM LETTER NGA
𑜅𑜊𑜢𑜂
U+11705 AHOM LETTER ALTERNATE TA
U+1170A AHOM LETTER JA
U+11722 AHOM VOWEL SIGN I
U+11702 AHOM LETTER NGA

Screenshot

𑜀𑜟𑜢𑜂 𑜁𑜟𑜢𑜂 𑜇𑜟𑜢𑜂 𑜅𑜊𑜢𑜂

U+1171E AHOM CONSONANT SIGN MEDIAL RA blocks ta–ja ligature

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/37b29f06fd0e65633ab7201555c28710888b45a1/hinted/ttf/NotoSerifAhom/NotoSerifAhom-Regular.ttf
Date: 2020-12-23

Font version

Version 2.003

Issue

U+1171E AHOM CONSONANT SIGN MEDIAL RA blocks the ligature between U+11705 AHOM LETTER ALTERNATE TA and U+1170A AHOM LETTER JA. Cf. U+11726 AHOM VOWEL SIGN E, another reordering mark, which does not block the ligature.

Character data

𑜅𑜞𑜊
U+11705 AHOM LETTER ALTERNATE TA
U+1171E AHOM CONSONANT SIGN MEDIAL RA
U+1170A AHOM LETTER JA
𑜅𑜦𑜊
U+11705 AHOM LETTER ALTERNATE TA
U+11726 AHOM VOWEL SIGN E
U+1170A AHOM LETTER JA

Screenshot

𑜅𑜞𑜊 𑜅𑜦𑜊

Missing additional Ahom characters

Defect Report

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://notofonts.github.io/fonts/NotoSerifAhom/full/ttf/NotoSerifAhom-Regular.ttf
Date: 2022-07-04

Font Version

v2.005

Issue

As of Unicode version 14.0, 7 new characters were added to the Ahom Unicode block, these characters are not covered in Noto Serif Ahom per 04 July 2022.

Character data

11740 𑝀 AHOM LETTER CA
11741 𑝁 AHOM LETTER TTA
11742 𑝂 AHOM LETTER TTHA
11743 𑝃 AHOM LETTER DDA
11744 𑝄 AHOM LETTER DDHA
11745 𑝅 AHOM LETTER NNA
11746 𑝆 AHOM LETTER LLA

Reference

http://unicode.org/charts/PDF/U11700.pdf

Screenshot

image

Ahom i–u ligature is still not always formed

Font

NotoSerifAhom-Regular.otf

Where the font came from, and when

Site: https://github.com/notofonts/ahom/releases/tag/NotoSerifAhom-v2.006
Date: 2023-03-24

Font version

Version 2.006

Issue

Issue #12 still exists for syllables where the base letter and the ⟨-i, -u⟩ sequence are separated by U+1171E AHOM CONSONANT SIGN MEDIAL RA or by multiple code points.

Rather than extending the fix implemented for that issue, I recommend a two-part solution. First, do the ligation after reordering instead of in 'ccmp', so that you don’t have to handle U+11726 AHOM VOWEL SIGN E explicitly. Second, use a mark set in the ligature lookup, so that irrelevant marks like U+1171D are skipped.

Character data

𑜀𑜞𑜢𑜤
U+11700 AHOM LETTER KA
U+1171E AHOM CONSONANT SIGN MEDIAL RA
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U

𑜀
U+11700 AHOM LETTER KA
U+1171D AHOM CONSONANT SIGN MEDIAL LA
U+11726 AHOM VOWEL SIGN E
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U

Screenshot

𑜀𑜞𑜢𑜤
𑜀

Inconsistent kerning of U+11705 AHOM LETTER ALTERNATE TA

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlefonts/noto-fonts/blob/4bff97c612daf65d4409c9ebc26dfbd6a3d83a7e/phaseIII_only/unhinted/ttf/NotoSerifAhom/NotoSerifAhom-Regular.ttf
Date: 2019-04-18

Font version

Version 2.002

Issue

The vowel sign e is kerned with the alternative ta but not with ligature of alternative ta and ja.

Character data

𑜅𑜦
U+11705 AHOM LETTER ALTERNATE TA
U+11726 AHOM VOWEL SIGN E
𑜅𑜦𑜊
U+11705 AHOM LETTER ALTERNATE TA
U+11726 AHOM VOWEL SIGN E
U+1170A AHOM LETTER JA

Screenshot

𑜅𑜦 𑜅𑜦𑜊

I+U does not form ligature in certain contexts

I have checked the Noto Serif Ahom font in several different applications (Microsoft Word, Libre Office, Facebook - using Chrome, Facebook - using Firefox) and found some implementation issues that differ from one application to another.

One issue, however, is common to all and is therefore assumed to be a 'bug' with the Noto Serif Ahom font that needs to be fixed.

It is described as follows:

The combination of AHOM VOWEL SIGN I (U+11722) and AHOM VOWEL SIGN U (U+11724) when following certain consonants NA NYA DA NGA, does not appear with the middle of the AHOM VOWEL SIGN I vowel directly above the vertical portion of the AHOM VOWEL SIGN U

The combination of AHOM VOWEL SIGN I and AHOM VOWEL SIGN U forms a ligature except after the four named consonants, and this is happening correctly in 5 of the 6 applications tested (not In Microsoft word). However the letters AHOM VOWEL SIGN I and AHOM VOWEL SIGN U need to be kerned when they are in combination with the four consonants NA, NYA, DA and NGA.

Please let me know if more information is needed.

Testing the Ahom font in different applications - 20221107.pdf

Wrong code point for Ahom glyph u11714.alt

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlei18n/noto-fonts/blob/d7af81e614086435102cca95961b141b3530a027/hinted/NotoSerifAhom-Regular.ttf
Date: 2018-10-24

Font version

Version 2.001;GOOG;noto-source:20181019:f8f3770

Issue

According to L2/12-0309R, the glyph called u11714.alt in Noto Serif Ahom “is a font variant of AHOM LETTER GA (U+11714)”. However, U+11714 is AHOM LETTER DHA: the proposal got the code point wrong, and the glyph should be a stylistic alternative of u11715. I know this is a form of ga and not dha because the earlier version of the proposal calls it GA and writes the code point consistently.

Character data

𑜔𑜕
U+11714 AHOM LETTER DHA
U+11715 AHOM LETTER GA

Screenshot

With 'salt':
𑜔𑜕

Inconsistent kerning in Ahom

Font

NotoSerifAhom-Regular.ttf

Where the font came from, and when

Site: https://github.com/googlei18n/noto-fonts/blob/d7af81e614086435102cca95961b141b3530a027/hinted/NotoSerifAhom-Regular.ttf
Date: 2018-10-24

Font version

Version 2.001;GOOG;noto-source:20181019:f8f3770

Issue

Ahom na and -i are kerned apart, except when the syllable also includes -u. The -u does not modify or appear between the other two glyphs, so I’d expect it to have no effect on their spacing.

Character data

𑜃𑜢
U+11703 AHOM LETTER NA
U+11722 AHOM VOWEL SIGN I
𑜃𑜢𑜤
U+11703 AHOM LETTER NA
U+11722 AHOM VOWEL SIGN I
U+11724 AHOM VOWEL SIGN U

Screenshot

𑜃𑜢 𑜃𑜢𑜤

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.