[bug #66040] [troff] no longer warns about unrecognized .hcode input

[Dave]

Follow-up Comment #13, bug #66040 (group groff):

[comment #6 comment #6:]
> The part I'm griefed about is "(not a special character escape sequence)".
> 
> A "hyphenation code" (an argument to the `hcode` request):
> 
> 1.  is always permitted as the destination (first of a pair), as in
> 

> .hcode \[S ,]s


> 
> from "tmac/ps.tmac".

Ah, but the documentation _does_ say that; you just have to look at the
context:

-- Request: .hcode c1 code1 [c2 code2] ...
    Set the hyphenation code of character C1 to CODE1, that of C2 to
    CODE2, and so on.  A hyphenation code must be an ordinary character
    (not a special character escape sequence)

Here, the odd-numbered arguments are "characters" and the even-numbered ones
"codes."  It may not be written as _clearly_ as it could be, but it is
accurate to how the arguments are defined: the "not a special character"
parenthetical applies only to codes, the even-numbered arguments.

I do note that one thing missing from the description is that the spaces
between arguments are optional, which the ps.tmac example demonstrates.


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature