Internationalization of content

[elis]

Hello, everyone,

I'm a long-term user of various CRM systems and have started to shift some of the organizations I work with towards EspoCRM, but I bumped into a situation I don't know how to solve and couldn't find any recent information about.

The context is as follows: I'm setting up the CRM for a mostly B2B organization, which activates in Germany, but wants to serve customers in multiple languages. This means being able to generate quotes, sales orders, invoices and various other documents in either German or English (potentially more down the line). Are there some best practices regarding how this could be done, when it comes to extending the entity models (with preferred communication language, for example/) and document templates (email, quote, invoice etc.)?

The latest conversation around this I could find was from a very long time ago with no follow-up, but maybe my search-fu fails me - would appreciate some insights from the more advanced users out there!

Cheers,
Elis.

[shalmaxb]

I have an App with German and English, which I made multilanguage in the following way.

1. I have an enum field with the options German, English and both (both I use for the translation edit of content, as with both all fields for German and all fields for English are displayed in one detail view).
2. I created all my fields for German and all fields for English. When in language selector is choosen both, all fields are displayed. This I achieved by making the layout in a way, that every field block in every language has a panel of its own. So i can hide or show, according to the language selector.
3. For field with fixed content, e.g. an article name or a description, that always stay the same, I made the translation automatically with formula, like ifThen(wordGerman == 'Wort', wordEnglish = 'word'); This fills the english field with word, when you write Wort. This way I have a bunch of fields already translated, without touching the translation.
4. For other content, which is different for each case you have to make a manual translation. I use for that a browser Extension named "Web-Übersetzer, Wörterbuch - einfache Übersetzung". With that extension I can select a text on the fly and a popup opens with the translation, which has a copy button.

[elis]

Thank you for that, shalmaxb greatly appreciated! It does feel like a lot of relatively advanced work and a potential absolute pain in the ass when it comes to supporting a new locale/language :-)
I also did a bit more digging and looks like there's one extension provider that did some work towards i18n-friendly entities, which I guess would help shortcut this process a bit.

I'm guessing l10n/i18n content isn't very high on the list of things to look into when it comes to roadmap, right? It would be helpful to know when it comes to planning with future projects.

[shalmaxb]

i18n files are only for translating field-label names, not content..