Hey All you web programmers out there! How hard to you think it would be to rig up a web page for people to do translations for wine on? Have a web page (translate.winehq.org?) into which we feed in all the .rc files and maybe even parts of WineHQ, and show the translations for each language and bits that are missing ... then accumulate all the bits of translation somehow so they can be sumbitted back to wine-patches. I think there's plenty of people who'd do translation work for us if they didn't have to bother learning about how to submit patches or understand how .rc files work. Mike
Mike McCormack <mike(a)codeweavers.com> writes:
How hard to you think it would be to rig up a web page for people to do translations for wine on?
Have a web page (translate.winehq.org?) into which we feed in all the .rc files and maybe even parts of WineHQ, and show the translations for each language and bits that are missing ... then accumulate all the bits of translation somehow so they can be sumbitted back to wine-patches.
Others have already solved similar problems: http://translate.sourceforge.net/doc/tools-online_editors.html These tools are usually .po centric, but may still be useful. -- Feri.
Translations are cool, but before we ask for translation help, I think it would be prudent to finish up our rewrite of the documentation. This includes Brian's rewrite, which is dependant on winecfg functionality. There's also a lot of stuff on the site that needs to be worked over a bit, which I'm currently doing. So... 1) Finish winecfg and the site a bit so we know what to write about 2) Finish documentation so they know what to translate 3) Then ask for translators :) Thanks, Scott Ritchie On Wed, 2005-01-05 at 15:43 +0900, Mike McCormack wrote:
Hey All you web programmers out there!
How hard to you think it would be to rig up a web page for people to do translations for wine on?
Have a web page (translate.winehq.org?) into which we feed in all the .rc files and maybe even parts of WineHQ, and show the translations for each language and bits that are missing ... then accumulate all the bits of translation somehow so they can be sumbitted back to wine-patches.
I think there's plenty of people who'd do translation work for us if they didn't have to bother learning about how to submit patches or understand how .rc files work.
Mike
On Wed, 5 Jan 2005, Scott Ritchie wrote:
Translations are cool, but before we ask for translation help, I think it would be prudent to finish up our rewrite of the documentation. This includes Brian's rewrite, which is dependant on winecfg functionality.
That would be for translating the Wine documentation but that's not exactly what Mike proposed. Still once we decide it's ready to go translation the Wine doc should be quite feasible using po4a and the tools for handling .po files online that Ferenc Wagner mentioned. But .rc files are a completely separate issue: * they are ready for translation (with the exception of the winecfg one) * we can't use .po files, at least for now The main issue here is that translating a .rc file may imply resizing the GUI elements so that the translation fits :-/. * so we'll need to develop our own online .rc file translation tools So this part can be started now and seeing as how we now have pretty talented web developers on board it's certainly going to be exciting... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ A black hole is just God dividing by zero.
On Wed, 05 Jan 2005 15:43:58 +0900, Mike McCormack wrote:
Hey All you web programmers out there!
How hard to you think it would be to rig up a web page for people to do translations for wine on?
https://launchpad.ubuntu.com/rosetta It requires POT files though and we've found it to be rather unstable at the moment in autopackage. thanks -mike
Le mer 05/01/2005 à 01:43, Mike McCormack a écrit :
Hey All you web programmers out there!
How hard to you think it would be to rig up a web page for people to do translations for wine on?
Have a web page (translate.winehq.org?) into which we feed in all the .rc files and maybe even parts of WineHQ, and show the translations for each language and bits that are missing ... then accumulate all the bits of translation somehow so they can be sumbitted back to wine-patches.
I have (not much touched since maybe a year ago... sigh) some code (based on initial work by Dimi) to get a picture of what's done (and what's left to do). The output was in HTML, although it's not a web-app in any shape or form. I'll try to resurrect it (at least not to have any conflict with CVS wine) and post it here. Don't expect this before saturday (or go look in wine-patches archives if you can't wait). Vincent
Vincent Béron wrote:
I have (not much touched since maybe a year ago... sigh) some code (based on initial work by Dimi) to get a picture of what's done (and what's left to do). The output was in HTML, although it's not a web-app in any shape or form.
I'll try to resurrect it (at least not to have any conflict with CVS wine) and post it here. Don't expect this before saturday (or go look in wine-patches archives if you can't wait).
Actually, after thinking about it a little more, I think the best think to do would be just to offer one line of text (or maybe two or three) to translate, and an edit box to add the translations to. Text to translate could then be queued (manually at first, then maybe automatically later). The idea would be that people could translate a few strings as they visit WineHQ, without worrying about a complex interface that would allow them to choose what to translate, we'd just feed each person one random string from our queue of stuff that needs to be done. The translator would only choose which language they'd like to translate to. Mike
Le jeu 06/01/2005 à 04:56, Mike McCormack a écrit :
Vincent Béron wrote:
I have (not much touched since maybe a year ago... sigh) some code (based on initial work by Dimi) to get a picture of what's done (and what's left to do). The output was in HTML, although it's not a web-app in any shape or form.
I'll try to resurrect it (at least not to have any conflict with CVS wine) and post it here. Don't expect this before saturday (or go look in wine-patches archives if you can't wait).
Actually, after thinking about it a little more, I think the best think to do would be just to offer one line of text (or maybe two or three) to translate, and an edit box to add the translations to.
Text to translate could then be queued (manually at first, then maybe automatically later).
The idea would be that people could translate a few strings as they visit WineHQ, without worrying about a complex interface that would allow them to choose what to translate, we'd just feed each person one random string from our queue of stuff that needs to be done. The translator would only choose which language they'd like to translate to.
Without more context that'll be useless, you'd be almost better off using an automatic translation tool like Google's or Systran (for supported languages at least). Even with 2 or 3 "lines" (which I understand as strings enclosed in "", correct me if I'm wrong) shown at the same time, that doesn't solve the problem that .rc files define more than stringtables: dialog boxes layout (dependent on string length), icons and images (none are translated in Wine yet, but they could become), menu layouts, etc. There must exist some tools on the Win32 side of the Earth to deal with those things... Vincent
Vincent Béron wrote:
There must exist some tools on the Win32 side of the Earth to deal with those things... I searched once for something like this and afair I found only commercial applications for this. Seems the OSS guys prefer the PO system.
bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart
participants (7)
-
Ferenc Wagner -
Francois Gouget -
Michael Stefaniuc -
Mike Hearn -
Mike McCormack -
Scott Ritchie -
Vincent Béron