Mongolian example

[davelab6]

I understand encoding of Mongolian isn't fully decided yet, but with the idea that ot-wasm allows us to defer deciding The One Right Best Way, I wonder if @simoncozens can do better than current Noto by doing it different ways ...

I post this following a chat with @aaronbell

[simoncozens]

Maybe, I would need a conversation with @lianghai to understand how it's all supposed to work and the current limitations.

[lianghai]

I understand encoding of Mongolian isn't fully decided yet, …

Not true.

The Unicode Standard has decided to align with China’s national standard based on my proposal L2/24-180 two years ago: https://unicode.org/L2/L2024/24159.htm#180-A3, which is why the Mongolian UTN is now referenced in both the core spec (https://unicode.org/versions/Unicode17.0.0/core-spec/chapter-13/#G27803) and the code chart (https://unicode.org/charts/PDF/U1800.pdf).

…, but with the idea that ot-wasm allows us to defer deciding The One Right Best Way, I wonder if @simoncozens can do better than current Noto by doing it different ways ...

The current version 3 of Noto Sans Mongolian was produced around that time (2023-2024) in sync with the Unicode Standard’s direction: https://github.com/notofonts/mongolian/releases. This is already “The One Right Best Way”.

The OT Wasm is probably not relevant to Mongolian. Mongolian’s problem has always been about how to consistently (between vendors) encode and shape text. There’s no actual shaping challenges. The Mongolian UTN provides clarification about the encoding-shaping model and a reference implementation in FEA: https://github.com/Kushim-Jiang/mongfontbuilder.

cc @Kushim-Jiang

[aaronbell]

Thanks for the clarification and info @lianghai! Clearly I missed the settling of the approach. It sounds like Mongolian wouldn't necessarily benefit from a wasm implementation.