Re: Tooltips not localizable?

Hello,

I have my own Pootle-like translation system I developed (it downloads
chosen sdf from OOo mirror servers and creates pot files from them, then
update/migrate it from previous milestone po translations of my choice).
For those commands I use Translate Toolkit and gsicheck. Does that mean that
I have those strings translated?

Well I checked my final SDF I reported in in the IZ yesterday as final
Slovenian SDF for 3.3 and it is not localized! What now? Should I localize
it manually and then for every SDF the same way, manually localizing 21
strings? I don't think that is an option.

Maybe here is a simple solution for the OOo team - create a special pot file
just for these 21 strings so all lang teams can translate them and send in
the po files. Then you OOo devs can write a special script that will replace
those 21 strings in the final delivered SDF files?

For the DEV300 the patch should be used to move this strings in such
format/location so that they can be localized via Translate Toolkit/Pootle
the normal way. Of course the ultimate solution would be to update Translate
Toolkit but we do not have time now (in 1 hour there is the deadline for
localization SDF delivery).

Just my 2 cents,
Martin

2010/8/18 Andras Timar <[email protected]>

> 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.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>