Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > Angus> Unfortunately, the installed po files are called lyx14x.mo. > Angus> Moreover, the lyx executable finds these files by interogating > Angus> its own name.
> Where does this happen? The code in message.C uses > textdomain(PACKAGE); > and PACKAGE is hardcoded. Ok, so lyx.exe is looking for PACKAGE and you're suggestion will ensure that PACKAGE on Windows is simply "lyx" if I understand correctly. I assume that the final piece of the jigsaaw therefore is to make sure that the .mo files are named PACKAGE.mo. > >> I'd rather apply the following patch instead (leave lyx.exe > >> alone). What do you think of it? > Angus> Nice idea, but won't work on its own. Unless $program_suffix is > Angus> applied also to the .mo files of course. Certainly, it'll > Angus> require some testing... > Sure, that would be a 1.4.2 thing anyway. But it already works like > that in OSX, AFAIK. Magic! Angus
