Hello



I have 2 Problems :



1.



In MessageEditor i had defined my messages.

for German-Language i translate buttons with German Caption.



When i run Application Messagetext appears in German

only Captions of Buttons are in English.





2.



in AppMAin where i set Datasource







Dialog appears in English



So what did i wrong ?





Thanks for your help



Rainer

Hi Rainer.

Have you embedded your Localization Files into your project?

Hi Ivan



thanks for reply



Yes i did



Also i check again Message_languages.xml



-

5

3

1031

deu

Ja

Nein

Wiederholen

Abbruch

Event ID

true

2008-11-19T16:37:42.983+01:00



-

4

3

1033

eng

Yes

No

Retry

Cancel

Event ID

false

2008-11-19T16:36:22.86+01:00





Here are Translations correct.



Any new idea ?



thanks



Rainer

You also embedded your Messages_1031.XML file, right?

Please, try registering your XML in code, in the InitApplication sub:

Sorry, were you see "Offisys.ProFilmeNET", just put your NameSpace...

Hi Ivan



Thanks for your help.



I changed now to External XML and it works fine with Messagebox.



But for DataBaseConnectionWizard it doesnt work.



Is this wizard Pre-Localized ?





Rainer

Good you got it working, but I think you could insist a bit more to get your Embedded XML Files working, since this is really the recommended way. If you feel like keeping on trying, don't worry about posting any doubts you get during the process, we will get there.

As for the Connection Wizard, I have a feeling it is not pre-localized yet.

Hi Ivan



Thanks again for your help.



Then i must ask Trent .





Trent, is the Database-Connection-Wizard localized ?



If not, how can i handle this in best way ?



thanks



Rainer

No. The Connection String Wizard is one of the few items that is not pre-localized.  The reason that it isn't is because most developers choose to use their own connection mechanism versus the Connection String Wizard in the field.  In truth, you could create your own connection dialog quickly and easily and manually set the connection, which like mentioned, is what most developers elect to do.

In our medical application, we never ask for a connection from the workstations, only the server.  The workstations all look for the server (UDP or IP) and once found, the server sends the workstation the connection string.  This makes it MUCH easier than trying to setup every workstation.

Other developers have a central location to which the workstations look (similar to our server approach minus the server) and then pull the connection string from that location when the workstation fires up.

We will more than likely localize this dialog in the next major version, but at present, it would require a significant amount of effort to retro-fit this.

hello trent





thanks for the info



Rainer