diff options
| author | G. Branden Robinson <g.branden.robinson@gmail.com> | 2022-01-22 03:50:19 +1100 |
|---|---|---|
| committer | G. Branden Robinson <g.branden.robinson@gmail.com> | 2022-01-25 02:12:49 +1100 |
| commit | 7476112d35aa8478b1ec89c5b435817763b3bf80 (patch) | |
| tree | b10fe15c65d1ec4d24549d7cabfa8ad30c7de718 /ChangeLog.119 | |
| parent | 1307a645ca75217f1f287dffe3f9afb8f505a64d (diff) | |
| download | groff-git-7476112d35aa8478b1ec89c5b435817763b3bf80.tar.gz | |
Fix clarity problems and doubled words.
...and some recent typos.
* ChangeLog: Recast my own entry regarding a post-1.22.4 refactor of the
man(7) font style alternation macros, for greater attempted clarity
and more normative use of terminology. Also be less vague about what
'tty.tmac' does with the 'latin1' and 'cp1047' macro files.
* ChangeLog.119, NEWS (1.06[!]): Fix doubled word typos.
* ChangeLog: Fix recent typo "easile", extraneous phrase "not a
warning", and inappropriate plural.
I recognize that some people feel it is inappropriate to modify older
content of ChangeLog and NEWS files in any way. Permit me to paraphrase
myself in response[1] to Ingo Schwarze.
---
> 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 doubled words 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. The question does not arise in this case.
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! :)
---
[1] https://savannah.gnu.org/bugs/?51062
Diffstat (limited to 'ChangeLog.119')
| -rw-r--r-- | ChangeLog.119 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ChangeLog.119 b/ChangeLog.119 index 71915bc6c..7e0345bb1 100644 --- a/ChangeLog.119 +++ b/ChangeLog.119 @@ -3077,7 +3077,7 @@ Version 1.19.1 released * src/preproc/refer/ref.cpp (reference::compute_sort_key): Always insert SORT_SEP. With certain combinations of sort specifications, refer sorted entries in the wrong order. In particular, entries - with a missing field should be be sorted before all entries that + with a missing field should be sorted before all entries that have that field, before refer looks to the next field. 2003-08-23 Werner LEMBERG <wl@gnu.org> |