Date: prev next · Thread: first prev next last
2024 Archives by date, by thread · List index


HI Tuomas, *,

On Mon, Feb 26, 2024 at 5:31 PM Tuomas Hietala <tuomas.hietala@iki.fi> wrote:

First, there's the Category feature:
https://docs.weblate.org/en/weblate-5.0/admin/projects.html#category

Categories aren't completely new, but were improved, previously there
was the option to create component lists/aggregates of components and
I created https://translations.documentfoundation.org/#componentlists
as a first test back in the day, grouping help to their modules as one
way to structure them. I don't know if anyone actually used those for
translation, since they are quite "hidden" in the UI

Currently on TDF Weblate there are dozens of sometimes somewhat
cryptically named components inside each project. You'll get used to
them after a while but we could reduce confusion and speed up navigation
by making use of categories. There could be one category per module
(Writer, Calc, etc.) and some common categories as well, as many
components are used across the whole suite.

Yep, some like cui and svx are used across everything. And it is
certainly possible to add them, but of course weblate doesn't know on
its own, so it would be ideal if someone could compile a hierarchy
that would make sense from a translator's perspective.

Also what we're not really using all that much is prioritization of
components/strings (that would change the order if you were to just
hit translate in a project and not manually pick a component).

I guess as a simple test to see how it looks I'll create a
"dictionaries" component - that is relatively easy to scope, has all
strings following the same pattern/basically only the language name
changes between the strings and thus might be a good candidate to
consolidate that way, also large number of components with few
individual strings...

Second, there's the Workflow customisation feature:
https://docs.weblate.org/en/weblate-5.1/workflows.html#workflow-customization

The idea was to allow each language team to make their own decicions
about workflow.

Yes, that's far more preference-dependent/requires input from the
corresponding l10n teams.

So I'm just making sure if it's now okay for teams to
make the switch if they want to?

I don't think our groups currently allow you to switch that yourself,
but you're more than welcome to request a specific workflow for your
language that Sophie or I can then configure for your language/for a
specific project and your language.

ciao
Christian

-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.