We need to interact with customers and sell our products in at least two languages (English and French). This means our content needs to be multilingual: item names and descriptions especially, but some other data as well. Has anybody figured out a satisfying way to use ERPNext in that manner? I’ve been looking through the forum and finding posts about translating the interface, but very little about translating the data.
I know fields can be made translatable and translations for those fields can be created using the Translation doctype, but that approach is rather limited, as I understand it:
- When translating, ERPNext seems to make no distinction between interface text and field contents: if no translations have been created for a translatable field, ERPNext will try to translate it by looking through the interface translation “dictionary”, which could have undesirable results (since translation in general can be very dependent on context).
- Suppose I have a translatable field with a given value, and I create a translation for it. If I notice a typo in the original value and fix it, ERPNext doesn’t know how to translate it anymore, even though the translation I had created is still perfectly valid.
- Translations are only tied to their original text and nothing else: if I translate the name of an item, there’s nothing in the database explicitly tying that translation to the item itself.
I have some rough ideas of how I might create my own content translation solution inside a custom app, but I’m still very new to ERPNext and am really curious to know:
- has anybody found/created some form of solution for this already?
- are there any translation improvements coming in ERPNext v16?
Thanks in advance for any responses.
Eric