Untranslated extensions

l10n
#1

l10n@libreoffice.org wrote:

>> 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.

Thanks,
Andras

Hello all

I think we are in the intersection of several issues on 3.3 and time is
pressing:

1) the fact that the windows installer is broken on the "Extensions" option,
2) untranslated extensions like this one, which is "difficult",
3) "bundled" extensions (new in 3.3), which prevents removing them thru unopkg.

equals= drop these "bundled extensions" in 3.3 and let's work them better in
3.4. There no issue on installing them after a clean and stable installation.

Regards