I searched the forum and did not see any threads addressing this question, please refer me to a previous thread if this has already been discussed.
Our group is looking to extend use of a single Integrity 10.4 Production Server instance to groups who do not speak english or have trouble with english. Our build of Integrity has been developed/configured in English only. I've been tasked with brainstorming ways to present all field names on all item types in different languages, within the same Integrity instance. By this, I mean that Users must have a means of viewing a ticket and having the ability to see the field names in languages other than English. Field values are currently out of scope. My current thoughts are rather basic:
If there was a way to associate individual users with their respective languages, and then identify the language to present to each user based on this relationship, then it would be a lot more effective and professional. Has anyone else ever approached this issue or have thoughts/comments/ideas?
Please keep in mind, the following are untested ideas. I am not in a position to access any servers to test any of the following thoughts.
The option that I immediately thought of was number 2, but I would consider investigating: is it possible to determine the user ID, and then choose the language based on that? Possibly with an IBPL that maps a type to a user's preferred language. I believe we have done this internally in the past for other functionality.
If you could tie that functionality to the Item Template Presentation (IPT) rules or relevance rules that you are using, you could have the item automatically adjust the language on the IPT to be appropriate to the viewing user.
Even if you can make this work, I expect maintaining the item presentation templates will be challenging on dynamic item types.
How many users do you have working in non-English languages? Are they altering the item types, or are they simply looking at the item types to get information? If the latter, it might be possible to make a "translation type" with FVAs as well. This method is very limited compared to your other options, though.