Re: lyx-devel po/: ChangeLog postats.sh

[Michael Schmitt]

Angus Leeming wrote:

>Let's move on to the actual process of extracting info from the msgfmt run. It
>is more interesting and was quite challenging. You put a lot of effort into
>it and I didn't mean to stand on your toes. If you feel hurt, I apologise
>profusely.
>
That's not the point! I wanted to help the LyX community and I feel
responsible for fixing all outstanding problems by myself. But now it
seems that you also had to spent a lot of time on the script which was
not my intention at all :-(

The previous version worked fine for me (apart from the XHTML problems).
".*" might be greedy but does it really matter? The gettext output is
well-known (if it changes in the future, we have to fix the reg. expr.
anyway), performance is absoluty irrelevant, and the script is used only
by a few LyX developers.

>Point 2. Sometimes 'cut' is a better tool than 'sed'.
>
Thanks for the hint.

>I'm not saying that they did here, but you get my point.)
>
Yes (partially). I am not a supporter of "extreme programming" but I
wonder why you had to care about problems that don't exist. There are
still many real LyX bugs that deserve attention.

>Point 3. This is very neat and compact:
> make 2>&1 $y.gmo | grep "^[1-9]" |
> sed -e 's/\([0-9]*\) translated m[a-z]*[.,]/"msg_tr" => \1,/' |
> sed -e 's/\([0-9]*\) fuzzy t[a-z]*[.,]/"msg_fu" => \1,/' |
> sed -e 's/\([0-9]*\) untranslated m[a-z]*./"msg_nt" => \1,/'
>
>But it fails totally if there are no untranslated or fuzzy strings. (msgfmt
>simply doesn't output anything about them.)
>
Are you really sure? When I tested the script, there was a po file that
had no fuzzy/untranslated messages. The usage of "[.,] indicates that I
considered this case. If there was a problem then it occured at a
different place.

Michael