Upgrading from 2.x
The following moments should be considered:
- DKLang starting with version 3.0 outputs language source files (.dklang) solely in Unicode. It is also preferable
to use Unicode translation files (.lng) as well, but the package still can read ANSI files produced by version
2.x. It uses LANGID parameter value to properly convert file contents into Unicode, so loading a translation takes
a bit longer because the loading occurs twice (first time to determine the language ID, and second time to load
the file with a correct code page).
To be able to load Unicode .dklang and save Unicode .lng files you have to upgrade DKLang Translation Editor to
version 3.0 or later (if available). The program will warn you if you will try to save ANSI translation based on
an Unicode source, and vice versa.
- DKLang starting with version 3.0 stores constants in a separate resource file (project_name.dkl_const.res)
instead of project resource file (project_name.res). This allows editing constants in Delphi 2005 and later
thus overcoming inaccessibility of project resource interface (IOTAProjectResource) in those IDEs (this bug was
introduced in BDS 2005 and still persists in BDS 2006).
If you were using DKLang 2.x constants, you should convert all your projects using the
Converter, and add the following line to project source files (.dpr):
{$R *.dkl_const.res}
Converter from 2.x
File: Converter_v2\DKLang_Converter_v2.dpr
Compile the converter using your IDE (most recent DKLang version must be installed before) and use it to split
project resource file project_name.res to DKLang constant resource file project_name.dkl_const.res, and
optionally to remove constant resources from the project file (you must remove it or duplicate resource name will be
reported).
You can also download a
precompiled Converter executable.