On Fri, 28 Sep 2007 19:12:11 +0200 Jesús Guerrero <[EMAIL PROTECTED]> wrote:
Also, the localization functions are really strange. Fvwm supports localization via gettext. No need to have separate menu files for each language. Just create .po files for each language, and then use $[gt.Office], for example, instead of the menu label "Office". If there is a translated string in the po file you use, then it will be used. If not, the sane default "Office" will be used instead. A big big big flaw is that the current system it implements is not able to load any menu file at all unless your lang is en or de. That is why it doesn't load for me. The function to set lang wouldn't be necessary if this was implemented using gettext instead, but it not, a default value should be used (probably en) if your lang is not supported. -- Jesús Guerrero <[EMAIL PROTECTED]>
