Question: separate repo for l10n

[sonnyp]

Hello :wave:

I've been struggling with l10n for my 6+ apps. I don't want git l10n commit messages for every single contribution. I setup a separate branch in the repos where Weblate pushes the l10n updates. On release I would squash merge it into main.

It worked fine for a while but I endup with conflicts and I don't have time to solve them.

How is your experience with using a separate repo for translations? Could you share your setup / weblate settings ?

I'd be interested in documenting this publicly if it works well.

[rafaelmardojai]

In general, I don't mind about commits per translation updates for my projects, but we agreed to separate them for Dialect, to have a cleaner git history and for our automation regarding language name translations.

I will say that the experience is good, we usually only touch this repo when updating strings from the UI.

The setup is not really special, just a git submodule and a regular weblate settings. I don't know how to exactly share the settings, screenshots will work? 😅

One important note is not to forget to tag releases in this repo as well, to make life easier for packagers.

[sonnyp]

Thanks a lot.

just a git submodule

Ha of course, I didn't think of that.

screenshots will work? 😅

Absolutely :) Just want to make sure I'm not missing on something.

[sonnyp]

Is the pot file in po/ui generated by Weblate?

[rafaelmardojai]

Is the pot file in po/ui generated by Weblate?

Nope, it is manually generated by us with meson/ninja.

[rafaelmardojai]

These are de add-ons we have enabled:

Settings:

[rafaelmardojai]

We also have the Weblate's webhook configured in Github

[ghost]

When I compare UI and strings in Weblate instance I see there are several (15~) missing strings in Weblate instance.

[rafaelmardojai]

@sabriunal Yes, we have merged a few contributions that added new strings recently. We sync po files to code changes manually, and we haven't done it yet.