Nikos Chantziaras wrote: > On 03/20/2011 03:41 PM, Jürgen Spitzmüller wrote: >> Nikos Chantziaras wrote: >>> >>> po files? Does that mean that if I build LyX without i18n support >>> (which I do; I only need English), it has an effect on the work produced >>> with it rather than just its GUI? >> >> Yes, that's correct. > > Well, IMO that should not be the case. po files are used for GUI > translations of the application. Using them for other stuff sounds like > abuse rather than use.
Using the same translations for LaTeX output and GUI is rather important IMO. It would be very confusing if you see on screen "Abbildung 5.1", but in the PDF "Grafik 5.1". Another reason for doing that is the reduced burden on the translators: This way all translations of a particular language are centralized in one .po file. I agree however that this results in two problems: 1) Stability of the translations (as mentioned by Pavel) 2) The installed (or not) .mo files influence the document output, and this is wrong, since people expect that .mo files are only used for UI translation. Problem 1) could be solved partially if the translations were marked as layout translations using the context mechanism, e.g. with [[layout]]. This could be automated with a trivial change of po/lyx_pot.py. Solving problem 2) requires that the translations are read from a different source than the installed .mo files. I suggest a new file per language, e.g. lib/layouts/translations/de. This file could be automatically created by po/lyx_pot.py. The ultimate responsibility for stable translations would then lay on those persons who remerge the translations. Georg
