Multilingual EA repository

[miron]

Would be amazing to have possibility to crate multilingual RTF reporter or HTML.

That means: name, notes, RTF embedded notes , tag value, tag value notes, scenarios and others should has possibility to write various cotnent for given language.

And additional view which in grid could choose columns for language and make quickly translation.

And next in RTF generator I could choose language of content....
Maybe it is only dreams  , but sometimes dream could be reality.

[qwerty]

Does not get my vote. Anything in that direction would mean a) complete new repository type (well, that would be worth it ), b) to make the whole program extremely complex and c) to increase the price of EA. There are more basic things I'd like to see first (like bug fixing and some other more general features).

Just as a side note: if you create a multi-lingual repository this will mean (except you have some Google Translator as the back bone) that you will have duplicate/redundant information. And if you don't maintain both in parallel (which illusionary) your model is simply scrap since you don't know which of the redundant informations is the right one.

q.

[miron]

Thank you for your remarks.
Re a and b)

no, it is just one table with language resource
this table could has columns

• value - blob for notes or rtf
• status - to inform about status translation
• some columns with dates
• foregin keys to object, rtf notes and others

and of course there are some additional effort

- Main language will be this which you write in main tables
(that means values which was written in GUI )

- Additional smart grid to manage translation
this grid will use language resource.
which show main language value and column to translation

and least change to retrieve values for text and rtf in reporting

Re c)
I think now, but at least
e.g. it could be feature which could be available in unlimited version

Re: Just as a side note
This functionality could open for EA area of new customers .

Could you imagine how its big effort to maintain translation in e.g. word?
And when you create big RTF report in EA you need make translation not buy google translator . But when you generate new version e.g. in English how you can find difference in german word document?

Maintain would be very easy. When you change some text you EA could compare data of change and data of last translation and status and tell you that you should update translation for given field.

It is not for goggle translator . But it is for bigger company which has team and customers which need document in own languages.


Summarization:
That means in my opinion it is not big revolution in repository.
And allow EA to get new customer. E.g. which need create international documents, manuals. Of course I only can ask, it is not my role to set priority for EA team :-).

Thank you once again for your remarks.
 

Does not get my vote. Anything in that direction would mean a) complete new repository type (well, that would be worth it ), b) to make the whole program extremely complex and c) to increase the price of EA. There are more basic things I'd like to see first (like bug fixing and some other more general features).

Just as a side note: if you create a multi-lingual repository this will mean (except you have some Google Translator as the back bone) that you will have duplicate/redundant information. And if you don't maintain both in parallel (which illusionary) your model is simply scrap since you don't know which of the redundant informations is the right one.

q.