Created attachment 71195 [details] Screenshot Steps how to reproduce [Reproducible] with parallel installation of "LOdev 4.0.0.0.alpha1+ - ENGLISH UI / German Locale [Build ID:d6579884752c298a18b7cdfcc7d1614b55c9c7c)]" {tinderbox: Win-x86@6, pull time 2012-12-06 02:46:58} on German WIN7 Home Premium (64bit) with own separate User Profile: 1. Open New Calc Document from LibO start center 2. Check Submenu items in all Items of menu Bar. All Except "Datei" and "Hilfe" contain untranslated English strings.
It seems not to be a "missing translation" problem, but some "wrong pointers problem", I see the same problem also in Spanish and French UI.
I can confirm with LOdev 4.0.0.0.beta1 (Build ID: 87906242e87d3ddb2ba9827818f2d1416d80cc7) and French UI. It seems to be the same menus/sub-memus that are not translated.
@GerardF What operating system? @András: Your area?
(In reply to comment #3) > @GerardF > What operating system? Windows Vista 32 bit.(French)
Definitely a cross-platform issue: I see exactly the same problems in 4.0.0.0beta1 with German langpack installed on Mac OS X 10.6.8 (Intel).
@ Markus Mohrhard: Hi Markus, Rainer Bielefeld suspects that this UI bug is not a simple “missing translations” problem, but some kind of “wrong pointers problem”. Could you, being a Calc expert, please check this possibility? (It’s an important issue; we can’t ship 4.0 with such glitches.) Thank you very much!
Created attachment 71557 [details] it works for me... I've just build one from libreoffice-4-0, and the menus in question are in German. In general, please do not escalate localization bugs before string freeze, and before translators finished their work. After RC1 or RC2 we can still fix real errors, I mean when you *know* that the string is translated in Pootle and in git, yet it does not show up in UI.
@Andras: How can we simply see when string fix has been done? It would help us to avoid some useless testing if someone could announce that on <libreoffice-qa@lists.freedesktop.org>
> How can we simply see when string fix has been done? And I can not even test this, because there are no up-to-date master builds for Mac OS since the beta1 ... but this is another problem :-(
I will update strings for 4.0 beta2 tomorrow. Regarding this bug, I must admit that it is not a simple "WORKSFORME", I know why it happened and how it was fixed. A cleaner/formatter script of mine had a bug, and it deleted translation from po files. I fixed it with this commit: https://gerrit.libreoffice.org/gitweb?p=translations.git;a=commit;h=d9a4b60f9ae7e15c44675ea56fe6a06613c419ae