Untranslated extensions

l10n
#41

2010.12.14. 15:00 keltezéssel, Andras Timar írta:

Hi Olivier,

HI

Some extensions are not fully tanslated and are bundled into the LIbO 3.3.

One interesting extension is the Calc non-linear Solver: Tools - Solver
- Options, and selec the non-linear solvers.

Can we load them in Pootle?

I've open this issue concerning the solver
https://bugs.freedesktop.org/show_bug.cgi?id=30839

And as I explained in the bug, this one is non-trivial. The extension
in general don't use the same translation mechanism that the rest of
LibO uses. Even so, some extensions written in C++ and included in the
build tree cheats by directly accessing LibO's internal resource API
(such as calc's default linear solver), but because the non-linear
solver is written in Java, we can't do that cheat. :frowning:

So, to make the string translatable for this extension we'd have to make
non-trivial amount of change in the code itself, which I personally
don't feel comfortable doing in the 3.3 time line.

As a temporary solution, can't we just translate the .properties files
and bundle the translated .properties? All you need to do is to update
tarball at the end of the process.

Hi,

Today Kohei signed off my patch to nlpsolver and I committed it. I also
committed the following translations from Pootle (+ Slovenian from
direct mail): ast, ca, fr, hu, it, nl, pt-BR, sl. These languages were
at 100%. Whenever I notice that a language reach 100%, I'll commit it, too.

Cheers,
Andras

#42

Rimas:

Could you enable extensions translation for Spanish also?

Thanks, and best regards,

Santiago

#43

Hi Santiago,

2010.12.22 18:56, Santiago Bosio rašė:

Rimas:

Could you enable extensions translation for Spanish also?

Thanks, and best regards,

Done. Have a nice day!

Rimas