Wine po issue page broken?
Hi Francois and list, the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time. It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016. First of all, did I miss something? I find that page quite useful, personally. What about the other translators? Seems there is not much interest...? http://source.winehq.org/transl/ is broken for me as well. It would be nice to hear from other translators, how much do you use these pages, would you like them to be fixed? If it's just me, please don't bother; otherwise it would be great if someone could look into it! All the best and a happy new year to everyone! Julian
On 2017-01-10 13:11, Julian Rüger wrote:
Hi Francois and list,
the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time.
It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016.
First of all, did I miss something?
I find that page quite useful, personally. What about the other translators? Seems there is not much interest...?
http://source.winehq.org/transl/ is broken for me as well.
It would be nice to hear from other translators, how much do you use these pages, would you like them to be fixed? If it's just me, please don't bother; otherwise it would be great if someone could look into it!
All the best and a happy new year to everyone! Julian
I've noticed this, too. The page was very useful when my translation was in progress. However, after reaching 100% I haven't needed it anymore. To stay up-to-date, I'm currently using my own script, which I run (with cron) every thursday and friday to catch any po changes. #!/bin/sh # Usage: wine-po-check.sh [language] # Example: wine-po-check.sh fi STR="$(curl -so- http://source.winehq.org/git/wine.git/blob_plain/HEAD:/po/$1.po)" FUZZY=$(($(test -z "${STR/*fuzzy*/}" && echo 1) +0)) EMPTY=$(($(echo "$STR" | grep -A1 'msgstr ""' | grep '^$' >/dev/null && echo 1) +0)) test $FUZZY = 1 && echo "wine-po: $1: fuzzy" test $EMPTY = 1 && echo "wine-po: $1: empty" exit $FUZZY$EMPTY With proper spell checking, I could take a look at the Swedish translation, but the Swedish spell checking on wine-po has always been broken (includes dots in words and so produces hundreds of false positives). -- Lauri Kenttä
Hello Julian, On 01/10/2017 12:43 PM, Lauri Kenttä wrote:
On 2017-01-10 13:11, Julian Rüger wrote:
Hi Francois and list,
the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time. hmm, I missed that yesterday when I saved the ro.po errors and spell errors page. I wanted later today to look for new errors introduced by my patch.
It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016.
First of all, did I miss something?
I find that page quite useful, personally. What about the other translators? Seems there is not much interest...? Yes, when I do translation work (only during code freeze) I do look at that page.
http://source.winehq.org/transl/ is broken for me as well.
This page is from the time when Wine used .rc file for translations. So a lot of the errors that page caught are not possible now with the new po based translation.
I wanted to submit now a patch to just remove the transl from wine-tools. But as that operates on .res file and those are still generated during the build it can be made to work again fairly easy. parse_resfiles.php just needs to be adapted to work with the new Makefiles. And then we can decide if that is still useful or not. bye michael
It would be nice to hear from other translators, how much do you use these pages, would you like them to be fixed? If it's just me, please don't bother; otherwise it would be great if someone could look into it!
All the best and a happy new year to everyone! Julian
I've noticed this, too.
The page was very useful when my translation was in progress. However, after reaching 100% I haven't needed it anymore. To stay up-to-date, I'm currently using my own script, which I run (with cron) every thursday and friday to catch any po changes.
#!/bin/sh # Usage: wine-po-check.sh [language] # Example: wine-po-check.sh fi STR="$(curl -so- http://source.winehq.org/git/wine.git/blob_plain/HEAD:/po/$1.po)" FUZZY=$(($(test -z "${STR/*fuzzy*/}" && echo 1) +0)) EMPTY=$(($(echo "$STR" | grep -A1 'msgstr ""' | grep '^$' >/dev/null && echo 1) +0)) test $FUZZY = 1 && echo "wine-po: $1: fuzzy" test $EMPTY = 1 && echo "wine-po: $1: empty" exit $FUZZY$EMPTY
With proper spell checking, I could take a look at the Swedish translation, but the Swedish spell checking on wine-po has always been broken (includes dots in words and so produces hundreds of false positives).
On 01/10/2017 01:31 PM, Michael Stefaniuc wrote:
On 01/10/2017 12:43 PM, Lauri Kenttä wrote:
On 2017-01-10 13:11, Julian Rüger wrote:
http://source.winehq.org/transl/ is broken for me as well. This page is now fixed too.
This page is from the time when Wine used .rc file for translations. So a lot of the errors that page caught are not possible now with the new po based translation. As expected it is not very useful and the statistics are skewed too. It would be more useful if it would take into account the po files too. But that's an exercise left for the interested reader...
I wanted to submit now a patch to just remove the transl from wine-tools. But as that operates on .res file and those are still generated during the build it can be made to work again fairly easy.
parse_resfiles.php just needs to be adapted to work with the new Makefiles. And then we can decide if that is still useful or not. That wasn't the issue but the introduction of the first MENUEX resource in wine-1.9.20-117-g2878d1e. Thanks to Alexandre for pointing me to that and volunteering me to fix it...
bye michael
On Tue, Jan 10, 2017 at 9:11 AM, Julian Rüger <jr98(a)gmx.net> wrote:
Hi Francois and list,
the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time.
It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016.
First of all, did I miss something?
I find that page quite useful, personally. What about the other translators? Seems there is not much interest...?
I have silently used that page for a long time in the past and I was about to send a similar email because for me it is quite useful to have the % representation of the translations and what is wrong. So, I'd vote for updating before code unfreeze if possible. Best wishes, Bruno
On Tue, 10 Jan 2017, Julian Rüger wrote:
Hi Francois and list,
the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time.
It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016.
That's when I got tired of running WineTest on my desktop because it kept crashing KDE. Unfortunately the wine-po site was updated by the same script. I've tweaked and reenabled the relevant cron entry so wine-po should get updated again (but I'm not going to run WineTest again yet). -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Sufficently advanced incompetence is indistinguishable from malice.
Den 10. jan. 2017 12:11, skrev Julian Rüger: Hi Francois and list, the po issue page http://fgouget.free.fr/wine-po/ has not updated for quite some time. It shows abb221fa81b60f53c14f6864bbfb9453455aeeeb as its latest commit id (that is the git commit id, right?), which is the release of 1.9.14, July 2016. First of all, did I miss something? I find that page quite useful, personally. What about the other translators? Seems there is not much interest...? I've used this page in the past to easier catch errors in both my own and the old translation, and as such has been very useful to me. I would say both these pages are useful to both new and old translators, particulary new ones as they are a great place to start. At least that's where I started off. Happy New Year. http://source.winehq.org/transl/ is broken for me as well. It would be nice to hear from other translators, how much do you use these pages, would you like them to be fixed? If it's just me, please don't bother; otherwise it would be great if someone could look into it! All the best and a happy new year to everyone! Julian
Thank you for all your answers! Special thanks to Francois for fixing it so quickly! I was thinking it may be a good idea to merge the two pages, or host the po issues on winehq as well? I.e. offering po issues for both stable and master seems reasonable, now we have separate stable point-releases. I'd volunteer to look into it, no promises though! ;) (Francois, did you put up the source anywhere, or could you send it to me?) Best, Julian
On Tue, 10 Jan 2017, Julian Rüger wrote: [...]
I'd volunteer to look into it, no promises though! ;) (Francois, did you put up the source anywhere, or could you send it to me?)
I didn't because it depends on a perl script I wrote for CodeWeavers. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Be careful of reading health books, you might die of a misprint. -- Mark Twain
Francois Gouget wrote:
On Tue, 10 Jan 2017, Julian Rüger wrote: [...]
I'd volunteer to look into it, no promises though! ;) (Francois, did you put up the source anywhere, or could you send it to me?)
I didn't because it depends on a perl script I wrote for CodeWeavers.
OK, nevermind then.. :)
participants (6)
-
Bruno Jesus -
Francois Gouget -
Julian Rüger -
Kim Malmo -
Lauri Kenttä -
Michael Stefaniuc