-
-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
helpdesk_mgmt: Wrong French translation filename #374
Labels
Comments
houzefa-abba
changed the title
helpdesk_mgmt: Wrong French translations filename
helpdesk_mgmt: Wrong French translation filename
Nov 7, 2022
Please go with 1 |
zuher83
pushed a commit
to zuher83/helpdesk
that referenced
this issue
Feb 27, 2023
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
chandni-serpentcs
pushed a commit
to chandni-serpentcs/helpdesk
that referenced
this issue
Jan 3, 2024
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
reichie020212
pushed a commit
to OpenSPP/helpdesk
that referenced
this issue
Feb 13, 2024
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
giarve
pushed a commit
to wvbs/helpdesk
that referenced
this issue
Oct 11, 2024
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
imlopes
pushed a commit
to imlopes/helpdesk
that referenced
this issue
Oct 24, 2024
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
giarve
pushed a commit
to wvbs/helpdesk
that referenced
this issue
Oct 26, 2024
Fix OCA#374 - Odoo expects `fr.po` for French translations, not `fr_FR.po`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
French localization files Odoo expects are
fr.po
, notfr_FR.po
In this repo in the 15.0 branch:
fr_FR.po
- wrong ❌fr.po
- ok ✔️I checked on runboat, activating the French language does fail to load
fr_FR.po
Solutions, which would you prefer?
fr_FR.po
➔fr.po
fr.po
&fr_FR.po
next to each other, would be confusingThe text was updated successfully, but these errors were encountered: