Re: Tooltips not localizable?

Hello,

There are 21 strings. See: http://pastebin.com/XeAQzVjT. All of them
are in the vcl module in source\src\print.src. These strings are
localisable, because they are extracted into the SDF file. Every team
can localize them, although not through the Translate Toolkit and
Pootle, because oo2po ignores the helptext field in the SDF file. I
think we cannot blame the OOo devs, they had the right to use this
feature. L10n tooling failed here. IMHO it's easier to fix the
Translate Toolkit than to make helptext field deprecated. For the time
being probably all teams should translate these strings separately and
submit via Issue Tracker. Let me know what you think.

Regards,
Andras


2010/8/18 Martin Srebotnjak <[email protected]>:
> Hello,
>
> today I saw this bug reported:
> http://www.openoffice.org/issues/show_bug.cgi?id=113961
>
> This obviously means that there are several undocumented tool-tips
> unlocalizable in 3.3 and that that is a known fact to some people at OOo.
> Please someone make an assessment about the seriousness (the amount of these
> unlocalizable strings) and I hope that this bug and all other unlocalizable
> strings become a stopper bug for 3.3.
>
> Every programmer touching the OOo code should be aware how to deal with
> l10n, it should not be an error that every programmer gets by without any
> repercussions. At least the authors of these tool-tips will learn something,
> if this becomes a stopper. Otherwise they will not even know they did
> something wrong.
>
> Lp, m.
>