Apache OpenOffice (AOO) Bugzilla – Issue 40244
SRC680_m71/70: menus are in en-US even in cs version
Last modified: 2005-01-21 14:19:54 UTC
Hi, SRC680_m71 (or m70) cripples menu. In Czech version, we have everything translated, but the top-level menu is in English even if I turn Czech as the GUI language. On the other hand, dialogs (like Tools - Options) are completely translated. The same applies to e.g. Open dialog - it is translated. ain: please confirm in Estonian language.
It also applies to German version built here.
GenericCommands.xcu contains correct values: pavel@linux:/tmp/SRC680_m71> grep -C6 "~Soubor" share/registry/res/cs/org/openof fice/Office/UI/GenericCommands.xcu <node oor:name=".uno:PickList"> <prop oor:name="Label" oor:type="xs:string"> <value xml:lang="cs">~Soubor</value> </prop> </node> Soubor is Czech word for File, so the translation seems to be correct.
Taking over. This is a regression from cws cfgimpex
Created attachment 21292 [details] Patch that reactivates localized data from configuration
Localized data that should be read from the configuration is not read (for any language), so the English fallback is used. Underlying reason is that a timestamp check is wrong: Data without timestamp support (this is the case for the locale-dependent data) is never read - even if there is no timestamp to check against.
jb: my verification build is already running. I'll report in the evening once I'm at home.
Fixed in CWS jb01
Verified. With this patch, my build of m71 again contains atrings translated. Thanks for very fast response!
Reopen to reassign to QA (for verifying on the CWS)
.
Fixed in cws jb01 @of: please verify asap This occurred in any non-english or multi-lingual version, so checking German should be enough. (pjank has verified the patch in cs version already)
of: Verified in cws jb01.
OF: is ok in src6780m71s1
*** Issue 40479 has been marked as a duplicate of this issue. ***
*** Issue 40656 has been marked as a duplicate of this issue. ***
is broken in m73 on Linux again...
The current problem is unrelated to this issue. It is merely a build problem (corrupted localized files) that occured during inhouse build on a single platform -> internal bug #119206#. -> back to fixed
And closing again.