Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: [FIX]:Weblate - use po file download/upload - revisions
    Hi Rémi,

    Thanks for your investigation.

    Asking support from weblate is a good idea. The board agrees to free up a small budget to get specialized support and put us on the right track.

    I'll PM you with the details.

    Best regards,

    -Stéphane

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

    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 :

    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
    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
    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
    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
    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

    _______________________________________________
    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

    by Stéphane Bidoul - 11:05 - 30 Jun 2023
  • Re: [FIX]:Weblate - use po file download/upload - revisions
    Yes, let's do at least the move of sharing glossaries and TM.

    Regards.
    by Pedro M. Baeza - 09:01 - 30 Jun 2023
  • Re: [FIX]:Weblate - use po file download/upload - revisions
    Hi Rémi,

    Thank you for your work on this topic. The proposed approach seems very coherent and offers the opportunity for significant improvements in translation processes and quality. Automating translation by using a tool like deepl seems to me to be better in most cases than no translation at all. If the process for correcting inconsistent translations is simplified, this will undoubtedly encourage more people to correct these cases. Being able to share glossaries and translation memories between projects should also increase consistency in translating the same terms across different repos. Let's see what others think.

    Regards,

    Laurent

    On Thu, Jun 29, 2023 at 2:47 PM Stefano Consolaro <notifications@odoo-community.org> wrote:
    Hi Rémi,
    thanks for your work.

    Regardless what the OCA Board will decide to do with different functionalities of Weblate, I think that know how it can works is a good things.

    We (Italian community) are a bit suspicious on automatic translations. Suggestion can be a good thing, but auto-fill the translation is a bit risky.

    What we desire much is the implementation of the review process, that has to be only tested on Weblate and then organized by OCA.

    Keep share here the news to stay all together up-to-date.

    Ciao
    Stefano

    Da "Rémi CAZENAVE - Le Filament" notifications@odoo-community.org
    Cc
    Data Thu, 29 Jun 2023 12:12:00 -0000
    Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

    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 :

    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
    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
    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
    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
    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

    _______________________________________________
    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



    Stefano Consolaro

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



    --
    Laurent Mignon
    Senior software engineer
    T: +32 2 8883148


    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg

    by Laurent Mignon - 08:55 - 30 Jun 2023
  • Re: [FIX]:Weblate - use po file download/upload - revisions
    Hi Rémi,
    thanks for your work.

    Regardless what the OCA Board will decide to do with different functionalities of Weblate, I think that know how it can works is a good things.

    We (Italian community) are a bit suspicious on automatic translations. Suggestion can be a good thing, but auto-fill the translation is a bit risky.

    What we desire much is the implementation of the review process, that has to be only tested on Weblate and then organized by OCA.

    Keep share here the news to stay all together up-to-date.

    Ciao
    Stefano

    Da "Rémi CAZENAVE - Le Filament" notifications@odoo-community.org
    A "Contributors" contributors@odoo-community.org
    Cc
    Data Thu, 29 Jun 2023 12:12:00 -0000
    Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions

    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 :

    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
    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
    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
    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
    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

    _______________________________________________
    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



    Stefano Consolaro
    www.mymage.it
    by Stefano Consolaro - 02:45 - 29 Jun 2023
  • Re: [FIX]:Weblate - use po file download/upload - revisions

    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 :

    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
    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
    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
    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
    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

    _______________________________________________
    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

    by Rémi Cazenave - 02:10 - 29 Jun 2023
  • Re: Google Analytics Universal to GA4 for versions < 15.0
    For the record, for v14 Studio73 developed this compatibility module that replaces the tracking code: https://github.com/OCA/website/tree/14.0/website_google_analytics_4 (we just migrated it to v13 for our not yet migrated modules: https://github.com/OCA/website/pull/987).

    El vie, 26 may 2023 a las 18:37, Francesco Foresti (<notifications@odoo-community.org>) escribió:
    Hi, 

    has anyone worked on a module to implement the change described here:  

    Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.

    Which according to this post, amounts to

    insert de GA tracker code manually on `website.layout` changing the `async` attribute to `t-att-async="true"`

     ?

    If not, do you think a backporting from v15 is feasible?

    Thanks!

    Francesco
    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

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

    by David Vidal - 11:46 - 29 Jun 2023
  • Re: Packaging in the warehouse
    Yes, in that regard secondary units act only as helper of different uom equivalences and you wouldn't be able to tell how many kg of rice you have stored in your bags (and neither product.packaging in its standard form).




    El mié, 28 jun 2023 a las 23:42, Radovan Skolnik (<notifications@odoo-community.org>) escribió:
    Hello David,

