Here is a copy of the comment I added there: http://bugzilla.lyx.org/show_bug.cgi?id=750
I attached an old patch from dekel too, since I think it is relevant. JMarc ------- Additional Comment #2 From JMarc 2002-11-30 00:51 ------- This is definitely a weakness of our l10n system, which is only correct to translate i nthe language of the interface, and not the language of the document. Since I do not find an existing bug about that, here are a few notes. First, we have to get the language in which to translate entries from the current document language, not the interface language. This means that I could be editing an english document, while showing menus in french. So we need to investigate how gettext can use several po files at once. [OK, maybe a dgression is needed here: Lars thinks that all translations should be done via gettext. This is not the only solution, since these language related translations can be defined by a language file, as dekel demonstrated 2 years ago. I'll attach the files to the bug. Personally, I think this may be the best solution, or rather a solution defining variables like $$thmname $$bibname, etc that would be used in the layout files.] Assume for now that we want to use gettext. What are the problems? 1/ can GNU gettext handle efficiently more than one po file at once (i.e. without having to close/reopen them all the time)? Do other gettext implementations work too? 2/ What kind of marking shall we use in the layout files? Assume for example that we define an envoronment theorem and that we have a document with parts in english and parts in french. Then theorems labels should be either "Theorem" or "Th?or?me". How do we code that? [I mean how do we code that cleanly without a pile of hacks?] Lots of questions, as you see...
