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: Bruno Haible
Subject: Re: [bug-gettext] many typo fixes
Date: Sun, 03 Jun 2012 21:39:40 +0200
User-agent: KMail/4.7.4 (Linux/3.1.10-1.9-desktop; KDE/4.7.4; x86_64; ; )

Hi Jim,

> 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?

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.

> sed -i '375s!loosing!losing!' gettext-runtime/intl/dcigettext.c

This should be reported to the glibc bug tracker.

> sed -i '1245s!thru!through!' gettext-runtime/intl/plural.c

This one should be reported to bug-bison.

> sed -i '206s!seperated!separated!' gettext-runtime/man/help2man

And this one to bug-help2man.

> 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.

Bruno




reply via email to

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