Apache OpenOffice (AOO) Bugzilla – Issue 7932
Use gettext ?
Last modified: 2013-08-07 15:00:01 UTC
Hello, it may be just an idea of mine, but I really think OpenOffice.org should use gettext for the localization of the interface. There are many advantages that would come from this: easier work on those responsible for the localizations, possibility to install more than one interface, ability to switch easily from one to the other ... The price to pay would be that all the strings would have to be gettextized. I think it's a fair price ...
DL->NF: Could you please takeover?
-
In general, I agree that it makes sense to align different open source solutions. In this case, we have to keep in mind, that consequent usage of gettext means changing our resource systems completally. This affects not only the UI but also the configuration with his localizable items, the setup functionality etc. My feeling is, that the benefit of such change is not that big. I remember, that other teams are already discussing how to go forward with the OOo resource system regarding the UI (customizable UI, XML based resources etc.) To fit into translation processes based on gettext, it is possible to convert the OOo gsi files to PO and back. I remember a team on OOo that did so. In my opinion, this issue has to be discussed on the corresponding dev list instead of this issue.
As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified.
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.
Created attachment 9957 [details] Patch to use gettext on strings read from resource files
I have attached a patch that uses gettext to localize strings that are read out of resource files. I will discuss this further on the l10n list...
PS the patch is for 1.1