Weblate instance for testing purposes

l10n
#21

Hi *,

> Why are there untranslated strings for Upper Sorbian and Lower Sorbian
> on Weblate? All master strings are translated on Pootle for both languages.

The template has been updated

Exactly. What was labeled "master" in pootle is used for 6.3 (just
renamed the projects to make that more clear, so now it is not labeled
master anymore). So translations for 6.3 and 6.2 are still in pootle
(and that will stay that way, those won't be migrated away)

Files on Weblate have been updated to reflect master/what will become 6.4

ciao
Christian

#22

Hi *,

Who volunteers to create a feature request?
https://github.com/WeblateOrg/weblate/issues

Doubt that this will be implemented, as weblate is built around that
single-file-component concept.

However I created the next-best-thing that Weblate has to offer for
grouping, namely Component lists for Help project:
https://vm137.documentfoundation.org/#componentlists

Does something like this already help?

ciao
Christian

#23

sophi schreef op 28.08.2019 10:42:

Hi,

I agree with Cheng.
All the different small parts of items makes it uncomfortable to see
what to translate.
Better is to have one folder of untranslated items (like Pootle)
And saving a change and skip to the next item seems a bit slow to me.

This is not possible currently on Weblate and I agree this is not the
best, but Weblate has many other nice features :slight_smile:

Can you tell us more about those features.
So we don't all have to look for them.

Greetings, Kees

#24

Christian Lohmaier schreef op 28.08.2019 13:31:

Hi *,

Who volunteers to create a feature request?
https://github.com/WeblateOrg/weblate/issues

Doubt that this will be implemented, as weblate is built around that
single-file-component concept.

However I created the next-best-thing that Weblate has to offer for
grouping, namely Component lists for Help project:
https://vm137.documentfoundation.org/#componentlists

Does something like this already help?

Not realy, because when you open the link, again there are a lot of lists.

#25

kees538@libreoffice.org schreef op 29.08.2019 07:04:

Christian Lohmaier schreef op 28.08.2019 13:31:

Hi *,

Who volunteers to create a feature request?
https://github.com/WeblateOrg/weblate/issues

Doubt that this will be implemented, as weblate is built around that
single-file-component concept.

However I created the next-best-thing that Weblate has to offer for
grouping, namely Component lists for Help project:
https://vm137.documentfoundation.org/#componentlists

Does something like this already help?

Not realy, because when you open the link, again there are a lot of lists.

But it is nice to have different folders for Help and UI.

#26

Here are highlighted features: https://weblate.org/en/features/

Ilmari

#27

Thank you but my point was less "how can I fix it" but rather more "I'm not sure about moving to a platform where we have to start by fixing fairly basic issues".

Michael

Sgrìobh Ilmari Lauhakangas na leanas 28/08/2019 aig 10:51:

#28

Hi Sophie

Ah I must have missed that. Would it not be easier to simply fork Pootle? I mean, it's relatively mature as a platform so unless TDF is needing a whole host of features for translation that Pootle currently doesn't have, why not stick with what we know & have and tinker with it as needed?

Michael

Sgrìobh sophi na leanas 28/08/2019 aig 11:04:

#29

I am sure Pootle takes patches, there is no need to fork (it is not declared as abandoned, progress is just slow). The problem is having to do the work. With Weblate there is active development that does not require investment from us.

Ilmari

#30

Hi all,

I've been using Weblate for several years for other projects I maintain, mostly F-Droid, OsmAnd and Debian-Installer, and I kind of have liked the experience.
What I've liked the most is the ability to setup Weblate to deliver the translations in a multitude of file-formats for download.
The UI is mostly sensible, not too much waisted whitespace as has been en vogue lately.

A couple of negative points though (which I will surely investigate later and discuss with the Weblate-team):

How on earth can I download/upload ALL the files in a project? Maybe it's there somewhere, but I haven't found this critical (for me) feature.

Since a recent Weblate upgrade (perhaps 3-5 months ago), validity-checks when uploading a file are way too strict and non-verbose; if there's ONE faulty string in a file, NONE of the other well formatted strings are accepted and you only get a message like: "Please fix errors in the form. Error in parameter method: This field is required."

Before the upgrade you would get the plain output from msgfmt or whatever script used to verify the file, with indicators on which lines there are errors. And other correctly formed strings got accepted.

What hurts me most are the false-positives concerning newlines in PO-files, PO-editors generally arrange very long lines in multiple shorter lines inside the same msgid/msgstr, which I think is accepted in the gettext-standard. Now those strings are not appended but get a newline symbol between them.
Another is the warning/fuzzying when the source and the translation are the same: I can see in the LO Weblate-instance some 30+ strings with this warning, for which I can remove the warning manually. Nothing tells me why these strings are considered so dangerous and not some of the other strings where the source and the translation are the same. Worst of all, next week they may be fuzzied again for the same reason, when the Weblate-files are read again from source.

I suspect that these problems stem from a combination of new validity-checks in latest Weblate along with files which are not gettext-native (for example iOS-strings), or even that their version of gettext is different from mine :wink:

Haven't had time to investigate this properly, my points mostly concern a couple of files I've been fighting with (for example OsmAnd-iOS https://hosted.weblate.org/projects/osmand/ios/is/) but also what I saw in the LO Weblate-instance.

Just thoughts,
Sveinn í Felli

Þann 28.8.2019 08:37, skrifaði sophi:

#31

Then again I ask the question, what does Weblate *do* that Pootle *doesn't* do that we *need/want*?

Michael

Sgrìobh Ilmari Lauhakangas na leanas 29/08/2019 aig 11:59:

#32

Hi,

I miss still a really important feature for translators: Localization notes that make the meaning of English strings clearer. there are e.g. simple things like: Is a word a noun or a verb, e.g. "download". Some words can have a different menaing in another context. There are those strange comments instead, with cryptic strings. I do not know what those cryptic strings shall mean.

Weblate would be a chance to bring this feature in. In the past, someone started to use localization notes on Pootle but they were a few only.

Then, I did not find the option to filter strings in the strings overview of a file anymore so I can display e.g. untranslated strings only.

Regards,

Michael Wolf

#33

In Pootle, below a string to translate, there are suggestions with former translations.
I miss those in Weblate, or are they somewhere ells?

Kind regards, Kees

sophi schreef op 27.08.2019 16:37:

#34

Hi,

In Pootle, below a string to translate, there are suggestions with
former translations.
I miss those in Weblate, or are they somewhere ells?

Weblate has similar feature, see for example:
https://vm137.documentfoundation.org/translate/libo_help-master/textsdraw04/de/?checksum=f7176f58b13e677f#machine

(But weblate only knows has master translations, thus no strings from
previous versions)

ciao
Christian

#35

I don't think that was the problem with Pootle though, that was just devs not commenting strings, which is a problem whatever the platform. Moving to Weblate won't solve that :wink:

Am Michael Eile [The other Michael]

Sgrìobh Michael Wolf na leanas 30/08/2019 aig 11:31:

#36

That is one feature of pootle that I will mis than.

Christian Lohmaier schreef op 31.08.2019 15:39:

#37

kees538@libreoffice.org kirjoitti 1.9.2019 klo 8.00:

Christian Lohmaier schreef op 31.08.2019 15:39:

In Pootle, below a string to translate, there are suggestions with
former translations.
I miss those in Weblate, or are they somewhere ells?

Weblate has similar feature, see for example:
https://vm137.documentfoundation.org/translate/libo_help-master/textsdraw04/de/?checksum=f7176f58b13e677f#machine

(But weblate only knows has master translations, thus no strings from
previous versions)

That is one feature of pootle that I will mis than.

The translation memory from previous versions can be imported: https://docs.weblate.org/en/latest/admin/memory.html

Translation memory scopes

New in version 3.2: The different translation memory scopes are available since Weblate 3.2, prior to this release translation memory could be only loaded from file corresponding to the current imported translation memory scope.

The translation memory scopes are there to allow both privacy and sharing of translations, depending on the actual desired behavior.
Imported translation memory

You can import arbitrary translation memory data using import_memory command. The memory content will be available for all users and projects.

https://docs.weblate.org/en/latest/admin/management.html#django-admin-import_memory

manage.py import_memory <file>

Imports a TMX or JSON file into the Weblate Translation Memory.

--language-map LANGMAP

     Allows to map languages in the TMX to Weblate one. The language codes are mapped after normalization usually done by Weblate.

     For example --language-map en_US:en will import all en_US strings as en ones.

     This can be useful in case your TMX file locales does not match what you use in Weblate.

Ilmari

#38

Ilmari Lauhakangas schreef op 01.09.2019 07:52:

kees538@libreoffice.org kirjoitti 1.9.2019 klo 8.00:

Christian Lohmaier schreef op 31.08.2019 15:39:

In Pootle, below a string to translate, there are suggestions with
former translations.
I miss those in Weblate, or are they somewhere ells?

Weblate has similar feature, see for example:
https://vm137.documentfoundation.org/translate/libo_help-master/textsdraw04/de/?checksum=f7176f58b13e677f#machine (But weblate only knows has master translations, thus no strings from
previous versions)

That is one feature of pootle that I will mis than.

The translation memory from previous versions can be imported:
https://docs.weblate.org/en/latest/admin/memory.html

Translation memory scopes

New in version 3.2: The different translation memory scopes are
available since Weblate 3.2, prior to this release translation memory
could be only loaded from file corresponding to the current imported
translation memory scope.

The translation memory scopes are there to allow both privacy and
sharing of translations, depending on the actual desired behavior.
Imported translation memory

You can import arbitrary translation memory data using import_memory
command. The memory content will be available for all users and
projects.

https://docs.weblate.org/en/latest/admin/management.html#django-admin-import_memory

manage.py import_memory <file>

Imports a TMX or JSON file into the Weblate Translation Memory.

--language-map LANGMAP

    Allows to map languages in the TMX to Weblate one. The language
codes are mapped after normalization usually done by Weblate.

    For example --language-map en_US:en will import all en_US strings
as en ones.

    This can be useful in case your TMX file locales does not match
what you use in Weblate.

Ilmari

This will be great. Are we going to use it?

Kees

#39

You can't see suggestions because for the moment, previous versions (and
translations) are not present in Weblate. This is what Christian
explained, for the future if we choose Weblate, then suggestions will be
present because everything will be imported there.

Cheers
Sophie

#40

Hi Michael and all,

I don't think that was the problem with Pootle though, that was just
devs not commenting strings, which is a problem whatever the platform.
Moving to Weblate won't solve that :wink:

Yes, you are right, the only file that is commented is emojis, so it's
not a missing feature :slight_smile:

Cheers
Sophie