2. F.A.Q.

Globalize your Delphi applications without troubles

Frequently Asked Questions

Q: I don't use Humanize option, because I couldn't find any suitable delimiter: when the delimiter found in the string, the kdlscan stops processing exe and leave incomplete lng file.

A: That's right. But you can use ANY STRING as delimiter, not only just one '\' character (for ex. '\*\', '/*/', '(*)', '+++', '<>' etc.). Set it in kdlscan.ini, HumanizedCR option.

Q: The K.D.L. can't translate all textual properties of the specific third-party component that I use in my application...

A: It is possible if this component override common .dfm file saving behavior. You can use the property name substitutions to workaround it. See kdlscan.ini for example with TVirtualTree (http://www.delphi-gems.com/VirtualTreeview/). Please e-mail me if you have problems with it or any other Delphi component.

Q: What is the String Version Control System? How it works?

A: The String Version Control System (SVCS) was introduced in KDL 3.0. SVCS can track all modifications you made in DFMs and string resources of your application.

Now all modified strings can be marked with the (!) sign, and old versions of modified (obsolete) strings can be marked with the (x) sign (as well as deleted strings). At the same time a version number of the modified strings will be increased.

To allow the SVCS to work, you should give the kdlscan utility an original language file of the previous version of your program.

Let we have this line in application.lng for our Application v.1.0:

cbAutoTranslation.Caption=Auto translation

Let in Application v.2.0 this string was modified to "Auto translate". After running the kdlscan utility you will get:

cbAutoTranslation.Caption{1}=Auto translate

where {1} is a version number of given string.

In turn the lngupdate utility recognizes version numbers and updates .lng files accordingly for all available languages.

downloads page >>