Hallo Fred van Stappen, vous ecrit au Wed, 23 Feb 2022 18:02:29 +0000:
> Re-re hello. Sadly, this loses some context... > > Maybe completely stupid but could it possible that the '⑳' and '🚀' > > should first be converted into UTF16 to be rendered on a msegui > > memo-text? If yes, do you have a idea how to do this? On Linux? No. If a text rendering program (editor or whatever) cannot render a UTF-8 glyph, it's either because the character set used doesn't contain a glyph for that, as they call it, "code point", or that it doesn't even recognize that the character consists of more that 2 bytes - AFAIK UTF-8 characters can comprise as many as 5 bytes. > Hum, no it did not help, using this (in mseide editor all the > ideograms are black rectangles): > tbutton1.caption := UTF8ToUTF16( '取消所有'); My news reader's editor displays all of these correctly, BTW. Interestingly, on my machine the ideograms are rendered as open rectangles in/by the mseide editor - that probabely means that this is caused by the font used. And another editor _does_ display them correctly, even after pasting, reselecting and copying them again. I.e. that the "characters" _are_ inserted correctly, it's just the rendering function that cannot correctly display them. So the task was to find the text rendering engine used by mseide, and possibly replace it by a more capable one that can render full UTF-8. Only transforming representations will not help at all, as it looks. -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
