Weblate: Missing features, project folder view and search across the whole project

l10n
#1

In Pootle, translators can search specific term/translation in the whole
project, such as LibreOffice UI, LibreOffice Help, LibreOffice Online, etc.

This feature enables translators to check existing terms or translations
and fix them. Weblate only provides the search and replace tool, but not
useful as you typically have to search for existing ones first (view) and
then to decide to replace them all once or manually change them according
to the context one by one (edit).

Listing the components as folders under the project and searching text
across the whole project are quite important features in the daily
translation workflow.

The way Pootle works is designed to serve multiple translation files under
different projects which fits LibreOffice well while Weblate is not.

If we are moving to Weblate, and that should be solved to fill the missing
gap between them.

#2

I didn't notice this yet. But this is indeed a very important feature of Pootle what can't be missed.

Cheers, Kees

Cheng-Chia Tseng schreef op 12.09.2019 13:53:

#3

Hi Cheng-Chai, *

In Pootle, translators can search specific term/translation in the whole
project, such as LibreOffice UI, LibreOffice Help, LibreOffice Online, etc.

This feature enables translators to check existing terms or translations
and fix them. Weblate only provides the search and replace tool, but not
useful as you typically have to search for existing ones first (view) and
...

Thanks for describing the use case and that it is currently missing.

If we are moving to Weblate, and that should be solved to fill the missing
gap between them.

The idea is to contribute to Weblate to make it outstanding, or at least
very good, for our use. So I assume this feature should be on that list.

Maybe after the discussions on the conference here in Almería, Spain
(delay on the airport, so still in Almería :wink: ) there can be some info
on the plans, possible time paths and such?

Cheers,
Cor

#4

Hi *,

In Pootle, translators can search specific term/translation in the whole
project, such as LibreOffice UI, LibreOffice Help, LibreOffice Online, etc.

You can also search in a whole project in weblate.
But what weblate doesn't offer is limiting search to a "folder" (since
weblate doesn't have concept of folders)
So in weblate it is either whole project or single file (component)

This feature enables translators to check existing terms or translations
and fix them.

Hmm. I wonder whether an additional Glossary-based check would fill
this gap in a more elegant way?
I.e. you add your terms to glossary/terminology and we maybe could
write a check for strings that don't have a translation that matches
the glossary.

Weblate already has a default "inconsistent translation" check
https://docs.weblate.org/en/weblate-3.8/user/checks.html#inconsistent
that follows a similar idea (but is not enabled in our instance
currently, since same string is corner case in our project, and more
likely than not it is in different context that requires different
translation, so I'm afraid that check would cause too many false
positives) - and for same string weblate has dedicated "other
occurrences" section when doing regular translation, example:
https://vm137.documentfoundation.org/translate/libo_ui-master/scaddinsmessages/de/?checksum=f718cc3da84a2ebf

Listing the components as folders under the project and searching text
across the whole project are quite important features in the daily
translation workflow.

But this also sounds also like something that can be done more easily
offline, with the po files directly?

That said: if we were to have a solution for aggregation by folder, we
could put both help and ui into a single project solving your issue?
Not sure whether I did really understand the problem correctly.

The way Pootle works is designed to serve multiple translation files under
different projects which fits LibreOffice well while Weblate is not.

