Re: .LR macro

[Kristaps Dzonsons <kristaps@bsd.lv>]

> This shows up in the Plan 9 manpage mk.1:
>
> .PP
> Seemingly appropriate input like
> .B CFLAGS=-DHZ=60
> is parsed as an erroneous attribute; correct it by inserting
> a space after the first
> .LR = .
> .PP
>
> Output from Plan 9 troff:
>
>         Seemingly appropriate input like CFLAGS=-DHZ=60 is parsed as an
>         erroneous attribute; correct it by inserting a space after the first
>         `='.
>
> Mandoc cuts off the last bit:
>         Seemingly appropriate input like CFLAGS=-DHZ=60 is parsed as an
>         erroneous attribute; correct it by inserting a space after the first
>
> OpenBSD's (ancient) groff displays the same as mandoc.

Anthony,

So the plan9 -man specification,

  http://swtch.com/usr/local/plan9/tmac/tmac.an ,

documents `LR' pretty much as you label it.  This is easily implemented. 
  But the plan9 man(7) page,

  http://swtch.com/plan9port/man/man7/man.html ,

lists `LR' as an alternating monospace-roman (like `BR' and friends) 
font trigger.  This is also easily implemented.

Unfortunately, this leads us down the twisty path of being compatible 
with one of the other.

Anthony, seeing as how you reported this, can you track down an official 
answer from the Plan9 folks?  Maybe you can pull from them an up-to-date 
man(7) page so we can see all the differences between groff's -man and 
plan9's?

Working with "the other troffs" isn't a priority for mandoc, but I'm 
happy to at least have COMPATIBILITY notes regarding the others so that 
we can later work in the biggest offenders.

Thanks!

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv