gbranden pushed a commit to branch master
in repository groff.
commit 5895ab976ddc27f41461f852774af1ad16ab5fb4
Author: G. Branden Robinson <[email protected]>
AuthorDate: Tue Jun 30 23:26:22 2020 +1000
ChangeLog: Remove excess precision from claim.
...about Ossanna's troff.
See commit bbdf8b1349698076c59a59b6ee1f6509631af02d.
---
ChangeLog | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index b1516a9..93e1f96 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -612,10 +612,10 @@
To anticipate objections: Why not throw only a warning? Because
there isn't a warning category for supported but ambiguous
- syntax (this behavior of AT&T troff dates to 1976 but apparently
- was not documented until 1992). Why not throw the error outside
- of compatibility mode too? Because outside of compatibility
- mode we (now) have an unambiguous parse.
+ syntax (this behavior of AT&T troff dates back to the mid-1970s
+ but apparently was not documented until 1992). Why not throw
+ the error outside of compatibility mode too? Because outside of
+ compatibility mode we (now) have an unambiguous parse.
Background: The Graphic Systems C/A/T phototypesetter (the
original device target for AT&T troff) only supported a few
_______________________________________________
Groff-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/groff-commit
