Weblate meeting at Fosdem, feedback needed

l10n
#1

Hi all,

During Fosdem, we (Christian and me) will attend Michal's BOF and will
meet with other projects.

Here is a list of issues that we would like to discuss and see how we
can help to solve them:

Team management possibility by language admins
Return "Edit user" privilege back in a better way #2493
https://github.com/WeblateOrg/weblate/issues/2127

Per language glossary management (instead of per project)
https://github.com/WeblateOrg/weblate/issues/1158

Glossary matches on a single word instead of the whole string
https://github.com/WeblateOrg/weblate/issues/2183

Are there any other issues you have under your radar that should be
discussed?
Thanks in advance,
Cheers
Sophie

#2

Hi Sophie, *,

Kontakt sophi (<sophi@libreoffice.org>) kirjutas kuupäeval T, 21. jaanuar
2020 kell 11:26:

Hi all,

During Fosdem, we (Christian and me) will attend Michal's BOF and will
meet with other projects.

Here is a list of issues that we would like to discuss and see how we
can help to solve them:

Team management possibility by language admins
Return "Edit user" privilege back in a better way #2493
https://github.com/WeblateOrg/weblate/issues/2127

Per language glossary management (instead of per project)
https://github.com/WeblateOrg/weblate/issues/1158

Glossary matches on a single word instead of the whole string
https://github.com/WeblateOrg/weblate/issues/2183

Are there any other issues you have under your radar that should be
discussed?

A little annoyance I've noticed:

Would it be possible to make clicking on a column header on components page
(e.g. https://weblate.documentfoundation.org/languages/et/libo_ui-6-4/)
sort all the components of the current project, not just the ones currently
in view? As it is now, the sort function there is half-useless if there are
4 pages to click through.

Alternatively, increase the number of components shown per page so that all
the components could fit on one page :slight_smile:

Best regards,
Mihkel
Estonian translator

#3

Hi Sophie

- We could want to upload a TM, but they are very large in size (maybe 10 MB and more). Is it possibile to work on this aspect? I got an error while trying to upload one.

- Also, it should be possible to download a "general", or "per project" Translation Memory?

Ciao

#4

Hi Valter, *,

- We could want to upload a TM, but they are very large in size (maybe
10 MB and more). Is it possibile to work on this aspect? I got an error
while trying to upload one.

Weblate's own TM has too bad performance for a project structure like
we have for LibreOffice.

Depending on the nature of the TM, I can add it to the amagama
instance, but if it is old translations from pootle, then those are
already available. (and for strings that were translated in weblate,
the builtin machine translation tab should also work just fine.

- Also, it should be possible to download a "general", or "per project"
Translation Memory?

See above, we're not using weblate's translation memory. And for our
case there is no distinction anyway, since all is a single
project/everything is related (so I don't see the need for having it
"per project" - why would you only have a TM for 6-4 but not for 6-3
and master?)

That again of course due to the way we have weblate setup, with
branches being on their own project because of the number of
individual components we have, and not the standard way of having the
different branches within a project.

ciao
Christian