dg333 wrote:Referring to this thread
http://goldendict.org/forum/viewtopic.php?f=4&t=2538, I would like to ask: is there any specification of the localization file format available? The only thing I could dig is that the format is simplified version of another format. If the spec is available, I’d file an RFE of its support by OmegaT in order to ease the process of localization.
Hi! Thank you for your initiative to add new advanced localization support in Omega-T, I am sure it would be very beneficial for many users.
I would advise you make the following request to Omega-T developers:
"To add a new file setting option for Translatable text.
Namely, users should be able to instruct Omega-T which specific parts of a text are to be translated.
It can be done by indicating Opening and Closing patterns (symbols) inside a file to be translated.
For example, in PO file which Qt Linguist can handle the Translatable text would be -
* for Opening pattern: msgstr "
* for Closing pattern: "
It mean that the text to be translated is between msgstr " and " (spaces are to be taken into account) - all other parts would be deemed by Omega-T as untranslatable, hence become invisible during translation.
NOTE: there is no need to add a new file type to Omega-T since PO and most of other translation files are essentially text files. Translators just need to change file extension to ".txt", edit/translate in Omega-T as a text file, then upon completion, change again the extension to previous file type (to ".po" - for instance).
Sorry, that I have no time to make this request to Omega-T developers directly. But if you need my further help, write me anytime!