Reported by Leif in a Danish locale:
> Alternative text on the program ikon says something about the
> documentformat that is supported by Oracle.
Works for me with "LibreOffice 3.3.0 RC1 - WIN XP German UI, Spanish UI, Danish UI, English UI, French UI, [OOO330m17 (build 126.96.36.199)]"
Seems that that has been fixed in between, or only with Danish OS (I doubt)?
Pls feel free to reopen the issue if you can contribute concrete information that the problem still is visible in a current LibO version
Created attachment 40821 [details]
Screenshots showing tooltipps
Doh; a trivial grep for 'Oracle' shows things like this:
l10n/source/ca/localize.sdf:scp2 source\ooo\folderitem_ooo.ulf 0 LngText STR_FI_TOOLTIP_SOFFICE 0 ca El paquet d'ofimàtica compatible amb el format de document obert i estandarditzat ODF. Amb el suport d'Oracle. 2002-02-02 02:02:02
l10n/source/ca/localize.sdf:sysui desktop\share\launcher_comment.ulf 0 LngText startcenter 0 ca El paquet ofimàtic compatible amb el format de document obert i estandarditzat ODF. Amb el suport d'Oracle. 2002-02-02 02:02:02
Which I assume is where this comes from; simply not substituted in a helpful way.
I guess we should manually sed them out of localize.sdf.
(In reply to comment #3)
These strings should have been overridden by lo-build-*.sdf files. They are not, because not all localizations are complete. Instead of s/Oracle/The Document Foundation/ which can lead to linguistic issues, we can revert these strings back to English in lo-build-*.sdf files and in the same time ask the localizers again to complete their translations.
Would be a good idea to commit that reversion Andras - would simply changing the base English string work ?
Either way - it'd be great to have this in libreoffice-3-3 too ...
I think that the cleanest solution would be to remove the wrong translations from the l10n module, so that the English string is used as fallback.
The point is that we should not add English strings instead of lang-speific strings into the po/lo-build-<lang>.po files. Otherwise, it would be had to fix what strings are actually translated.
Andras, any chance that you could look at it?
(In reply to comment #6)
> Andras, any chance that you could look at it?
I will do it today.
I removed 4 strings that mention Oracle from each translation:
framework source\classes\resource.src 0 string STR_STATUSBAR_LOGOTEXT
instsetoo_native inc_openoffice\windows\msi_languages\Control.ulf 0 LngText OOO_CONTROL_124
scp2 source\ooo\folderitem_ooo.ulf 0 LngText STR_FI_TOOLTIP_SOFFICE
sysui desktop\share\launcher_comment.ulf 0 LngText startcenter
These strings are covered by lo-build-*.sdf files.
Closing - Sophie