http://bugs.winehq.org/show_bug.cgi?id=12097
Dwayne Bailey dwayne@translate.org.za changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dwayne@translate.org.za
--- Comment #1 from Dwayne Bailey dwayne@translate.org.za 2008-04-24 04:17:47 --- Some solution suggestions that I can suggest based on rc2po: http://translate.sourceforge.net/wiki/toolkit/rc2po
Out-of-sync resources --------------------- Using the translation recovery approach: 1. rc2po -t En.rc Qq.rc Qq.po (first create a PO file with existing translations) 2. po2rc -t En.rc Qq.po Qq.rc (Now create an updated .rc)
The new output Qq.rc will contain everything needed from En.rc since po2rc uses En.rc as a template and will place English strings for untranslated items.
It cannot handle sub languages in the same file i.e. en_US and en_GB in the same file but you could get around that by creating En_Gb.rc. Also the recovered translations are based on the IDs within the .rc thus it cannot determine if for instance the translation of a DIALOG CAPTION is a translated based on the current English.
This method will ensure that the .rc is in sync with English even if many of the items are untranslated. If the .po files are stored in Git then these become the reference and can track the status of the translations.
Using PO/MO ----------- I would really recommend this. If WINE is able to use .rc files with a Mechanism that can extract and use Gettext like files then it makes the whole process of keeping translations up to date much much easier for everyone.
I would suggest extending xgettext to allow extraction from .rc files. Then WINE is free to work out a method of finding translations either at build or execution time, whichever makes the most sense.
In many ways with rc2po this would be possible to do now without any changes needed to create .rc extraction in xgettext.