tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Jason McIntyre <jmc@cava.myzen.co.uk>
Cc: tech@mdocml.bsd.lv
Subject: Re: [PATCH] \*(Px and \*(Ai
Date: Wed, 20 Apr 2011 22:10:35 +0200	[thread overview]
Message-ID: <4DAF3DBB.6080403@bsd.lv> (raw)
In-Reply-To: <20110420125208.GF13691@harkle.bramka>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On 20/04/2011 14:52, Jason McIntyre wrote:
> On Wed, Apr 20, 2011 at 01:46:19PM +0200, Kristaps Dzonsons wrote:
>> Hi,
>>
>> As discussed on tech@openbsd.org,
>>
>> http://comments.gmane.org/gmane.os.openbsd.tech/24663
>>
>> we're missing two symbols defined in tmac.doc.  The enclosed patch
>> includes them (not the documentation bits for mandoc_char.7, which I'd
>> include if this is ok'd).
>>
>> For the record, I don't particularly like these as they discourage using
>> `St' in favour of hand-rolling standards.  I think this should be taken
>> into account when deciding on whether to ok this.
>>
>> So... thoughts?
>>
>> Kristaps
>
> i personally don;t care. i can remove the one instance of Px if that's
> what we prefer. i certainly don;t want Px and Ai all over the manuals.

Enclosed is a patch with the documentation.  I think this is good enough 
to discourage usage.  Oks?

[-- Attachment #2: patch.chars.txt --]
[-- Type: text/plain, Size: 2138 bytes --]

Index: chars.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.c,v
retrieving revision 1.34
diff -u -r1.34 chars.c
--- chars.c	22 Mar 2011 10:13:01 -0000	1.34
+++ chars.c	20 Apr 2011 20:09:29 -0000
@@ -41,7 +41,7 @@
 #define CHARS_BOTH	 (CHARS_CHAR | CHARS_STRING)
 };
 
-#define	LINES_MAX	  351
+#define	LINES_MAX	  353
 
 #define CHAR(in, ch, code) \
 	{ NULL, (in), (ch), (code), CHARS_CHAR },
Index: chars.in
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/chars.in,v
retrieving revision 1.36
diff -u -r1.36 chars.in
--- chars.in	16 Mar 2011 22:49:55 -0000	1.36
+++ chars.in	20 Apr 2011 20:09:29 -0000
@@ -375,6 +375,8 @@
 STRING("right-singlequote",	"\'",		8217)
 STRING("rp",			")",		41)
 STRING("Tm",			"(Tm)",		8482)
+STRING("Px",			"POSIX",	0)
+STRING("Ai",			"ANSI",		0)
 
 /* Lines. */
 CHAR("ba",			"|",		124)
Index: mandoc_char.7
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/mandoc_char.7,v
retrieving revision 1.42
diff -u -r1.42 mandoc_char.7
--- mandoc_char.7	9 Feb 2011 22:53:20 -0000	1.42
+++ mandoc_char.7	20 Apr 2011 20:09:30 -0000
@@ -481,8 +481,12 @@
 .It \e(ts    Ta \(ts        Ta sigma terminal
 .El
 .Sh PREDEFINED STRINGS
-These are not recommended for use, as they differ across
-implementations:
+Predefined strings are inherited from the macro packages of historical
+troff implementations.
+They are
+.Em not recommended
+for use, as they differ across implementations.
+Manuals using these predefined macros are almost certainly not portable.
 .Pp
 .Bl -column -compact -offset indent "Input" "Rendered" "Description"
 .It Em Input Ta Em Rendered Ta Em Description
@@ -512,6 +516,8 @@
 .It \e*(>=   Ta \*(>=       Ta greater-than-equal
 .It \e*(aa   Ta \*(aa       Ta acute
 .It \e*(ga   Ta \*(ga       Ta grave
+.It \e*(Px   Ta \*(Px       Ta POSIX standard name
+.It \e*(Ai   Ta \*(Ai       Ta ANSI standard name
 .El
 .Sh NUMBERED CHARACTERS
 For backward compatibility with existing manuals,

  parent reply	other threads:[~2011-04-20 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 11:46 Kristaps Dzonsons
2011-04-20 12:03 ` Joerg Sonnenberger
2011-04-20 12:24   ` Kristaps Dzonsons
     [not found] ` <20110420125208.GF13691@harkle.bramka>
2011-04-20 20:10   ` Kristaps Dzonsons [this message]
2011-04-20 21:36     ` Ingo Schwarze
2011-04-20 22:22       ` Kristaps Dzonsons

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DAF3DBB.6080403@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=jmc@cava.myzen.co.uk \
    --cc=tech@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).