From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Accomodate for \f(Cx formatting.
Date: Sun, 13 Nov 2011 01:14:34 +0100 [thread overview]
Message-ID: <4EBF0BEA.3030608@bsd.lv> (raw)
In-Reply-To: <20111112224058.GA16229@iris.usta.de>
On 12/11/2011 23:40, Ingo Schwarze wrote:
> Hi,
>
> the meaning of the "C*" font family is not "constant width" in general.
> Even in groff, its meaning is output-device dependent, and only a few
> devices support it: mainly -Tps and -Thtml, but not -Tascii or -Tdvi.
>
> Even in groff -Tps, its meaning isn't "constant width", but rather
> "Adobe Courier". There are many other -Tps families we do not
> support (A, BM, H, HN, N, P, T). Even when aiming for groff -Tps C*
> support only, this patch is incomplete, \f[CBI] is missing.
>
> Hence, i mildly disagree with this patch - but merged it anyway
> because it doesn't do that much harm. I do think, however, that
> any font escape except \fR \fI \fB \f1 \f2 \f3 \fP merits a warning
> that it's utterly non-portable both regarding different roff
> implementations and even regarding different output devices.
>
> I don't consider this an urgent matter at all, but thought
> i'd bring this up in case anybody has more thoughts on the
> subject...
Ingo,
Hm, you have a good point. Maybe mention should be omitted from the
manual to avoid encouraging this bad behaviour?
And while yes, in principle warning about bad formatting tokens is a
good idea -- there just so many of them! We should maybe warn when
people are doing the correct thing. ;)
Thoughts? (About the manual entry, of course...)
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-11-13 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201111061443.pA6EhE7Q011223@krisdoz.my.domain>
2011-11-12 22:40 ` Ingo Schwarze
2011-11-13 0:14 ` Kristaps Dzonsons [this message]
2011-11-14 16:11 ` Ingo Schwarze
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=4EBF0BEA.3030608@bsd.lv \
--to=kristaps@bsd.lv \
--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).