Re: Conflict issues with WebLate translations for libosinfo projects
Jean-Baptiste Holcroft <[email protected]>
| Newsgroups | gmane.linux.redhat.internationalization |
|---|---|
| Message-ID | <[email protected]> |
Hi, Le 2020-01-16 12:52, Fabiano Fidêncio a écrit : > Firstly, we're receiving MRs on our GitLab directly changing po/*po > files. is that expected? Yes, your component uses the plugin "Update PO files to match POT (msgmerge)" https://docs.weblate.org/en/weblate-3.10.1/admin/addons.html#update-po-files-to-match-pot-msgmerge This will update automatically all po files, allowing translators to see missing translations without having you to care about updating all files. > If so, what would be the best way to: > 1) Avoid things like > https://translate.stg.fedoraproject.org/projects/libosinfo/libosinfo/#alerts? Here you have the Polish file in conflicts. It probably means it was edited in both git repositories. To solve it: * as it's only one file, upload it manually in Weblate and set the real contributor name * or use command line: https://docs.weblate.org/en/weblate-3.10.1/faq.html#how-to-fix-merge-conflicts-in-translations To prevent it: The easiest for you and translators is to only use Weblate. Anyone can do imports. For every languages. You'll have no integration work and translators will be able to see changes. The more complex is to use the wlc command line tool to lock, pull and merge changes. But honestly, it's a bad idea as it brings manual operations and hide the change for Weblate users. > Last but not least, I've failed to understand what's the best way to > use `wlc` command line tool. `wlc lock` just returns me "Error: No > object passed on command line!". But what shall I pass? `wlc lock > --help` tells me that: "object Object on which we should operate > (project, component or translation)". `wlc lock $project_name` just You are using wlc to lock a project, but documentation tells it is to lock a component: https://docs.weblate.org/en/weblate-3.10.1/wlc.html#cmdoption-wlc-arg-lock Try with `wlc lock libosinfo/libosinfo` In Weblate, the project is a group of components, and only the component contains the git repository (or reuse an existing one, if so, you'll see it marked as linked). Jean-Baptiste _______________________________________________ trans mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]