Your presentation on LibreOffice code

[Jan-Marek Glogowski]

Sorry for the late reply. Had some mail problems.

Am 16.03.20 um 22:20 schrieb Arvind Kumar:
> Jan-Marek Glogowski <glogow at fbihome.de <mailto:glogow at fbihome.de>> wrote:
> 
>> If you want to generate single glyphs from multiple keystrokes, then you
>> should have a look into input method handling (IM), like ibus or
> fcitx, which
>> is normally used to type complex-glyph based languages, like Chinese.
> 
> I know this is outside LO, but is this as easy as editing a file and
> adding my mapping, and if so, is there an example I can look at?

Hmm - I know fcitx uses some kind of tables for the direct mappings. My
Debian has fcitx-table-emoji. Guess that would be the easiest starting
point, if your languages typed letters don't depend already existing
previous or next letters and just need some keys to code point mapping.

>> Hard to say, if this is a general problem of your font or a bug in LO or
>> just caused by your changes to the VCL gtk3 plugin key handling code
> in LO.
>>
>> If you have some other working example document, like a UTF-8 encoded
>> text file, which you know is displayed correctly in some Gtk
>> application, than you could copy and paste that text into Writer and
>> then select your font. That should already work, without any code changes.
> 
> I just tested this and it works very well and correctly shows my text!
> So it now comes down to the input mechanism and making it work for the
> keystrokes. LayoutText is not the right place?

Yup. No LO changes needed, unless you find some bug.

[some unicode politics, I can't do anything about]

> Another problem is that even GTK's code tests for unicode
> compatibility and will not accept "non-standard" strings, for example,
> file names not recognized as unicode compatible.

I'm not sure I understand you. Is this a Gtk-only problem, so qt5 or kf5
works? I'm not aware of any restriction regarding file names. Sure Gtk+
and Qt5 default to utf-8 encoding, but that should just work. Or do they
reject PUA code points (which IMHO makes sense, because a filename has
no font).

>From the filesystem POV it's all just bytes. Encoding depends on your
locale, like C.UTF-8. There is
https://bugs.documentfoundation.org/show_bug.cgi?id=125995 as a result
of this IMHO sane UTF-8 default.