cancel
Showing results for 
Search instead for 
Did you mean: 

UI: Multilingualism

Former Member
0 Kudos

Hi all,

has enyone knowledge, how to make my add-on language independent? I think, there is a way by using resource string, but no idea, how to use it.

Best regards

Libor Mego.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

I need my Add-on appers in 4 languages. I think, one possibility is to create 4 different versions of Add-on with differences in form's object-captions or user-messages. It's not aet_LanguageChanged event sensitive, but still possible and workable

Regards

Libor.

Former Member
0 Kudos

Hi

There is currently no easy way of doing it as far as I can see. The UI documentation suggests using a different XML document for each language you are trying to support and then using oCompany.Language to find out which document to load.

I think its a bad solution, since it requires alot of maintenance.

Instead I have tried another solution.

The problem is,.. when you run loadbatchaction the form becomes visible, so it will show up with the language that was in the xml file you loaded. It looks awfull if you use the form object to change the texts after it has become visible.

So,... only possible solution is to change the texts in the XML object before loadbatchaction. Its a bad solution, but it works ...

I hope a better solution will be available for us later, because editing the XML object directly is difficult and makes the load process slow.

Yours Sincerely

Mikael Kiilerich

Former Member
0 Kudos

You might consider storing the info of which the xml consists in the SAP database.

Just a thought. And better maintenance.

Lutz Morrien

Something like

Table

UID Lang_ID ControlType Property Value Parent

100001 1033 form title 'MyForm' Null

100001 1031 form title 'Mein Fenster' Null

XXX1 1033 button caption 'OK' 100001

XXX1 1031 button caption 'OK' 100001

Former Member
0 Kudos

It is not necessary to let the form become visible when you run LoadBatchAction. If you set the form property visible="0" in the XML, it will be invisible by default. This can be helpful if you are making changes of any type before presenting it to the user.