I have used my own format, with key-value pairs for original English string (key) and translated string (value)), I get the complete set of localizable strings from my source code, this info is added to the executables as a resource (.res) and Inside the source code, we have to call a translate function for a matching value for the key. If no value is found, the original English string is being used.
So, for now I am going to change my own system and use the standard translation system for Delphi projects.
Altrought, I think should be easy to transform our format to the .xlat format and build it as it is now. However, also I like the idea to extend the solution to support different project file formats using an internal system.
I will let you to know what approach I decide to follow.
Thanks.