ODF 1.3 Extended

Hi *,

What's up with this comment here?
Source string comment
5ANvD
EN-US, the term 'extended' must not be translated.
Context: optsavepage|odfwarning_label
Source
Not using ODF 1.3 Extended may cause information to be lost.

(
https://weblate.documentfoundation.org/translate/libo_ui-6-4/cuimessages/et/?checksum=2585550260551d82
)

Why on earth shouldn't the "extended" be translated?
As a side note, in settings (Tools - Options - Load/Save - General), the
name of the format has been translated in all the languages i checked.

Best regards,
Mihkel
Estonian team

The author probably thought that "ODF 1.3 Extended" was a proper name. But
it's just a label, nothing will happen if you actually translate the term
Extended. It may or may not confuse the user. That's all.

Best regards,
Andras

Andras Timar (<timar74@gmail.com>), 16. detsember 2019 kell 14:20:

Hi *,

What's up with this comment here?
Source string comment
5ANvD
EN-US, the term 'extended' must not be translated.
Context: optsavepage|odfwarning_label
Source
Not using ODF 1.3 Extended may cause information to be lost.

(

https://weblate.documentfoundation.org/translate/libo_ui-6-4/cuimessages/et/?checksum=2585550260551d82
)

Why on earth shouldn't the "extended" be translated?
As a side note, in settings (Tools - Options - Load/Save - General), the
name of the format has been translated in all the languages i checked.

The author probably thought that "ODF 1.3 Extended" was a proper name.
But it's just a label, nothing will happen if you actually translate the
term Extended. It may or may not confuse the user. That's all.

Thanks for the reply. I know nothing will break if it gets translated :slight_smile:
However I can't see any reason for that label *not* to be translated, and
as such I think the comment should be changed to a milder wording, leaving
it up to the individual l10n teams to decide whether or not to translate
that format name (both in this string and in the format selection list in
settings).

Best regards,
Mihkel

Hi Mihkel,

Mihkel Tõnnov wrote:

Why on earth shouldn't the "extended" be translated?
As a side note, in settings (Tools - Options - Load/Save - General), the
name of the format has been translated in all the languages i checked.

Then I guess there's no harm translating this one, too.

I was mechanically taking the ODF 1.2 extended entry, and adjusting it
for 1.3:

  <item translatable="yes" context="optsavepage|odfversion">1.2
    Extended (compatibility mode)</item>

So perhaps this discussion took place already for ODF 1.2 Extended,
and was just not reflected back into the source tree?

Cheers,

-- Thorsten