n national business languages versus 1 technical &

[mbormans]

Tagged values permit adding names (aside each technical name) in different national languages, and these (tag+value) appear in documentation generated, that's already a good thing.
What is the right choice for definitions in the different national languages to be added? (Tagged values seem not to be memo-style fields) and (Notes seem to be untagged fields)... These definitions should be easily accessible from within the generated documentation...

The leftside tree-like structure is based upon the technical name of the any elements.
Pure businesspeople, with a very low tech-profile, already find it too difficult to find their way in such a tree, based upon a language which is A. technical and B. english-based.
When confronting pure businesspeople with documentation generated, it is a "nice to have" to be able to replace standard actor-images with nice and appealling images, but would it not be a "even nicer to have" to be able to replace the technical actor-name with some wording that really comes from the daily working environment of the businesspeople?
My question:
I would like to provide the user that navigation tree in his own national business language; meaning the branches are visible in and sorted based upon that national language, but the branching (or the nodes) are kept based upon the actual technical namings.

As a newcomer to the EA-world, i possibly raise some already existing question. So be it; i did not see how to first verify this full forum...
And yes, i am confronted with a mixed french, dutch, english and german user community...

[thomaskilian]

You might not want to hear it, but I found it easier to force English as standard language than to adopt EA to something else. It's basically not multi-language capable.

[mbormans]

If you are not interested in further widening your potential clientbase, you can stick to the easy way. (I'm not talking about myself here, but about EA getting into even closer contact/collaboration with businesspeople.)
You should understand that i gladly accept the value of english-based fundamentals, something i do not question nor want to change.
I merely wish to add some minimalistic multilingual information (essentially labels and definitions), and some minimalistic multilanguage capabilities for documentation purposes.
I have been experimenting a bit myself (I do not consider myself a programming expert), and presented these to my business environment. As the first reactions were quite positive, I think this all merits further attention.
On www.telebib2.org/DTDs.htm, under "27/09/2007 : some other tests", there are some links showing how it can be made a bit easier for business people to find their way within large stacks of information, by simply offering them that same info in their own language.

[thomaskilian]

I did not want to frustrate you, but I did find it rather fruitless to dig into multi-language support with EA. If the product is not designed for it, you will never be happy with the results. The Alias can help very, very little with two languages. But then it's simply over.

Good luck, however