Hi Darius,
good Job.
But isnt your work a rebuild of what gettext does except using xml files
and having all translations in one File ?
Or did I missunderstood your source ?
My approach would be like this as I dicribed in the MSG to Mattias:
- 1. Locate available Resource-Strings
- 2. Scanning the Application ContainerClasses TForm, TDataModule and
the included Tcomponents which has TTranslateString Properties by RTTI
- 3. Generating an XML - File with these ResourceStrings, Components and
properties (with optional context comments for the Translators, etc)
- 4. Translating the XML-File in other Languages
- 5. Provide a funktion or a mechanism to Translate the Forms,
Datamodules by reading back the Properies of the translated xml-files.
I would prefere XML because of the ability to have a hirarchical
structure similar to the Component.owner structure.
But there are the issues of the overhead and Performance.
Another Problem would appear if the component-names change or adding new
Components, removing Components in further versions of the Application.
Therefore I thought it would be better to have it integrated inside of
the IDE to make it easier for developers to keep the XML-Files up to
date.
What do You think ?
The approach by Vasily Volchenko is a very good one, but i don't know if
i can do that this way or complete his work.
Greetings
Tanila
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
