Hi,
G. Branden Robinson wrote on Sat, Apr 29, 2017 at 07:26:15AM -0400:
> At 2017-04-27T17:37:15+0200, Ingo Schwarze wrote:
>> .TP
>> \fB\-scale\fP \fIxfac\fP[,\fIyfac\fP]
>> is not bad markup, but decent quality man(7) code
> Well, thanks. This is what it looked like before I got to it:
> .TP
Dave Kemper writes:
> On 4/29/17, Anthony J. Bentley wrote:
> > Unicode made the decision a long time ago to consider U+2019 as both
> > right single quotation mark and apostrophe; see the Apostrophes section
> > of Unicode 9.0, chapter 6.
>
> Yes, and that remains a bad decision, because it conf
Hi,
Dave Kemper wrote on Sat, Apr 29, 2017 at 02:47:50PM -0500:
> On 4/29/17, G. Branden Robinson wrote:
>> At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:
>>> So yes, documentation kind of recommends "Don\(aqt listen".
>> I don't interpret it that way.
> Nor I.
I stand corrected. As was p
On 4/29/17, G. Branden Robinson wrote:
> At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:
>> So yes, documentation kind of recommends "Don\(aqt listen".
>
> I don't interpret it that way.
Nor I.
The quoted mandoc_char passage cites things like "source code samples"
as places where one should us
Hi Ralph,
Ralph Corderoy wrote on Sat, Apr 29, 2017 at 03:47:53PM +0100:
> Ingo Schwarze wrote:
>> .Fl S Ar var Ns Op Pf = Ar value
> This has reminded me of one reason I didn't get on with mdoc.
> Only the `Fl' is obviously mdoc's, due to the `.' invocation.
> The rest are a mix of command and
Hi Ingo,
Ingo Schwarze writes:
>Accents
> In output modes supporting such special output characters, for
> example -T pdf, some roff(7) formatters convert the following
> ASCII input characters to the following Unicode special output
> characters:
>
> ` U+2018
At 2017-04-29T15:40:06+0200, Ingo Schwarze wrote:
> $ man groff_char
> [...]
> REFERENCE
> [...]
>7-bit Character Codes 32-126
> [...]
>' the ISO latin1 `Apostrophe' (code 39) prints as ', a right
> single quotation mark; the original character can be obtained
> with `\(aq'.
Hi Branden,
> > The troff system was designed to be typed at a keyboard. The
> > dot-on-the-left rule might be ugly, and the requests/macros terse,
> > but the benefit to the user is relatively few keystrokes above those
> > needed for the text.
...
> Nothing has come close to saving me more keys
Hi Ingo,
> things are actually much simpler even for describing such unusually
> complicated syntax:
>
> .Oo : Ns Fl c Ar cc-addr : Oc
> .Eo [: Fl c Ar cc-addr Ec :]
>
> .Fl S Ar var Ns Op = Ns Ar value
> .Fl S Ar var Ns Op Pf = Ar value
This has reminded me of one reason I didn't get on with mdo
Hi,
G. Branden Robinson wrote on Sat, Apr 29, 2017 at 08:32:57AM -0400:
> I'm noticing that in some of groff's own man pages, the plain-old
> long-suffering apostrophe is explcitly avoided in favor of \(aq.
>
> And I don't mean in any fancy technical jargon, I mean in plain
> language like:
>
>
I'm noticing that in some of groff's own man pages, the plain-old
long-suffering apostrophe is explcitly avoided in favor of \(aq.
And I don't mean in any fancy technical jargon, I mean in plain language
like:
Don\(aqt listen to Trump\(aqs advisors.
That sure is ugly, and unkind to spell-checker
Thanks to a perfectly pleasant offline conversation with Ingo, I no
longer fear that he is hell-bent on man's destruction. ;-)
But I figured I'd better address a few remaining points, and
particularly to offer some thanks where it's deserved.
At 2017-04-27T17:37:15+0200, Ingo Schwarze wrote:
> G
Any advice on how I can improve this? (I'll take "no, don't even try to
do this" as read, from those who hate man(7). ;-) )
This is a private macro, not something I'm proposing as an extension to
any macro package.
.\" The bold italic font is not accessible via the man macro package.
.de BOLD-IT
13 matches
Mail list logo
