Hi, I didn't update the translation statistics (http://www.mikolaj.zalewski.pl/wine-transl/) very regularly lately - my server is a bit broken and I can't run the scripts from cron but have remember to do it manually from a different computer. I have plans to fix it, but in the mean time, as some people may want fresh data, I have finished the changes I've been working on and uploaded the sources. It should be very easy to run them on ones machine and check the tree one has on disk - there is a README with explanations. The archive is available at http://www.mikolaj.zalewski.pl/dl/wine-transl.tgz . It is the latest version that adds support for dumping/diffing dialogs.
Mikolaj Zalewski
Hello,
Le dimanche 07 décembre 2008 à 02:15 +0100, Mikołaj Zalewski a écrit :
Hi, I didn't update the translation statistics (http://www.mikolaj.zalewski.pl/wine-transl/) very regularly lately - my
Your server seems down. Wouldn't it be better to host your script on WineHQ ?
Best regards
Jonathan Ernst napisał(a):
Hello,
Le dimanche 07 décembre 2008 à 02:15 +0100, Mikołaj Zalewski a écrit :
Hi, I didn't update the translation statistics (http://www.mikolaj.zalewski.pl/wine-transl/) very regularly lately - my
Your server seems down. Wouldn't it be better to host your script on WineHQ ?
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
Mikołaj
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
If you send me the necessary information I can probably take care of it.
If you send me the necessary information I can probably take care of it.
I've uploaded the lastest version to http://www.mikolaj.zalewski.pl/dl/wine-transl.tgz . There is a README there, but basically one needs to start with copying scripts/config-example to scripts/config and setting the paths. There should be a path to a Wine tree, a path to a temporary work directory and a path to the directory with the final data (all of these must be writeable by the scripts). With this set, one should do 'cd scripts && ./Master.sh'. This should create langs/ and dumps/ directories, first in the work directory and then move them to the final data directory (it's good for the temporary and final directory to be on the same filesystem for the move to appear to be atomic). It will also synchronize the conf directory in scripts/ with the one in the permanent data directory. With these files persent, the php/config.php should be edited to point to the final data directory. With this set, the PHP should show the translation state. I'm showing separate statistics for 1.1.x and 1.0.x by having the same code in two different places. The config.php contains some options that allow to use the same codebase for this (with changes only in config).
Mikołaj
Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
If you send me the necessary information I can probably take care of it.
And we of course need something to cope with the change to the clock resource files as mentioned by Michael Stefaniuc.
Paul Vriens schrieb:
Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
If you send me the necessary information I can probably take care of it.
And we of course need something to cope with the change to the clock resource files as mentioned by Michael Stefaniuc.
Or we should change our clock resources to fit in the rest of wine?
André Hentschel wrote:
Paul Vriens schrieb:
Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
If you send me the necessary information I can probably take care of it.
And we of course need something to cope with the change to the clock resource files as mentioned by Michael Stefaniuc.
Or we should change our clock resources to fit in the rest of wine?
You mean reverting Alexandre's patch? Doubt it.
Alexandre and I talked on irc about that. The --verify-translation functionality needs to move out wrc and into a separate tool that parses the .res files or the binary.
bye michael
Michael Stefaniuc schrieb:
André Hentschel wrote:
Paul Vriens schrieb:
Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
If you send me the necessary information I can probably take care of it.
And we of course need something to cope with the change to the clock resource files as mentioned by Michael Stefaniuc.
Or we should change our clock resources to fit in the rest of wine?
You mean reverting Alexandre's patch? Doubt it.
For now i dont't understand the sense of the patch...
On Mo, 2009-06-08 at 23:24 +0200, Michael Stefaniuc wrote:
And we of course need something to cope with the change to the clock resource files as mentioned by Michael Stefaniuc.
Or we should change our clock resources to fit in the rest of wine?
You mean reverting Alexandre's patch? Doubt it.
Alexandre and I talked on irc about that. The --verify-translation functionality needs to move out wrc and into a separate tool that parses the .res files or the binary.
When using the *.rc files, we could add --import and --export for *.po
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
It looks like there is a problem with CSS - some formatting is gone and I get a 403 forbidden on http://source.winehq.org/transl/style.css .
Mikołaj
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
It looks like there is a problem with CSS - some formatting is gone and I get a 403 forbidden on http://source.winehq.org/transl/style.css
Yep, should be fixed now.
BTW it would be nice to give it a more WineHQ-ish look, if someone feels like hacking up that CSS...
On Sa, 2009-06-20 at 19:19 +0200, Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. T
Thanks!
The results for Wone 1.0.x ( http://pf128.krakow.sdi.tpnet.pl/wine-transl/ ) won't open (tryied several times yesterday and today)
Is is possible to host a copy of the results on winehq.org ( http://source.winehq.org/transl-1.0/ ) to remove the load and bandwidth from Mikołaj's server or remove the Link to the Results from winehq.org?
The results for Wone 1.0.x ( http://pf128.krakow.sdi.tpnet.pl/wine-transl/ ) won't open (tryied several times yesterday and today)
The correct URL is http://www.mikolaj.zalewski.pl/wine-transl/1.0.x/ . This can be fixed in config.php (I've forgotten to update the example config in the sources). Of course, this can be also moved to WineHQ (by creating a new tree with the same PHP scripts, but with different config and data) to have everything in one place.
Mikołaj
Alexandre Julliard schrieb:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
Nice! I will have a look at the style and the clock-resource bug.
On 2009.06.20 20:19, Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
There is a problem with generating a new translation report. http://source.winehq.org/transl/runlog.php:
*** programs/winedbg/rsrc.rc [] Could not open ./work/tmp.res ./build-native/tools/wrc/wrc -I./wine/programs/winedbg/ -I./wine/include -I./build-mingw/programs/winedbg/ -I./build-mingw/include --verify-translation ./wine/programs/winedbg/rsrc.rc ./work/tmp.res 2>>./work/run.log >./work/ver.txt
Aurimas Fišeras schrieb:
On 2009.06.20 20:19, Alexandre Julliard wrote:
Mikołaj Zalewski mikolaj@zalewski.pl writes:
It's online again. Having it on WineHQ would probably give a better uptime (and a much better latency, but this should also improve on my side, when I won't need a temporary SSH tunnel anymore and will move the HTTP server from my good old Pentium 100MHz to a new Atom machine). I've been in contact with Jeremy Newman about it some time ago, but, after a few exchanges, my e-mails got unanswered, so I assumed he is too busy to help with it (and, alone, I don't know how to do it).
It's now online at http://source.winehq.org/transl/ and will be updated every time there's a git push. Please let me know if you find any problems. The source is also available now in the tools.git repository.
There is a problem with generating a new translation report. http://source.winehq.org/transl/runlog.php:
*** programs/winedbg/rsrc.rc [] Could not open ./work/tmp.res ./build-native/tools/wrc/wrc -I./wine/programs/winedbg/ -I./wine/include -I./build-mingw/programs/winedbg/ -I./build-mingw/include --verify-translation ./wine/programs/winedbg/rsrc.rc ./work/tmp.res 2>>./work/run.log >./work/ver.txt
Alexandre is already working on it.
-
Alexandre Julliard -
André Hentschel -
Aurimas Fišeras -
Detlef Riekenberg -
Jonathan Ernst -
Michael Stefaniuc -
Mikołaj Zalewski -
Paul Vriens