Different behaviors of glyph connections when typesetting mixed languages: comparing latin+Arabic and latin+Mongolian #1728
Unanswered
mongol-surah
asked this question in
Q&A
Replies: 1 comment
-
I rerun the examples with
Debug info:
Mongolian:
Debug info:
It is apparent that the tokenization mechanism in SILE treats Mongolian and Arabic inputs differently, as mentioned in #1726. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, the SILE community!
I was trying to typeset some Mongolian texts using SILE. When a Mongolian word is preceded by a Latin character like this:
\font[family="Mongolian White"]{AᠳᠤᠷᠠA}
, the connectivity between Mongolian characters is broken: . This is fair, since that's what harfbuzz will output, if the string "AᠳᠤᠷᠠA" as a whole is sent to harfbuzz.However, the breaking of connectivity does not happen for the latin+arabic mixture. The instruction
\font[family=Arial,size=16pt,direction=rtl]{AفـانيA}
produces . The characters are connected very well. Harfbuzz doesn't produce connected glyphs (by design) if the whole string "AفـانيA" is fed in. Harfbuzz outputs this: where the characters are not connected to each other.My question is, does SILE do some itemizations for Arabic input before sending it to harfbuzz, while doesn't do itemization for Mongolian input? Why does SILE show different behaviors for the connectivities of Arabic and Mongolian inputs? Thanks!!
Beta Was this translation helpful? Give feedback.
All reactions