I deploy ERPNext in french, and I’ve add to deal with a lot’s of custom translation. My ERPNext users are gentle and accept the fact that some translation are not done, but it’s tricky each time in prospect demo.
We use lot’s of Doctype from lead/opportunity to selling, buying and manufacturing.
I also contributed to translation tools. Some of my translation suggestion where just not integrated, and stay in suggest during many months.
Even in ERPNext (version-12) the feature “contribute” do not work anymore.
There is a new feature to deal with context in translation, but i didn’t understand how it works, before in frappe 12, the core csv translation file have a first column look like “context like”, it’s no more the case in 13, but the “context translation feature” is only in 13, according the doc, I didn’t understand. Here the PR https://github.com/frappe/frappe/pull/9636
An example :
- translation key/word “Rate” in french can be a rate (%) or a price/amount (€), and it’s not the same meaning, it depend of the doctype.
- Fun fact (or not), on login page the word “show” to show the password is translated in french as “Spectable” => “a show” (like tv show yes…). I can make french user have fun or just fly away from Frappe/ERPNext. I suggested the fix in translation tools 7 month ago, still waiting.
Worst is in develop where if translation is missing the workspace and link to doctype just do not display, it’s like ERPNext is cut from 80% of his features. In English, it’s ok. Not always easy to debug when it’s a language related bug.
NB: you know how to deal with context translation doctype feature, how custom csv files in app deal with the context, or how specify context into translation core doctype, I’m ready to learn. As I see it must be specified when _(xxx,context) ot __(xxx,context) (so make a PR for all frappe/ERPNext code base with this)… Where specify this context in translation module or csv ?