Benoit KUGLER

Hi @MayankFawkes, Thank you for your question. As you might have guessed, you encounter a typical text shaping problem. Several languages/scripts, like Arabic or Hindi, require complex layout rules to...

> I was wondering if typesetting would use the semi-standard libraries for [languages](https://pkg.go.dev/golang.org/x/text/language#Tag) and [scripts](https://pkg.go.dev/golang.org/x/text/language#Script). Hum.. I'm not sure what would be the complications on the various generated tables. We...

> `opentype/api/metadata.Describe` prefers returning a family name that fits into the WWS model, I'm not sure I'm following you here. Could you explain why would be the alternatives ?

> We encountered this issue at multiple levels in recent explorations: > > * In the context of the Apple SF system fonts, which only list the rounded, arabic etc...

> This is probably user-error and the intended usage of language.Language is to use language.NewLanguage to canonicalize the string before assigning it to `SegmentProperties.Language`. Unfortunately, it's easy to misuse this...

> How do you feel about something like this instead? Looks great. It would not be backward compatible though, so I'm not sure how much this change is worth doing....

> As an aside (which I'm happy to split into its own issue if need be), the handling of language.Script is also case-sensitive, but language.ParseScript doesn't do any normalization. So...

Huh.. We could do it, but it would involve a new API for loading collections, since we would need to track the shared tables. And the `NewFont` constructor would have...

Here hare some numbers to illustrate @dominikh point . Details /usr/share/fonts/opentype/noto/NotoSansCJK-Bold.ttc 10 faces CFF : 16023 KB -> used 10 times hmtx : 262 KB -> used 10 times vmtx...

Hum.. I was not aware the same Unicode code point may have different glyphs presentation depending on the language. Have you some examples of fonts and languages that have this...