Using the Borland dictionary component

[bnothos]

I am stuck translating piles of prompts in my company's borland builder 6.0 based product. I find the dictionary editing tool in Borland to be cumbersome and almost impossible to use. Even with a modern 2.0GHz + workstation it still takes forever to switch from dialogue to dictionary tabs.

Does anyone know of a alternative way to edit the .dct file other than using Borland Builder? Or does anyone have any success stories / techniques to using the dictionary that would make it less of a pain in the @$#! to work with?

Any help would be greatly appreciated!

 

[bnothos]

I should also mention that I'll have to repeat the process in the antiquated Borland Builder 3 for an older version of our software. The tool between these 2 versions doesn't seem to have changed much. 3 is no worse than 6 considering the age difference.

Does anyone know if the .dct files are compatible between versions?

 

[bnothos]

hmm chatting to myslef apparently... So no one uses the dictionary tool? Or those that do actually like it? Perhaps no one makes multi-lingual software?

 

[finnmike]

Dear bnothos,

I do plan to do a multilingual version of my application, but this waill take some time...

But my first task was to tell my compiler that i did not wnt it to compile all messages with german texts, as it did in the first versions.

My way around the dictionary was to install the complete english version of my bcb, and, here it was, all in english.

I managed to find the poitn in the included libfiles ($BCB$/Vcl). when I changed the german vcl libs into the english ones I alos had the right messages.

maybe this is another way around:
to get hand on different language versions of the complete bcb.

More I do not know yet.

best regards,

Michael

 

[bnothos]

If I understand this correctly, you're talking about built in system messages provided by Borland?

I am referring to custom label, menu items, title bars, prompts etc...