I have gone through the code but I somehow fail to see how secondary unit could be used for the purpose. I could see the incoming package in a secondary UoM? Not sure I follow here. What would represent a 50kg bag (packaging) of rice (product)?

On the other hand, your suggestion for the other question (stock.quant.package and stock.package.type) seem quite relevant here. It would seem to me that stock.quant.package references:
A) stock.quant which in turn reference product_id (rice in this case)
B) stock.package.type which represents the kind of bag the rice is put into

The stock.package.type however does not limit the "amount" (in UoM) of stock.quant present in it, so not a perfect solution.

Or maybe I am missing something here. Would be happy if you explained further.

Best regards,

	Radovan

On streda 28. júna 2023 18:02:44 CEST David Vidal wrote:


> Take a look at our approach for this in the modules family


> product_seconday_unit which deals with these double format


> issues: https://odoo-community.org/shop?&search=secondary_unit


> 


> 


> El mié, 28 jun 2023 a las 17:47, Radovan Skolnik


> (<notifications@odoo-community.org>) escribió:


> 


> Hello,


> 


> another question for another customer. The customer is dealing with storing


> and distribution of food supplies. The way the products are modelled (in SAP


> which is the source of master data) is a product - for example rice, and a


> packaging - for example 50kg bag, 25kg bag, ...


> 


> So the first idea was to use Odoo's packaging. However Odoo does not use it


> for inventory management (inside warehouse). The different types of


> packaging could maybe be modelled as attributes for variants. But that


> doesn't feel right as well. In this scenario I would expect to be able to


> get a report of total amount of rice in the warehouse as well as grouped by


> different packaging types.


> 


> Any pointers are highly welcome. Thank you.


> 


> Best regards


> 


> 	Radovan Skolnik


> 


> 


> 


> 


> _______________________________________________


> 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

    by David Vidal - 10:21 - 29 Jun 2023
  • Re: Packaging in the warehouse 
    Jacques-Etienne,

but which of the module(s) you have in mind to model the situation? Not really 
sure here.

Best regards

	Radovan

On štvrtok 29. júna 2023 0:37:22 CEST Jacques-Etienne Baudoux wrote:

> Hi Radovan,

> 

> 

> Look at the OCA packaging modules

> in https://github.com/OCA/stock-logistics-warehouse/tree/14.0 for better

> stock integration of product packaging. I would not use the

> product_seconday_unit module as, by definition, a packaging is not a unit

> of measure.

> 

> 

> Regards

> J-E

> 

> 

> Le mer. 28 juin 2023 à 23:42, Radovan Skolnik

> <notifications@odoo-community.org> a écrit :

> 

> Hello David,

> 

> I have gone through the code but I somehow fail to see how secondary unit

> could be used for the purpose. I could see the incoming package in a

> secondary UoM? Not sure I follow here. What would represent a 50kg bag

> (packaging) of rice (product)?

> 

> On the other hand, your suggestion for the other question

> (stock.quant.package and stock.package.type) seem quite relevant here. It

> would seem to me that stock.quant.package references: A) stock.quant which

> in turn reference product_id (rice in this case) B) stock.package.type

> which represents the kind of bag the rice is put into

> 

> The stock.package.type however does not limit the "amount" (in UoM) of

> stock.quant present in it, so not a perfect solution.

> 

> Or maybe I am missing something here. Would be happy if you explained

> further.

> 

> Best regards,

> 

> 	Radovan

> 

> 

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe
    by Radovan Skolnik - 02:20 - 29 Jun 2023
  • Re: Packaging in the warehouse
    Hi Radovan,

    Look at the OCA packaging modules in https://github.com/OCA/stock-logistics-warehouse/tree/14.0 for better stock integration of product packaging.
    I would not use the product_seconday_unit module as, by definition, a packaging is not a unit of measure.

    Regards
    J-E

    Le mer. 28 juin 2023 à 23:42, Radovan Skolnik <notifications@odoo-community.org> a écrit :
    Hello David,

