Rob Bochan <[EMAIL PROTECTED]> writes: > Some more info. I was just able to get fvwm95 to start properly, but I had to > reconfigure locales, adding all the EN_US entries available (as per bug > #278775). This was a fresh netinstall of Etch, and the default locales setup > apparently doesn't allow fvwm95 to start properly, so I don't know if this is > an issue with locales or fvwm95.
It's an issue with fvwm95, in that fvwm95 doesn't understand utf-8 locales at all. Unfortunately, fixing this is beyond me. I'm thinking of putting together a package that contains a configuration for fvwm2 that makes it look like fvwm95, and then transitioning fvwm95 to that. This separate wm should die off. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
