bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] many typo fixes


From: Jim Meyering
Subject: Re: [bug-gettext] many typo fixes
Date: Sun, 03 Jun 2012 22:03:12 +0200

Bruno Haible wrote:
>> Using the "misspellings" program from http://github.com/lyda/misspell-check,
>> I've massaged its output to create the following sed -i commands
>
> Thanks. This appears easy to use. Have you filtered out the false reports
> manually?

Hi Bruno,

I ran only the commands I mentioned in that report.
I performed no other filtering.  Note however that the command
I used there was an early version.  It did not handle
the case of a single quote (e.g., "doesn't") in the RHS.
This longer version of the command does handle that:

git ls-files|misspellings -f -|perl -nl \
  -e '/^(.*?)\[(\d+)\]: (\w+) -> "(.*?)"$/ or next;' \
  -e '($file,$n,$l,$r)=($1,$2,$3,$4); $q="'\''"; $r=~s/$q/$q\\$q$q/g;'\
  -e 'print "sed -i $q${n}s!$l!$r!$q $file"'

> I have applied the fixes to the files I maintain.
>
>> sed -i '463s!occurence!occurrence!' build-aux/texinfo.tex
>> sed -i '4787s!achive!archive","achieve!' build-aux/texinfo.tex
>
> This should be reported to bug-texinfo.

Both are already fixed at least in gnulib's texinfo.tex.

>> sed -i '375s!loosing!losing!' gettext-runtime/intl/dcigettext.c
>
> This should be reported to the glibc bug tracker.

Maybe later (but anyone else is encouraged to do it).

>> sed -i '1245s!thru!through!' gettext-runtime/intl/plural.c
>
> This one should be reported to bug-bison.

Just reported.

>> sed -i '206s!seperated!separated!' gettext-runtime/man/help2man
>
> And this one to bug-help2man.

It's already fixed there.

>> sed -i '96s!dum!dumb!' gettext-tools/doc/ISO_639-2
>> sed -i '281s!Timne!Time!' gettext-tools/doc/ISO_639-2
>
> These are false reports. I am impressed that other language names
> like Rapanui, Sasak, Sogdian, etc. were not reported ;-)
>
>> sed -i '274s!seldomly!seldom!' gnulib-local/lib/glib/gstrfuncs.c
>
> This one should be reported to GLib.

Maybe later (but anyone else is encouraged to do it).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]