Hello!
We should try to update the translations of Wine to other languages for 1.0. The code freeze during the release candidate time frame is perfect for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or broken ones in the .rc files. But I seem to not enter the right search words to find any info regarding that; if somebody has a pointer please let me know. It would be nice if we could run that scripts regularly during the release candidate time.
bye michael
Michael Stefaniuc wrote:
Hello!
We should try to update the translations of Wine to other languages for 1.0. The code freeze during the release candidate time frame is perfect for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or broken ones in the .rc files. But I seem to not enter the right search words to find any info regarding that; if somebody has a pointer please let me know. It would be nice if we could run that scripts regularly during the release candidate time.
bye michael
You mean:
http://pf128.krakow.sdi.tpnet.pl/wine-transl/
Paul Vriens wrote:
Michael Stefaniuc wrote:
Hello!
We should try to update the translations of Wine to other languages for 1.0. The code freeze during the release candidate time frame is perfect for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or broken ones in the .rc files. But I seem to not enter the right search words to find any info regarding that; if somebody has a pointer please let me know. It would be nice if we could run that scripts regularly during the release candidate time.
Yepp! Thanks!
bye michael
On Tue, Mar 18, 2008 at 5:30 AM, Michael Stefaniuc mstefani@redhat.com wrote:
Hello!
We should try to update the translations of Wine to other languages for 1.0. The code freeze during the release candidate time frame is perfect for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or broken ones in the .rc files. But I seem to not enter the right search words to find any info regarding that; if somebody has a pointer please let me know. It would be nice if we could run that scripts regularly during the release candidate time.
bye michael
Would the Launchpad translations site be helpful?
https://translations.launchpad.net/
I think basically the workflow is:
* put phrases that need translation into the work queue. * select the languages it needs to be translated into. * people offer suggestions, and launchpad offers suggestions for the same phrase already translated in other projects. * pick the most appropriate suggestion. * watch the percentage bars go up.
(please correct me if this is inaccurate)
- Lei
Hello Lei,
Lei Zhang wrote:
On Tue, Mar 18, 2008 at 5:30 AM, Michael Stefaniuc mstefani@redhat.com wrote:
We should try to update the translations of Wine to other languages for 1.0. The code freeze during the release candidate time frame is perfect for this as the translations don't have to track a moving target.
Somebody had scripts/a web page to check for missing translations or broken ones in the .rc files. But I seem to not enter the right search words to find any info regarding that; if somebody has a pointer please let me know. It would be nice if we could run that scripts regularly during the release candidate time.
Would the Launchpad translations site be helpful?
Something like that would be useful.
I think basically the workflow is:
- put phrases that need translation into the work queue.
- select the languages it needs to be translated into.
- people offer suggestions, and launchpad offers suggestions for the
same phrase already translated in other projects.
- pick the most appropriate suggestion.
- watch the percentage bars go up.
(please correct me if this is inaccurate)
Wine is already there: "Translation setup needed The Wine project is not set up for translation in Launchpad. If you are Scott Ritchie, log in to begin the setup process. Otherwise, you might want to talk with Scott Ritchie, the project registrant, about using Launchpad for translations."
bye michael
On Tue, 18 Mar 2008, Lei Zhang wrote: [...]
I think basically the workflow is:
- put phrases that need translation into the work queue.
- select the languages it needs to be translated into.
- people offer suggestions, and launchpad offers suggestions for the
same phrase already translated in other projects.
- pick the most appropriate suggestion.
- watch the percentage bars go up.
I think the problem is extracting the strings to translate from the rc files, and combining the translations with the reference rc file to generate a translated rc file. Besides the issue of handling include files and macros, one aspect that spices things up is that the translation may need to tweak the widget sizes in order for the translated text to fit. How to represent that is not clear.
Still I think it would be doable with some conventions (e.g. prepend the geometry data to the string to be translated). Might make a good GSoC project:
Create a tool to manage rc file translations and integrate them with standard localisation tools such as the PO tools or https://translations.launchpad.net/.
One possible starting point would bethe po4a project. http://po4a.alioth.debian.org/
Btw, is the translations.launchpad using po files?
I think the release candidate phase for Wine 1.0 is a good time to add new translations and it's also important to fix out-of-sync resources. They may cause programs to run incorrectly when running under with a different language (I've filled a bug about it: http://bugs.winehq.org/show_bug.cgi?id=12097). The lanuchpad looks interesting. What's the format for importing/exporting data from it? Extracting strings from a *.res is quite easy. Building a *.rc from a *.res and strings is also not too hard. It would be more tricky if we would like to extract the #define'd symbolic names of resources or comments. There is the problem of changing dialogs geometry (but we could use special files for that and write a dialog editor to edit them) and that sometimes the same string have different translations - e.g. in same langauges the column "Size" for directory view (where it means file size) is translated differently then the column "Size" in My Computer (where is means disk size). But that can be solved by preppending the string id to the string. Having string in different files than the resources would also help fixing out-of-sync resources (we could use English string if translated ones are not available).
Mikolaj Zalewski