I have gone through the code but I somehow fail to see how secondary unit could be used for the purpose. I could see the incoming package in a secondary UoM? Not sure I follow here. What would represent a 50kg bag (packaging) of rice (product)?

On the other hand, your suggestion for the other question (stock.quant.package and stock.package.type) seem quite relevant here. It would seem to me that stock.quant.package references:
A) stock.quant which in turn reference product_id (rice in this case)
B) stock.package.type which represents the kind of bag the rice is put into

The stock.package.type however does not limit the "amount" (in UoM) of stock.quant present in it, so not a perfect solution.

Or maybe I am missing something here. Would be happy if you explained further.

Best regards,

	Radovan
    by Jacques-Etienne Baudoux - 12:35 - 29 Jun 2023
  • Re: Packaging in the warehouse 
    Hello David,

I have gone through the code but I somehow fail to see how secondary unit could be used for the purpose. I could see the incoming package in a secondary UoM? Not sure I follow here. What would represent a 50kg bag (packaging) of rice (product)?

On the other hand, your suggestion for the other question (stock.quant.package and stock.package.type) seem quite relevant here. It would seem to me that stock.quant.package references:
A) stock.quant which in turn reference product_id (rice in this case)
B) stock.package.type which represents the kind of bag the rice is put into

The stock.package.type however does not limit the "amount" (in UoM) of stock.quant present in it, so not a perfect solution.

Or maybe I am missing something here. Would be happy if you explained further.

Best regards,

	Radovan

On streda 28. júna 2023 18:02:44 CEST David Vidal wrote:

> Take a look at our approach for this in the modules family

> product_seconday_unit which deals with these double format

> issues: https://odoo-community.org/shop?&search=secondary_unit

> 

> 

> El mié, 28 jun 2023 a las 17:47, Radovan Skolnik

> (<notifications@odoo-community.org>) escribió:

> 

> Hello,

> 

> another question for another customer. The customer is dealing with storing

> and distribution of food supplies. The way the products are modelled (in SAP

> which is the source of master data) is a product - for example rice, and a

> packaging - for example 50kg bag, 25kg bag, ...

> 

> So the first idea was to use Odoo's packaging. However Odoo does not use it

> for inventory management (inside warehouse). The different types of

> packaging could maybe be modelled as attributes for variants. But that

> doesn't feel right as well. In this scenario I would expect to be able to

> get a report of total amount of rice in the warehouse as well as grouped by

> different packaging types.

> 

> Any pointers are highly welcome. Thank you.

> 

> Best regards

> 

> 	Radovan Skolnik

> 

> 

> 

> 

> _______________________________________________

> 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
    by Radovan Skolnik - 11:41 - 28 Jun 2023
  • Re: Proposing myself as Procurement & Purchase PSC
    +1

    El mié, 28 jun 2023 a la(s) 10:37, Fernando La Chica (notifications@odoo-community.org) escribió:
    +10000

    El mié, 28 jun 2023 a las 16:17, Carlos Liébana (<notifications@odoo-community.org>) escribió:
    +1

    El mié, 28 jun 2023, 9:12, Rafael Blasco <notifications@odoo-community.org> escribió:
    +1


    El mar., 27 jun. 2023 12:17, Harald Panten Lopez <notifications@odoo-community.org> escribió:
    Hi Community,

    I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).

    My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).

    Thanks!

    --


     

    Harald Panten López

    CEO

    Sygel Technology S.L

    		 
    		+34 613 04 76 66
    		harald.panten@sygel.es
    		https://www.sygel.es
    		C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     

    _______________________________________________
    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

    by Luis Romero - 11:05 - 28 Jun 2023
  • Re: Routes, trucks and gates
    Thanks Andreas 🙏👍

    Modules worked out pretty well. 

    --
    Maxime Chambreuil
    Desde mi móvil

    El mié, 28 de jun de 2023, 02:22, Andreas Hochuli <notifications@odoo-community.org> escribió:
    Hey Maxime

    Have a look at https://github.com/OCA/stock-logistics-transport/tree/14.0 (not everything migrated to 16.0 yet). With shipment_advice you can plan/merge outgoing stock moves into shipments, plan the (un)loading time and (un)load them. With stock_docks you can manage your docks and assign them to shipments. However, currently there is no fleet management or route planning involved but only a truck reference field on each shipment advice. But maybe this helps with the intralogistics part.

    Best Regards
    Andreas Hochuli
    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Andreas Hochuli
    Odoo Consultant
    Monday, Tuesday, Wednesday, Thursday

    +41 (0)79 755 71 94

    Camptocamp SA
    Leberngasse 21
    4600 Olten
    Schweiz


    New address from 1st September 2022


    Camptocamp SA

    Route de la Chaux 4

    1030 Bussigny

    Suisse


    Discover more about our new base camp office!


    On Wed, 28 Jun 2023 at 05:22, Maxime Chambreuil <notifications@odoo-community.org> wrote:
    Hello,

    I have a customer using Odoo 16 to manage his logistics operations: they have 2 warehouses with 12 gates, a fleet of 30 trucks of different sizes and a number of routes.

    I checked the transport repo but didn't find much there. Am I missing something? 

    Any suggestion that could help?

    Thank you
    --
    Maxime Chambreuil
    Desde mi móvil

    _______________________________________________
    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

    by Maxime Chambreuil - 10:46 - 28 Jun 2023
  • Re: Palette management in the warehouse 
    Hi David,

