A little tiny new string for 4.2.1???

l10n
#1

I know that I risk to become a piece of hamburger asking for this, but I
will try anyway :slight_smile:

I would love to add for 4.2.1 a new feature (AbiWord import filter). The
only problem is that it would mean one new string "AbiWord Document" for
4.2.1. OTOH, there are already "WordPerfect Document" and many other
"<something> Document" strings, so I guess that even a fuzzy translation
could produce a good result. Moreover, this string would be visible only
if one lists the document types in the File->Open dialogue.

Please, advise, whether I am making myself a lot of enemies by
requesting this.

Cheers

F.

#2

Fridrich Strba wrote (16-01-14 16:58)

I know that I risk to become a piece of hamburger asking for this, but I
will try anyway :slight_smile:

As long as it's a human-eco-hamburger, I support you :wink:

Kidding of course. I won't object, but am one with only little rights to
speak here :wink:

I would love to add for 4.2.1 a new feature (AbiWord import filter). The

+1

#3

Hi,

I support inclusion of this new feature and there is no big issue since
there will be enough time to localize it for 4.2.1.
My question is: why not into 4.2.0? We have 3 day to translate and 1 string
is not a nightmare.

Lp, m.

#4

1 string isn´t a big deal. That´s ok for me.

#5

Martin,

I support inclusion of this new feature and there is no big issue since
there will be enough time to localize it for 4.2.1.
My question is: why not into 4.2.0? We have 3 day to translate and 1
string is not a nightmare.

You motivated me and I found enough of reviews to push it to 4-2-0 too.
So yes, there is the string "AbiWord Document" that needs to be
translated for 4.2.0.

Thanks a lot for your magnanimity

F.

#6

Dear Fridrich,

Martin,

I support inclusion of this new feature and there is no big issue since
there will be enough time to localize it for 4.2.1.
My question is: why not into 4.2.0? We have 3 day to translate and 1
string is not a nightmare.

You motivated me and I found enough of reviews to push it to 4-2-0 too.
So yes, there is the string "AbiWord Document" that needs to be
translated for 4.2.0.

Thanks a lot for your magnanimity

Content of <value xml:lang="x-default"> tag is not extracted for
translation, you need to use xml:lang="en-US". Same applies to all of
your exotic filters. So actually you did not add a new string for
translation. But you may want to enable translation for all of these
"FooBar Document" strings which exist under
filter/source/config/fragments/filters.

Best regards,
Andras

#7

Not every developer is as nice as Fridrich :wink: so despite he actually
did not add a new string, others did, so update of pot files is
necessary anyway.

I see changes in the following files:
cui/uiconfig/ui.pot
dictionaries/pt_BR/dialog.pot
sc/source/ui/src.pot
sc/uiconfig/scalc/ui.pot
sd/uiconfig/simpress/ui.pot
sfx2/uiconfig/ui.pot
sw/uiconfig/swriter/ui.pot

Most of the changes are just re-ordering controls, so strings did not
change actually. The are some real changes, too.

Best regards,
Andras

#8

Thank you so much Andras!
Cheers
Sophie

#9

So I guess these filter strings will be localizable by 4.2.1, as a patch to
a bug that marks all these strings "unlocalizable"?

Thanks, m.

#10

Hello,

So I guess these filter strings will be localizable by 4.2.1, as a patch
to a bug that marks all these strings "unlocalizable"?

Ouch, I did not realize that thing since ages. The WordPerfect filter
for instance is there since 2004/2005 :slight_smile:

Now in that directory, there are several zillions of files that have the
x-default as xml:lang. The question is whether I simply change each
<prop oor:name="UIName"> to have <value xml:lang="en-US">. If that is
the case, I will file the bug today and provide patch to master and file
it to gerrit for 4.2.1

Please, advise,

F.

#11

Andras,

Content of <value xml:lang="x-default"> tag is not extracted for
translation, you need to use xml:lang="en-US". Same applies to all of
your exotic filters. So actually you did not add a new string for
translation. But you may want to enable translation for all of these
"FooBar Document" strings which exist under
filter/source/config/fragments/filters.

Could you check in https://gerrit.libreoffice.org/7491 whether that is
what we want? Not sure what to do with ui strings that only say
"Microsoft Visio", how localizable that should be. OTOH, I would not be
surprised if for some languages it would be "Микрософт Визио".

Please, advise

F.

#12

Yes, I think we can allow localization/transliteration for all filter
names. It is up to the translators to keep the proper names. I trust
the community. :slight_smile:

To translators: From the technical point of view, 42 new strings will
appear for translation. 41 of them have been in the source code for
ages, but were not localizable. Nothing will change, if you leave them
alone, they will be in English as before. The +1 new string is
"AbiWord Document".

Best regards,
Andras

#13

Hello,

Yes, I think we can allow localization/transliteration for all filter
names. It is up to the translators to keep the proper names. I trust
the community. :slight_smile:

Here I touched only the once that are implemented in writerperfect
module. There is still a number of UIName instances with
xml:lang="x-default". Should I patch it too?

Cheers

F.

#14

I suggest yes. Probably these are the filter strings that were not
localizable until now. Andras?

Lp, m.

#15

Hi *,

I updated the templates and triggered the syncing process (but this is
rather slow and takes a while), As it processes the languages in
alphabetical sorting (regarding the iso-code) - don't be alarmed if
nothing new shows up right now. Check again in a few hours.

As Andras mentioned: While there a couple of new strings, it is just
that those haven't been marked as translatable before, and for most of
them you can just copy the english string (as for example a string
like "CGM - Computer Graphics Metafile" won't be translated, but you
might want to translate Document in filternames like
"ClarisWorks/AppleWorks Document"

ciao
Christian