Don't quite get that, since pootle also is limiting stuff on a
per-project basis. (but within the project it works on folders, with
automatic aggregation, that's right)

If we are moving to Weblate, and that should be solved to fill the missing
gap between them.

Can you give a full example of what you do in pootle currently?
That would help me understand the issue better and maybe come up with
an easier workaround.
(Since adding folder-based view on weblate is nothing you should wait
for - that would likely take a while/if at all...)

ciao
Christian

#5

Þann 17.9.2019 10:53, skrifaði Christian Lohmaier:

Listing the components as folders under the project and searching text
across the whole project are quite important features in the daily
translation workflow.

But this also sounds also like something that can be done more easily
offline, with the po files directly?

But that raises the question (again); is it possible in Weblate to download all translation files for entire projects?
I've searched for the feature but not found.

Best,
Sveinn

#6

Christian Lohmaier <lohmaier+ooofuture@googlemail.com> 於 2019年9月17日 週二
下午6:53寫道：

Hi *,

>
> In Pootle, translators can search specific term/translation in the whole
> project, such as LibreOffice UI, LibreOffice Help, LibreOffice Online,
etc.

You can also search in a whole project in weblate.
But what weblate doesn't offer is limiting search to a "folder" (since
weblate doesn't have concept of folders)
So in weblate it is either whole project or single file (component)

If I am working on LibreOffice UI/ LibreOffice Online, then I donʼt want to
go through LibreOffice Help when searching.
Fixing translations in LibreOffice Help is kind of time-consuming and
torturing, so I work with UI/Online first. :S

> This feature enables translators to check existing terms or translations
> and fix them.

Hmm. I wonder whether an additional Glossary-based check would fill
this gap in a more elegant way?
I.e. you add your terms to glossary/terminology and we maybe could
write a check for strings that don't have a translation that matches
the glossary.

Weblate already has a default "inconsistent translation" check
https://docs.weblate.org/en/weblate-3.8/user/checks.html#inconsistent
that follows a similar idea (but is not enabled in our instance
currently, since same string is corner case in our project, and more
likely than not it is in different context that requires different
translation, so I'm afraid that check would cause too many false
positives) - and for same string weblate has dedicated "other
occurrences" section when doing regular translation, example:

https://vm137.documentfoundation.org/translate/libo_ui-master/scaddinsmessages/de/?checksum=f718cc3da84a2ebf

Yeah, I do notice the feature as I work on Weblate to translate the UI of
Weblate for some years.
However, finding inconsistent translations is another issue.

The idea of searching across the whole project mentioned above is mostly
happened when we are "changing the translation of specific terms".

> Listing the components as folders under the project and searching text
> across the whole project are quite important features in the daily
> translation workflow.

But this also sounds also like something that can be done more easily
offline, with the po files directly?

Thatʼs true we can do it offline, but the challenge we face is that Pootle
does this well online and we are used to it. T-T

That said: if we were to have a solution for aggregation by folder, we
could put both help and ui into a single project solving your issue?
Not sure whether I did really understand the problem correctly.

Yes! That might be a good solution. :slight_smile:

> The way Pootle works is designed to serve multiple translation files
under
> different projects which fits LibreOffice well while Weblate is not.

Don't quite get that, since pootle also is limiting stuff on a
per-project basis. (but within the project it works on folders, with
automatic aggregation, that's right)

Agree. It is more about the user experience part for translators working on
multiple files under one project, although it might seem nothing special.

> If we are moving to Weblate, and that should be solved to fill the
missing
> gap between them.

Can you give a full example of what you do in pootle currently?
That would help me understand the issue better and maybe come up with
an easier workaround.
(Since adding folder-based view on weblate is nothing you should wait
for - that would likely take a while/if at all...)

I typically click "LibreOffice Master UI" first, then click the different
components to translate.
If I find something translated wrongly (I may notice it in fuzzy, under the
translation memory pane below or see it in neighboring strings) when I am
going though the fuzzy/untranlsated strings, I will do the cross search
between projects (such as Master, LibreOffice 6.3 UI, LibreOffice 6.2 UI)
to fix them all at once (like bug fix and backport).

Actually, I totally support the move to Weblate in any time.

I just want to express that Poole has some advantages that we are used to,
and it is always better that we can have that again no matter how much the
time it might take.
There will be more of joy when we translate for LibreOffice projects as
before with folder-based view.
I also work on other small projects which have few files as well. I don't
think folder-based view is needed with those small projects.
However, in my point of view, LibreOffice needs it because of the
complexity of files.

If we canʼt have that after all, it is fine as well because we have
collected opinions and tried methods together with Weblate developers to
bring them back and failed.

#7

Hi,

Þann 17.9.2019 10:53, skrifaði Christian Lohmaier:

Listing the components as folders under the project and searching text
across the whole project are quite important features in the daily
translation workflow.

But this also sounds also like something that can be done more easily
offline, with the po files directly?

But that raises the question (again); is it possible in Weblate to
download all translation files for entire projects?
I've searched for the feature but not found.

I also find this to be an important question.

Currently we have in Weblate in Slovak UI master a lot of strings with
failing checks (mostly unchanged translation and trailing space). I
hoped to be able to download them for the whole UI master, fix them and
upload back (the page is currently very slow and I hoped to speed up the
process in this way).
However, I was able to download these strings only for individual files
(which does not help), since the hierarchy is file-language and not
language-file (which would be for our multifile project more appropriate).

To learn more, I've tried Weblate with another project
(https://hosted.weblate.org/projects/copyq/master/sk/). It is a single
file project and I would rate Weblate for this case as better than
Pootle. But in the case of LO it is very awkward. I think we should ask
the author, perhaps it can be fixed.

Best
Milos

#8

This could be a dummy question, let's say that I want to translate all
untranslated strings, one after the other as we used to do in Pottle, how
can we do that?

Christian Lohmaier <lohmaier+ooofuture@googlemail.com> escreveu no dia
terça, 17/09/2019 à(s) 11:54:

#9

Hi Sergio,

This could be a dummy question, let's say that I want to translate all
untranslated strings, one after the other as we used to do in Pottle, how
can we do that?

I'm not sure to understand your question, but it's just like on Pootle,
you go from one untranslated string to another.
What I've done to get a better view of what I've to translate is to
activate the Untranslated column (click on the last icon after the
column names and check Untranslated) in the dashboard and I sorted the
view by this column.
Cheers
Sophie

#10

Hi Sophie,

The activation of that option, for me, does not persists. Is ther any
option to make it persistent.

Regards

sophi <sophi@libreoffice.org> escreveu no dia quinta, 26/09/2019 à(s) 13:17:

#11

Sérgio Marques schrieb:

Hi Sophie,

The activation of that option, for me, does not persists. Is ther any
option to make it persistent.

Hi Sérgio,

go to your profile - the icon on the top at the far right with your avatar - then to "Definições" > Preferências > Ocultar as traduções completas no painel

Enable this setting and save it by clicking "Gravar" button.

Then click "Painel" on the bar at the top. You will see components with untranslated strings only then.

Michael

#12

Hi Michael and thanks for you reply.

That helps, but that way it also shows help content. If I go to Language ->
Portuguese that setting doesn't have any effect.

Regards

Michael Wolf <milupo@sorbzilla.de> escreveu no dia quinta, 26/09/2019 à(s)
15:41:

#13

Hi Sérgio,

Hi Michael and thanks for you reply.

That helps, but that way it also shows help content. If I go to Language ->
Portuguese that setting doesn't have any effect.

I search yesterday evening how to solve that, but didn't find. I'll ask
Christian if we can make that setting persistent and set by default. If
some translators don't want it, they still could unmarked it.

Cheers
Sophie

#14

Sérgio Marques schrieb:

Hi Michael and thanks for you reply.

That helps, but that way it also shows help content. If I go to Language ->
Portuguese that setting doesn't have any effect.

Hi Sérgio,

yes, you are right. In the components list (Listas de componentes) are help projects only. I don't know why. Upper and Lower Sorbian are not activated for help projects yet. You must use "Your languages" (Os seus idiomas) for translating. In your profile settings you can set "Your languages" as default.

Michael

#15

Ok Shopie. Thanks

sophi <sophi@libreoffice.org> escreveu no dia sexta, 27/09/2019 à(s) 09:36:

#16

Hi Michael, done that. Thanks

Michael Wolf <milupo@sorbzilla.de> escreveu no dia sexta, 27/09/2019 à(s)
11:42:

#17

Hi *,

But that raises the question (again); is it possible in Weblate to
download all translation files for entire projects?

Not via weblate directly, but you can get them from the repository.

https://github.com/LibreOffice/translations-weblate

While automatic push is not yet enabled, the plan is to have it push
once a week (or whatever looks sensible)

I've searched for the feature but not found.

there is no such feature in weblate webUI. One possibility would be to
use welbate client program / api wrapper and write a script that
iterates over all components and downloads them, but I think that
would be more complicated to use than fetching the files from the git
repository.

Ciao
Chrisitan

#18

Hi *,

Sérgio Marques schrieb:
[…]
yes, you are right. In the components list (Listas de componentes) are
help projects only. I don't know why.

I only created those components list to illustrate one possible
workaround for the lack of aggregation in weblate.
I could create similar aggregates for UI project as well if that would
help. But this is only a way to have a high-level overview of the
projects, you'd still work with the individual components.

ciao
Christian