thanks for info. I somehow got misleaded with packagings where they say in the docs: "In Odoo, packagings are used for indicative purposes on sales/purchase orders and inventory transfers." Now I see packages and packagings are two different things. Will check them out. 

Best regards

	Radovan Skolnik

On streda 28. júna 2023 18:02:42 CEST David Vidal wrote:

> This very much how the core packages work (model stock.quant.package).

> Although the workflows for this maybe aren't the most intuitive.

> 

> 

> El mié, 28 jun 2023 a las 17:42, Radovan Skolnik

> (<notifications@odoo-community.org>) escribió:

> 

> Hello,

> 

> hope this is not a stupid question. Customer would like to have something

> like this:

> 

> *) a palette with multiple different lots (batches) of single product (or

> even with different products)

> *) the palette can be placed in a (palatte) location/position in the

> warehouse *) you can remove things from palette (put them in outgoing

> shipments for example)

> *) when all the contents of the palette is gone, the palette should

> "disappear" as well and effectively make the location/position free.

> 

> Has anyone dealt with something like this? Any pointers I could follow?

> 

> Thank you very much. Best regards

> 

> 	Radovan Skolnik

> 

> 

> 

> 

> _______________________________________________

> 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
    by Radovan Skolnik - 07:21 - 28 Jun 2023
  • Re: Packaging in the warehouse
    Take a look at our approach for this in the modules family product_seconday_unit which deals with these double format issues: https://odoo-community.org/shop?&search=secondary_unit

    El mié, 28 jun 2023 a las 17:47, Radovan Skolnik (<notifications@odoo-community.org>) escribió:
    Hello,

another question for another customer. The customer is dealing with storing 
and distribution of food supplies. The way the products are modelled (in SAP 
which is the source of master data) is a product - for example rice, and a 
packaging - for example 50kg bag, 25kg bag, ...

So the first idea was to use Odoo's packaging. However Odoo does not use it for 
inventory management (inside warehouse). The different types of packaging could 
maybe be modelled as attributes for variants. But that doesn't feel right as 
well. In this scenario I would expect to be able to get a report of total 
amount of rice in the warehouse as well as grouped by different packaging 
types.

Any pointers are highly welcome. Thank you.

Best regards

	Radovan Skolnik

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

    by David Vidal - 06:01 - 28 Jun 2023
  • Re: Palette management in the warehouse
    This very much how the core packages work (model stock.quant.package). Although the workflows for this maybe aren't the most intuitive.

    El mié, 28 jun 2023 a las 17:42, Radovan Skolnik (<notifications@odoo-community.org>) escribió:
    Hello,

hope this is not a stupid question. Customer would like to have something like 
this:

*) a palette with multiple different lots (batches) of single product (or even 
with different products)
*) the palette can be placed in a (palatte) location/position in the warehouse
*) you can remove things from palette (put them in outgoing shipments for 
example)
*) when all the contents of the palette is gone, the palette should 
"disappear" as well and effectively make the location/position free.

Has anyone dealt with something like this? Any pointers I could follow?

Thank you very much. Best regards

	Radovan Skolnik

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

    by David Vidal - 06:01 - 28 Jun 2023
  • Packaging in the warehouse 
    Hello,

another question for another customer. The customer is dealing with storing 
and distribution of food supplies. The way the products are modelled (in SAP 
which is the source of master data) is a product - for example rice, and a 
packaging - for example 50kg bag, 25kg bag, ...

So the first idea was to use Odoo's packaging. However Odoo does not use it for 
inventory management (inside warehouse). The different types of packaging could 
maybe be modelled as attributes for variants. But that doesn't feel right as 
well. In this scenario I would expect to be able to get a report of total 
amount of rice in the warehouse as well as grouped by different packaging 
types.

Any pointers are highly welcome. Thank you.

Best regards

	Radovan Skolnik
    by Radovan Skolnik - 05:46 - 28 Jun 2023
  • Palette management in the warehouse 
    Hello,

hope this is not a stupid question. Customer would like to have something like 
this:

*) a palette with multiple different lots (batches) of single product (or even 
with different products)
*) the palette can be placed in a (palatte) location/position in the warehouse
*) you can remove things from palette (put them in outgoing shipments for 
example)
*) when all the contents of the palette is gone, the palette should 
"disappear" as well and effectively make the location/position free.

Has anyone dealt with something like this? Any pointers I could follow?

Thank you very much. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 05:41 - 28 Jun 2023
  • Re: Proposing myself as Procurement & Purchase PSC
    +10000

    El mié, 28 jun 2023 a las 16:17, Carlos Liébana (<notifications@odoo-community.org>) escribió:
    +1

    El mié, 28 jun 2023, 9:12, Rafael Blasco <notifications@odoo-community.org> escribió:
    +1


    El mar., 27 jun. 2023 12:17, Harald Panten Lopez <notifications@odoo-community.org> escribió:
    Hi Community,

    I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).

    My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).

    Thanks!

    --


     

    Harald Panten López

    CEO

    Sygel Technology S.L

    		 
    		+34 613 04 76 66
    		harald.panten@sygel.es
    		https://www.sygel.es
    		C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     

    _______________________________________________
    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

    by Fernando La Chica - 05:35 - 28 Jun 2023
  • Re: Proposing myself as Procurement & Purchase PSC
    +1

    El mié, 28 jun 2023, 9:12, Rafael Blasco <notifications@odoo-community.org> escribió:
    +1


    El mar., 27 jun. 2023 12:17, Harald Panten Lopez <notifications@odoo-community.org> escribió:
    Hi Community,

    I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).

    My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).

    Thanks!

    --


     

    Harald Panten López

    CEO

    Sygel Technology S.L

    		 
    		+34 613 04 76 66
    		harald.panten@sygel.es
    		https://www.sygel.es
    		C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     

    _______________________________________________
    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

    by Carlos Liébana Anero. - 04:16 - 28 Jun 2023
  • Re: Routes, trucks and gates
    Hey Maxime

    Have a look at https://github.com/OCA/stock-logistics-transport/tree/14.0 (not everything migrated to 16.0 yet). With shipment_advice you can plan/merge outgoing stock moves into shipments, plan the (un)loading time and (un)load them. With stock_docks you can manage your docks and assign them to shipments. However, currently there is no fleet management or route planning involved but only a truck reference field on each shipment advice. But maybe this helps with the intralogistics part.

    Best Regards
    Andreas Hochuli
    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Andreas Hochuli
    Odoo Consultant
    Monday, Tuesday, Wednesday, Thursday

    +41 (0)79 755 71 94

    Camptocamp SA
    Leberngasse 21
    4600 Olten
    Schweiz


    New address from 1st September 2022


    Camptocamp SA

    Route de la Chaux 4

    1030 Bussigny

    Suisse


    Discover more about our new base camp office!


    On Wed, 28 Jun 2023 at 05:22, Maxime Chambreuil <notifications@odoo-community.org> wrote:
    Hello,

    I have a customer using Odoo 16 to manage his logistics operations: they have 2 warehouses with 12 gates, a fleet of 30 trucks of different sizes and a number of routes.

    I checked the transport repo but didn't find much there. Am I missing something? 

    Any suggestion that could help?

    Thank you
    --
    Maxime Chambreuil
    Desde mi móvil

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

    by Andreas Hochuli - 10:20 - 28 Jun 2023