Question:
I would like to have some inputs on how you deal with all the texts fields in BW when you have a multi langual community ?
Like, what is your procedure for the translation of texts that have to appear in queries (column header, query name, variables,...)
And what about the texts that are not for end-user use (infopackages, process chains...)
My request for queries seems obvious, while I understand the one about server_texts may be less clear, let's take a sample. I define a process chain in chinese with correct names for infopackages. Somebody else wants to look at this process chain, and connect bw in english. In this case, the chinese names will be replaced by the technical name of the infopackage -> it will look like chinese , but not really convenient...
Ch
Answer:
Hi CHC,
I am not sure on understanding your question, but for InfoObjects, InfoPackages and so on, you can translate them from RSA1. You have the button translation. It works like BCT. You can choose source language and target.
The only problem is translating text variables. The only way I know to translate them is to access system in target language, edit variables and translate.
Answer:
I don't have a technical problem on how to achieve it ;
I've got a procedural problem on when it should be translated, and to wich extent.
For the infopackages, for instance, I don't think I can ask my colleagues to translate everything in the three working languages we have here, but if we don't translate we receive the unreadable technical name instead.
--> if you have a process chain defined in french, it's not readable in english, you need to connect in french
So I will propose here that we choose one language that everybody should stick to for such things, but was wondering how it's adressed in other companies.
Ch
Answer:
We managed the problem in saying : we are a multinational company, so everybody who uses BW is/should be english speaker/reader (even if bad)... so no translations.
_________________
When my car stops, I first look at the gasoline's level before dismounting the engine.
Tuly Idiot's fan club active member.
Answer:
c'est ça, fous-toi de ma gueule, en plus
I promise you that as off I will have been accounted CEO of my current company, I'll take the same decision.
But for now on, I welcome any other comments/suggestions/ideas.
Ch
Answer:
Hi,
We are working in a multilingual environment and we translated everything an end-user (BEx Analyzer user) can see. So Infocubes, InfoObjects, variables.
We didn't translate Infopackages, process chains, and so on because they are only used by system administration group, and they are all same language speakers.
So I think it will depend on your case.