<html><head></head><body><div class="yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div><div>Jan-Marek Glogowski <<a href="mailto:glogow@fbihome.de" rel="nofollow" target="_blank">glogow@fbihome.de</a>> wrote:</div><div><br></div><div dir="ltr">> If you want to generate single glyphs from multiple keystrokes, then you <br></div><div dir="ltr">> should have a look into input method handling (IM), like ibus or fcitx, which</div><div dir="ltr">> is normally used to type complex-glyph based languages, like Chinese.<br></div><div dir="ltr"><br></div><div dir="ltr" data-setdir="false">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?</div><div dir="ltr"><br></div><div dir="ltr">> Hard to say, if this is a general problem of your font or a bug in LO or<br></div><div dir="ltr">> just caused by your changes to the VCL gtk3 plugin key handling code in LO.<br></div><div dir="ltr">><br></div><div dir="ltr">> If you have some other working example document, like a UTF-8 encoded<br></div><div dir="ltr">> text file, which you know is displayed correctly in some Gtk<br></div><div dir="ltr">> application, than you could copy and paste that text into Writer and<br></div><div dir="ltr">> then select your font. That should already work, without any code changes.</div><div dir="ltr"><br></div><div dir="ltr" data-setdir="false">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?<br></div><div dir="ltr"><br></div><div dir="ltr">> Maybe try contact either people from unicode.org or icu-project.org?<br></div><div dir="ltr">> They should eventually be able to assign some code point ranges for your<br></div><div dir="ltr">> language / glyphs, so other programs can also represent your glyphs<br></div><div dir="ltr">> correctly. I have no idea, how the unicode people work, but especially<br></div><div dir="ltr">> if you have an actively used language, that would be my way to go.<br></div><div dir="ltr"><br></div><div dir="ltr" data-setdir="false">Unicode is the problem! In the early 1990s, UTF-8 encoding started off as 31-bit encoding scheme. IEEE came up with a 32-bit scheme. Unicode should have done the same thing. It was well intentioned when it started off and was supposed to accommodate all languages. Today, Unicode Consortium is run by people from large firms who, over time, restricted Unicode to 16 and 20-bits and there is no space for every character. Of course, Unicode neatly fits in with the ancient DBCS technology of Microsoft. 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. <br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><span>Thanks!</span></div><div dir="ltr" data-setdir="false"><span></span><br></div><div dir="ltr" data-setdir="false">-a<br></div></div><div id="ydpc0a7e7b5yahoo_quoted_4591765290" class="ydpc0a7e7b5yahoo_quoted"><div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"> </div> </div></div></body></html>