bug-groff
[Top][All Lists]
Advanced

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

[bug #51062] [PATCH] fixed doubled words in text


From: G. Branden Robinson
Subject: [bug #51062] [PATCH] fixed doubled words in text
Date: Sat, 22 Jan 2022 06:41:37 -0500 (EST)

Update of bug #51062 (project groff):

                Category:                    None => General                
              Item Group:                    None => Lint                   
             Assigned to:                    None => schwarze               
                 Summary: misc: Remove repeated words in files in "top_srcdir"
=> [PATCH] fixed doubled words in text

    _______________________________________________________

Follow-up Comment #2:

[comment #1 comment #1:]
> changing historical information in the ChangeLog and the NEWS file would be
wrong.

I agree that misrepresenting history would be wrong, but correcting solecisms
like mistyped bug numbers is not a misrepresentation of history--it's a _more
accurate_ representation of history.

Because my own brain hates me, it is only after committing and pushing that I
am likely to notice egregiously bad typos or missing words in my ChangeLog
entries.

Material misrepresentations of fact in such files should either be corrected
in-place or supplemented with "[recte: ]" or similar annotation.

There is the question of how much time has to pass before we consider that
such documents (or what portions of them, in the case of "NEWS") have
stabilized such that the bracketed-annotation approach is more appropriate
than the former.

Anyway, like you, I don't exactly welcome further use of the Savannah system
for this sort of thing.  It would be better for such "linty" patches to go to
the groff@ mailing list, and better still for someone to contribute a style
checker that we can run automatically as part of builds to catch these things
automatically so that a developer can fix them before they're even introduced
into a pushed commit.

What ever became of the Writer's Workbench, eh?

As I recall, a doubled-word finder for plain text that works across line
boundaries is an exercise in the O'Reilly _sed & awk_ book.  It would be a
nice thing for a new developer to contribute!  :)

Anyway, here's the state of play for the doubled words Bjarni reported.  I
intend to fix them, but I'm not reopening this ticket because this sort of
issue simply doesn't rise to that level, IMO.


$ git grep -w "be be"
ChangeLog.119:  with a missing field should be be sorted before all entries
that
contrib/mom/examples/copyright-chapter.mom:chapter, should be be treated as a
DOCTYPE DEFAULT.  The text of
contrib/mom/examples/copyright-default.mom:A copyright page (also called an
edition page) should be be treated

$ git grep -w "the the"
ChangeLog:      BR).  This way the the font escape style names in the
appendment
doc/groff.texi:followed by integers arguments to number the the heading
depths
doc/groff.texi:usually invoked by a localization file, which is turn loaded by
the the
doc/ms.ms:effective as of the the next listed element encountered.
src/roff/groff/groff.1.man:creates font description files for the the HP
LaserJet\~4 family of
tmac/groff_ms.7.man:effective as of the the next listed element encountered.

$ git grep -w "for for"
NEWS:the $r or $R register is set to a value that would be correct for for


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?51062>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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