Re: FVWM: UTF-8 support in fvwm
when are we going to get UTF-8 support in fvwm2? I give a font which uses the 10646 encoding, but fvwm uses the font without rendering the UTF-8 accented characters which I use for Esperanto. I appreciate that this might take a lot of doing, so I am not holding my breath! (I think that the original poster has solved this - but it might be handy for someone else to know...) I certainly use exotic glyphs in my menus etc with no problem. What I did find was that it was important to ensure that the text editor saving the config file was using the correct encoding. I used scite - which the first few times seemed to save another encoding until I realised what was going on. The other matter is whether or not the font actually includes the glyphs which you require. If you are looking through the table in the gtk font viewer, by default it shows all glyphs in the table regardless of whether or not they are actually present in the font being examined. You have to set a particular option in order to see only the glyphs which are actually in the current font - which is a great disappointment when the symbols which you require then disappear... Hope that helps, Richard.
Re: FVWM: UTF-8 support in fvwm
Sian Mountbatten poenik...@fastmail.co.uk writes: when are we going to get UTF-8 support in fvwm2? I give a font which uses the 10646 encoding, but fvwm uses the font without rendering the UTF-8 accented characters which I use for Esperanto. I appreciate that this might take a lot of doing, so I am not holding my breath! As far as I know, utf-8 works. Although being from the USA, I've never had occasion to even try it. You need to post some details about what you tried, the version of fvwm you are using, etc. -- Dan Espen
Re: FVWM: UTF-8 support in fvwm
As far as I know, utf-8 works. Although being from the USA, I've never had occasion to even try it. You need to post some details about what you tried, the version of fvwm you are using, etc. It's my fault, I was answering via Roundcube which doesn't work with the mailing lists very well. The problem was most likely because of a mistake in XLFD string which led to using a fallback font. That, or a font without needed glyphs. Solved by using xft:Font Name:size=somesize instead.
