Different terminology by tenant

[andreslucena]

This issue is part of the EPIC: Improve Multitenant #4693

Each organization has different terminology for communication with its users (for example: citizens, associates, affiliates, sympathizers, vote, support).

So that this adaptation is not too costly economically will be made through YAML files defined by each instance through the i18n API of Ruby on Rails, and improve project documentation so that these changes can be proposed through GitHub by people that are not developers.

Discussion on MetaDecidim

[mrcasals]

You'll need to manually replace the whole strings, and you'll need to identify what keys you need to overwrite. For example, if you want to replace "asambleas" (Spanish word, with a feminine gender) to "órganos" (masculine gender) you need to adapt the whole sentence so that genders match.

Example, a this key:

highlighted_assemblies: "Asambleas destacadas"

A naive approach would be doing something like this:

highlighted_assemblies: "%{assembly_name} destacadas"

And call it like this form Rails: t("highlighted_assemblies", assembly_name: "Órganos"), but this would result in "Órganos destacadas", with a gender mismatch.

You'd need to find all relevant keys, and replace them. And, more difficult, you'll need to check this for every update.

This, unless someone comes up with abetter solution, of course! 😄

[andreslucena]

Related with this:

• https://meta.decidim.org/processes/roadmap/f/122/proposals/12401
• https://meta.decidim.org/processes/roadmap/f/122/proposals/12143

[ahukkanen]

I'd like to add here that we are currently developing a module that allows customizing specific terms from the UI:
https://github.com/mainio/decidim-module-term_customizer

It allows you to map the specific term customizations to different contexts, including:

• Specific organization (the one you are currently logged in at)
• Specific participatory space (selecting from a list of all spaces)
• Specific component (selecting from a list of components in the selected participatory space)

UI-wise it could be improved, e.g. searching a translation key from all terms since now you have to know the key. But the basic functionality should be there. UPDATE: Searching the translation keys has been added as a feature.

Feel free to play around and test it out, we welcome any comments. It's mostly done for what it's aiming to do but it hasn't been thoroughly tested in an actual instance yet. That should also happen pretty soon after which it's ready for a release.

[mrcasals]

@ahukkanen wow, looks promising! @andreslucena would this solve the issue for you? 😄

[andreslucena]

@ahukkanen looks pretty well, we'll check this out, thanks :D

[ahukkanen]

@andreslucena Cheers, feel free to leave any feedback, it's still pretty new.

Update also to the previous comment that we have now released the first version which also ships with the translation searching UI. It's been installed also to an actual instance where it is being tested in a live environment as we speak.

Because of this, I've also removed the development status notices from the README.

[mrcasals]

@andreslucena can we close this issue then?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. @carolromero & @xabier feel free to chime in.