Japanese Translation

All announcements, questions and issues related to the TsiLang Components Suite.
Post Reply
pmroberto
Posts: 4
Joined: Fri Jul 11, 2003 10:42 am

Japanese Translation

Post by pmroberto »

Hi all,

I am working with SIL files and Delphi 6.
I can see inside the TSI component the Japanese characters, but in the application it is not a Japanese character, it is different.

What I have to do to see the Japanese characters in a button, for example?

Thanks in advance.

Roberto
isiticov
Site Admin
Posts: 2383
Joined: Thu Nov 21, 2002 3:17 pm

Post by isiticov »

Hello,
As you discovered, some Delphi controls draw themselves using OS default locale and don't take in account the Charset property. These controls are wrappers of native Windows controls. Example of such countrols: TButton, TRadiobutton, TCombobox and others.
So as the solution of this problem could be either:
1. Use custom draw components instead of these controls. (3rd party)
2. Use Unicode components (3rd party), this will help you to show any language independent on default locale.
3. Do nothing but just adjust developer OS to be able to handle needed languages.

Some further details about each of point above:
1. This will require to change your project forms as well as code quite seriously. So it may be smarter to consider other two options.
2. Freeware with source Unicode TNT controls available from http://www.tntware.com offers the replacement for almost all standard VCL so the migrating will require just some DFM editing and may take minutes. This way allows to have and display any language at run-time you want. (But you still will need to adjust Charsets configuration in TsiLang, since it is used to perform ANSI <-> UNICODE conversion)
3. This may looks strange but in most cases you don't need to do anything special. Most users who will need to read your UI in their local language will have their language as default in OS and as result they will be able always to see English and their language. The only problem would be to configure your development OS to support needed language. So it may be worth considering this.

The most flexible way is to use option 2. Because actually the only way to support different (like German, Russian and Chinese or Greek) languages at same time is to use Unicode controls. In this way we've built our Resource Builder http://www.resource-builder.com , which was initially built as Ansi but easily converted to Unicode later and supports now any language.
Best regards,
Igor Siticov.
Post Reply