Contributors mailing list archives

Hi Stéphane, all,

I have been looking into the best way to integrate OCA repos inside Weblate but could not figure it out by myself. I have found a few promising things however :

• Glossaries are defined by project but can be shared across projects (https://docs.weblate.org/en/latest/admin/projects.html#component-links)
• Projects can be configured to share Translation Memory so that these translations could be accessible from any other project (https://docs.weblate.org/en/latest/admin/memory.html#shared-translation-memory)
• Translation memory can be used per project to automatically suggest or translate (with or without "To be verified" checkbox) terms (https://docs.weblate.org/en/latest/admin/machine.html#weblate-translation-memory)
• DeepL or any other service from this page https://docs.weblate.org/en/latest/admin/machine.html could be used to automatically translate or suggest remaining terms (configurable per project)

I have also looked in Transifex and was able to export glossary and translation memory used by Odoo (so that OCA modules translations are as much as possible coherent with Odoo ones). Next step would be to import those in Weblate (I am working on French ones for now).

As you mentioned, from my point of view, before going more in details on what we could do on Weblate, we would need to question the organization of projects / components. I have tried to figure out what is the best way to implement those based on Weblate documentation, but with not much findings. I think the best way-forward would be to ask support from Weblate directly to ask them what would be the most efficient way to do so.

I have discussed this point internally at Le Filament and we would be OK to pay for a few hours of support from Weblate engineers on this OCA topic.

Basically, I would like to present them :

• what OCA has to translate (GitHub repos, with branches and modules inside),
• OCA processes regarding translations (pot file generated by odoobot and pushed to Weblate, Weblate pushes translations back to repo)
• (the way we implemented it in Weblate)
  
• the languages we use

And ask them the following :

• What would be the best way to integrate OCA modules to ease translation while keeping automatic workflows ?
• Also, I would like to ask them whether it is possible to merge redundant languages (for instance is it necessary to keep both fr and fr_FR translations) ?
• What is according to them the best path towards automatic translations (keeping only review / correction / validation by translation teams before pushing to OCA repos)

I am not sure how to get approval from OCA to perform the above (maybe even whether I should seek approval) ? Let me know if this should be granted by OCA board or if I could go forward if noone is against it (please tell me if you do object with the approach) ?

Let me know also if you see other questions that we could ask them ?

Best Regards,

Rémi

Le 22/06/2023 à 18:16, Stéphane Bidoul a écrit :

A DeepL integration in weblate would be great. If the budget is reasonable we may even imagine that OCA could cover the DeepL cost.

I suspect however that a prerequisite to make that work is the better organization of the projects and glossaries that I mentioned before.

-sbi

On Thu, Jun 22, 2023 at 5:52 PM Rémi CAZENAVE - Le Filament <notifications@odoo-community.org> wrote:

Hi Stefano,

We also had discussions for French translations earlier today (not really to add validation layers / access rights but rather to improve the number of translated modules) and we are about to test translating with DeepL using Traduction Memory and Glossaries to see how good it gets and if it can improve a lot contributing with French translation.

(For now we will test it outside Weblate and import translations manually in Weblate, but it is also possible to directly interface Weblate with DeepL to get automatic translations or suggestions, maybe we could go into that direction if it really helps !)

Also, I had a few spare minutes so I unlocked all the repositories you listed below in Weblate.

It seems that this could be scripted but I would have needed access to the server which I do not have so I did it manually, one by one.

As for why they were locked I cannot say, the only thing I see is that these were locked because of error, but I could not find the error...

Best Regards,

Rémi

--X-BM-SIGNATURE--

Le 22/06/2023 à 08:31, Stefano Consolaro a écrit :

Hi Stéphane,

you are not alone with a lot a things to do and the my reply time to your answer prove it ;-)

We (italian members) have talked a bit and will probably install a test server after the summer to test configuration options and functionalities.
After that we will share results and some ideas on how to rules the translations.

In the meantime I ask you the favour to unlock some modules listed below (but there are many more).
But, why some modules are locked?
Is there a way to unlock all at once or do you have to do them one at a time?

Thanks

Modules locked
agreement-16.0-agreement
bank-payment-16-0-account_payment_mode
connector-16-0-test_component
contract-16-0-contract
crm-16.0-crm_claim
currency-16.0-currency_rate_update
data-protection-16-0/data-protection-16-0-privacy
fleet-16.0-fleet_vehicle_fuel_type_ethanol
helpdesk-16.0-helpdesk_mgmt
hr-16.0-hr_employee_firstname
iot-16.0-iot_oca
l10n-italy-16.0-l10n_it_rea
management-system-16.0-mgmtsystem
manufacture-16.0-mrp_warehouse_calendar
project-16.0-project_type
purchase-workflow-16.0-purchase_discount
report-print-send-15-0-base_report_to_printer
report-print-send-16-0-base_report_to_printer
server-backend-16.0-base_user_role
server-backend-16-0-base_user_role
server-env-16-0-server_environment
vertical-association-16-0-membership_extension
vertical-hotel-15.0-hotel_reservation

Da "Stéphane Bidoul" notifications@odoo-community.org

A "Contributors" contributors@odoo-community.org

Cc

Data Sat, 10 Jun 2023 12:32:03 -0000

Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

Hi Stefano,

I also support the idea, obviously ;)

Unfortunately that alone will not help get things moving as I have several other priorities with OCA infrastructure and tooling that already barely fit in the time I can allocate to it.

For instance, just preventing weblate to bring down the OCA server swallowed several hours already, recently (and there is still more to do).

I'm happy to tweak any configuration you propose but I'd need precise indications of what to do with links to the weblate documentation.

The process part also needs to be elaborated. The high level principle you mentioned sound good but how do we concretely do that in practice? For instance, when one asks to get translation access how will Rebecca know which role to give them? What is the process to accept a new reviewer for a given language? Can we have languages with reviewers and other without? Do we need to publish who has reviewer rights? What does all that imply in terms of weblate configuration?

Regarding glossaries and translation memories there are also important questions to be investigated. For instance, we now have one project per repo and branch. Is it possible to share glossaries across these? If not, should we / can we group them? Who should have permissions to manage glossaries, etc.

So there is quite a bit of research to do that, as far as I know, as not been done by anyone yet.

As I don't think these can be easily experimented live on the OCA instance (I may be wrong about that), I'd recommend anyone who would like to dive in that to setup a test weblate on their local machine and play with that to come up with a proposal or a plan. I'm happy to help with that too.

Best regards,

-Stéphane

On Thu, Jun 8, 2023 at 10:01 PM Stefano Consolaro <notifications@odoo-community.org> wrote:

Hi Stéphane,

did you give a look to mine and Sergio replies (i attached them below)?

Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.

We met Simone Orsi, OCA member, that support this idea.

In fact we think that what we are looking for could be useful for all language teams.

If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.

Obviously, we welcome all people willing to join the project.

Thanks for your time and help.

Stefano

Da "Stefano Consolaro" stefano.consolaro@mymage.it

A contributors@odoo-community.org

Cc

Data Mon, 23 Jan 2023 08:40:30 +0100

Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

I give my reply for italian language/community:
 

> Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect  or not so pertinent translations.
 

> What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.
Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
 

> How to make sure translation proposals are not stuck for too long waiting for review?
Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
 > Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.

Thanks for expanding the discussion, I hope others will join.

Da "Sergio Zanchetta" notifications@odoo-community.org

A "Contributors" contributors@odoo-community.org

Cc

Data Mon, 23 Jan 2023 10:36:56 -0000

Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

Il giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:

We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

Yes, you are right. :-)

Below, as italian community in addition to Stefano answers, you can find a proposal.

Here are a few questions that come to mind. There might be more.

- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?

The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).

 

- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.

- How to make sure translation proposals are not stuck for too long waiting for review?

I would replicate Transifex structure or similar, if possible. Here is a proposal:

- Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)

- There is a reviewer role, reviewed strings are freezed and can't be changed by translators.

-  The coordinator role has reviewer power and can appoint translators as reviewers.

The coordinator could be nominated by each localization repository PSC. (l10n-*)

He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.

- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

Sure, I add that not all communities have translation guidelines. [*]

[*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.html

Da "Stéphane Bidoul" notifications@odoo-community.org

A "Contributors" contributors@odoo-community.org

Cc

Data Sun, 22 Jan 2023 10:27:40 -0000

Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.

Here are a few questions that come to mind. There might be more.

- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?

- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.

- How to make sure translation proposals are not stuck for too long waiting for review?

- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.

Best regards,

-sbi

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

Stefano Consolaro

www.mymage.it

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe