Translation status

773 Strings
5%
Browse Translate
14,351 Words
1%
99,209 Characters
1%

Strings status

Strings Words Characters
773 14,351 99,209
All strings Browse Translate Zen
45 61 404
Translated strings Browse Translate Zen
45 61 404
Strings waiting for review Browse Translate Zen
728 14,290 98,805
Unfinished strings Browse Translate Zen
728 14,290 98,805
Untranslated strings Browse Translate Zen

Summary

Project website www.odoo.com
Project reviewers46 User avatar cimaUser avatar ronmUser avatar mseaUser avatar paujUser avatar juauUser avatar madiUser avatar ngtoUser avatar petiUser avatar chwaUser avatar noplUser avatar anastasiia_odooUser avatar pagcUser avatar mfarUser avatar kwpaUser avatar lman_odooUser avatar wacmUser avatar Alina LisnenkoUser avatar hedsheferUser avatar cmd-odooUser avatar mapr-odooUser avatar GRCOodooUser avatar maan_odooUser avatar awt_odooUser avatar MichaelHadarUser avatar gezzzan …
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask locale/*/LC_MESSAGES/studio.po
Translation file Download locale/he/LC_MESSAGES/studio.po
Last change June 6, 2026, 3:48 p.m.
Last change made by None
Language Hebrew
Language code he
Text direction Right to left
Case sensitivity Case-insensitive
Number of speakers 9,402,620
Number of plurals 3
Plural type One/two/other
Plurals One 1
Two 2
Other 0, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula (n == 1) ? 0 : ((n == 2) ? 1 : 2)
06/18/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 773 14,351 99,209
Approved 0% 0 0% 0 0% 0
Waiting for review 5% 45 1% 61 1% 404
Translated 5% 45 1% 61 1% 404
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 94% 728 99% 14,290 99% 98,805
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 543 changes 0 changes 349 changes 0 changes 0 changes 0 changes 1 change 0 changes 13 changes 0 changes 717 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 76 changes 0 changes 0 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

14,351
Hosted words
773
Hosted strings
5%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+5%
—
Contributors
—
User avatar webhook:github

Resource updated
The “locale/he/LC_MESSAGES/studio.po” file was changed. 06/06/2026
User avatar webhook:github

String added in the repository
With Studio, you can :ref:`edit existing PDF reports <studio/pdf-reports/edit>` (e.g., invoices, quotations, etc.) or :ref:`create new ones <studio/pdf-reports/create>`.
 
06/06/2026
User avatar webhook:github

Resource updated
The “locale/he/LC_MESSAGES/studio.po” file was changed. 04/18/2026
User avatar webhook:github

String added in the repository
If the intention is to declutter the view, it is also possible to :ref:`modify a field <studio/fields/modify>` and make it :guilabel:`Invisible` on the view in question.
 
04/18/2026
User avatar webhook:github

String added in the repository
A removed field can be easily :ref:`added back to the view <studio/fields/add-existing>` at a later stage, if needed.
 
04/18/2026
User avatar webhook:github

String added in the repository
Click :guilabel:`Ok` to confirm the action.
 
04/18/2026
User avatar webhook:github

String added in the repository
Scroll to the bottom of the :guilabel:`Properties` tab, then click :guilabel:`Remove from view`.
 
04/18/2026
User avatar webhook:github

String added in the repository
To remove a field from a view, follow these steps:
 
04/18/2026
User avatar webhook:github

String added in the repository
Remove a field from a view
 
04/18/2026
User avatar webhook:github

String added in the repository
When updating the technical name of a field, make sure to keep at least the `x_` prefix, which is required for any custom field; for fields created using Studio, keep the `x_studio_` prefix to allow such fields to be more easily identified.
 
04/18/2026
Browse all translation changes