Angus Leeming <leeming <at> lyx.org> writes: > > But does Pango require the use of Unicode? LyX isn't there yet. >
I did some stuff using gtk and pango, and never worried about that. Neither in the editor, nor in a glade file or wherever. The only thing is that I needed to make my xml files utf8 encoded since I did not do any conversion code. I could have done so, but I didn't see a reason. The big benefit of UTF 8 is that you can use it for everything. No need to switch or determine a special encoding. Another big benefit is that it keeps simple while things are simple. The Text I am writing here could actually be valid UTF 8 encoded!! The only differences come with the foreign characters. It should be quite easy (and not very slow) to convert between lyx's encoding to UTF-8. There are libs for that, and I think gtk has some. Maybe even the STL. I don't know, because I never used something but UTF 8 and the principle "what I type in a program will be the output" before that. I can type Germand and Japanese side by side if I want to in Gnome (but not in Lyx -.-). The Lyx core will not need to know about UTF-8... I don't know the internals very well, maybe we can even make the buffer contain UTF-8 data? That would be cool. But absolutely not neccessary for pango, which is only meant as a gtk-specific way of handling fonts, just as the QT frontend uses it's qt-specific way. > > It would be nice if someone could confirm the bug for their setups. > > Confirmed. I get a crash with e-acute. > Thanks for confirming. That lessens the probability of me having configured something badly. Thanks for reading my oversized posts... Greetings, Andreas
