Thanks to attendees to the “Issues in the Font Rendering Stack for
Non-Latin Scripts BoF”!
For non-latin script users there are many pitfalls and there is much
work left to do for making their life easier.
pleas find attached the gobby notes, which are also on gobby.debian.org.
Max
* install gobby
* gobby.debian.org
* debconf18/bof/non-latin-issues
Issues with non-latin script
Font rendering issue(s)
* CJK Han unification
right to left writing
-
Good support in QT and GTK. Not so where they are not used. Specifically: not
in a terminal.
pipe into bidiv
r2l (bidirectional) - hebrew, arabic, farsi, urdu and others
Not only R2L - Some glyphs have to modify (ligate with?) the preceding one.
harfbuzz - Can properly render multiple glyphs sorting out fine positioning
between them. Requires the information from the fonts
Rubyscript(?) is an aid to pronunciation that adds aids for pronuntiation.
Furigana(?) in Japanese is fully supported. This seems to be a tension issue
in Taiwan, it's hard to find proper typesetting. Contact should be made for
collaboration! Norbert Preining offers his support. (Zhuyin 注音符號)
Example: W3C Ruby support: http://rocksaying.tw/archives/2912837.html
Question - Is there a standard way to encode Furigana/Rubyscript i.e. to UTF8,
into a stream of characters?
Linux kernel console
* Useless for CJK, at least
(Workarounds: CJKTTY patch, fbterm, ... or kmscon -- Linux KMS/DRM based
virtual Console Emulator?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700210 )
(reports of reproducible-builds issues derived from RTL - don't remember
exactly what triggered them..?)
Another issue to discuss - Input methods... fcitx (chinese development) has
excellent support. The mixes between keyboard layouts and input methods leads
to really confusing situations.
signature.asc
Description: OpenPGP digital signature