-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: separate repo for l10n #19
Comments
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. |
Thanks a lot.
Ha of course, I didn't think of that.
Absolutely :) Just want to make sure I'm not missing on something. |
Is the |
Nope, it is manually generated by us with meson/ninja. |
We also have the Weblate's webhook configured in Github |
@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. |
Hello 👋
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.
The text was updated successfully, but these errors were encountered: