Re: bin/49485 (mandoc fails to fail if the word No appears unquoted in a reference)

[Steffen Nurpmeso <sdaoden%yandex.com@localhost>]

The following reply was made to PR bin/49485; it has been noted by GNATS.

From: Steffen Nurpmeso <sdaoden%yandex.com@localhost>
To: gnats-admin%netbsd.org@localhost, gnats-bugs%NetBSD.org@localhost,
 netbsd-bugs%netbsd.org@localhost, wiz%NetBSD.org@localhost
Cc: 
Subject: Re: bin/49485 (mandoc fails to fail if the word No
 appears unquoted in a reference)
Date: Wed, 17 Dec 2014 10:41:58 +0100

 Antti Kantee <pooka%iki.fi@localhost> wrote:
  |On 16/12/14 23:29, wiz%NetBSD.org@localhost wrote:
  |> Synopsis: mandoc fails to fail if the word No appears unquoted \
  |> in a reference
  |>
  |> State-Changed-From-To: open->closed
  |> State-Changed-By: wiz%NetBSD.org@localhost
  |> State-Changed-When: Tue, 16 Dec 2014 23:29:18 +0000
  |> State-Changed-Why:
  |> Thanks for the laugh!
  |> (If you really care about the groff misbehaviour,
  |> we can reopen that, but I don't expect it to be fixed
  |> in NetBSD. It would be wiser to report it to groff upstream
  |> instead.)
  |
  |I'm a bit confused when the same thing is described both as "Not a bug"=
 =20
  |and "misbehaviour".
  |
  |The practical aspect I *am* interested in if it's mandated that manpages=
 =20
  |should be tested to render properly with both mandoc and groff before=20
  |committing them.
 
 It is cryptic and ugly, but it is definetely true that arguments
 of the % series are interpreted as normal macros (macros as of
 1.22.3), and thus need escaping -- simply enclose in quotation
 marks and everything should be fine.
 Thanks to Ingo's and Kristaps' roff.7 it is also clear how to
 write quotation marks: "Rules are ""complicated""".
 
 --steffen