- Mailing Lists
- Contributors
- Re: New Odoo17 translated fields
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: New Odoo17 translated fields
Beautiful ! Thank you very much David -)
With kind regards,
Van Hirtum Johan
Van: David Vidal [mailto:notifications@odoo-community.org]
Verzonden: donderdag 1 februari 2024 13:08
Aan: Contributors
Onderwerp: Re: New Odoo17 translated fields
The ORM does it for you. Simply use the `lang` context:
```python
record.with_context(lang='es_ES`).field_name = translated_string
```
You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.
El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:
Dears,
Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.
I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)
Thanks for helping me out.
With kind regards,
Van Hirtum Johan
_______________________________________________
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 Silvio Gregorini - 02:06 - 1 Feb 2024
Reference
-
OCA/connector-telephony Mantainers/PSC
Hello, is there an active maintainer of the OCA/connector-telephony repo? I saw that there are some people trying to migrate modules but no one is active to review/merge them.If there is no active PSC i volunteer as PSC of the repository, since i use these modules in v14.0 and now i need them in v16.0. So I volunteer to be the PSC and bring the repository back to life since it appears to be abandoned.I'm currently PSC of OCA/payroll and the other HR repositories, you can see some of my work there.Hope this week finds you well.
Kind regards.
by Nicolas Rodriguez Sande - 01:10 - 30 Jan 2024-
RE: New Odoo17 translated fields
Thank you Silvio, I didn’t know this way also -) I’ll try this to.
With kind regards,
Van Hirtum Johan
Van: Silvio Gregorini [mailto:notifications@odoo-community.org]
Verzonden: donderdag 1 februari 2024 14:08
Aan: Contributors
Onderwerp: Re: New Odoo17 translated fieldsSince v16, there's also a method made available by the ORM to update translations without overriding the context:
On Thu, Feb 1, 2024 at 1:52 PM Johan Van Hirtum <notifications@odoo-community.org> wrote:
Beautiful ! Thank you very much David -)
With kind regards,
Van Hirtum Johan
Van: David Vidal [mailto:notifications@odoo-community.org]
Verzonden: donderdag 1 februari 2024 13:08
Aan: Contributors
Onderwerp: Re: New Odoo17 translated fieldsThe ORM does it for you. Simply use the `lang` context:
```python
record.with_context(lang='es_ES`).field_name = translated_string
```
You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.
El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:
Dears,
Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.
I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)
Thanks for helping me out.
With kind regards,
Van Hirtum Johan
_______________________________________________
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 johan - 02:35 - 1 Feb 2024 -
Re: New Odoo17 translated fields
Since v16, there's also a method made available by the ORM to update translations without overriding the context:On Thu, Feb 1, 2024 at 1:52 PM Johan Van Hirtum <notifications@odoo-community.org> wrote:Beautiful ! Thank you very much David -)
With kind regards,
Van Hirtum Johan
Van: David Vidal [mailto:notifications@odoo-community.org]
Verzonden: donderdag 1 februari 2024 13:08
Aan: Contributors
Onderwerp: Re: New Odoo17 translated fieldsThe ORM does it for you. Simply use the `lang` context:
```python
record.with_context(lang='es_ES`).field_name = translated_string
```
You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.
El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:
Dears,
Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.
I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)
Thanks for helping me out.
With kind regards,
Van Hirtum Johan
_______________________________________________
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 Silvio Gregorini - 02:06 - 1 Feb 2024 -
RE: New Odoo17 translated fields
Beautiful ! Thank you very much David -)
With kind regards,
Van Hirtum Johan
Van: David Vidal [mailto:notifications@odoo-community.org]
Verzonden: donderdag 1 februari 2024 13:08
Aan: Contributors
Onderwerp: Re: New Odoo17 translated fieldsThe ORM does it for you. Simply use the `lang` context:
```python
record.with_context(lang='es_ES`).field_name = translated_string
```
You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.
El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:
Dears,
Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.
I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)
Thanks for helping me out.
With kind regards,
Van Hirtum Johan
_______________________________________________
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 johan - 01:50 - 1 Feb 2024 -
Re: OCA/connector-telephony Mantainers/PSC
+1
Thanks for stepping up Nicolas.
I did some contributions there a while ago, but haven't been active on it.
/Daniel
On 30/01/2024 12:46, Simone Orsi wrote:
Is great to see people stepping up to take over.Thanks! :thumbs-up:
Just open a PR against https://github.com/OCA/repo-maintainer-conf to change this https://github.com/OCA/repo-maintainer-conf/blob/master/conf/psc/connector.yml#L91
On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams
El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
OK for me.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Enric Tobella AlomarCEO & Founder
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Simone Orsi
Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 01:21 - 1 Feb 2024 -
Re: New Odoo17 translated fields
The ORM does it for you. Simply use the `lang` context:```pythonrecord.with_context(lang='es_ES`).field_name = translated_string```You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:Dears,
Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.
I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)
Thanks for helping me out.
With kind regards,
Van Hirtum Johan
_______________________________________________
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 - 01:05 - 1 Feb 2024
-