From: "Anthony J. Bentley" <anthony@cathet.us>
To: discuss@mdocml.bsd.lv
Subject: Re: FWD: man.conf mandoc -Tlocale
Date: Mon, 17 Feb 2014 04:55:12 -0700 [thread overview]
Message-ID: <CAFRrxym-ODuoW6mSFv+Qhc97Wr6ob=dXqZ-+nuqiczYOj7jx7w@mail.gmail.com> (raw)
In-Reply-To: <20140217114136.GE93008@acme.spoerlein.net>
On Mon, Feb 17, 2014 at 4:41 AM, Ulrich Spörlein <uqs@spoerlein.net> wrote:
> On Sun, 2014-02-16 at 21:56:55 +0100, Ingo Schwarze wrote:
>> So, we have these mappings:
>>
>> input output
>> ----- ASCII UTF-8
>> ----- -----
>>
>> - - -
>> \- - -
>> \(hy - U+2010
>> \(en - U+2013
>> \(em -- U+2014
>>
>> See also these lines in chars.in:
>>
>> CHAR("-", "-", 45)
>> CHAR("hy", "-", 8208)
>> CHAR("en", "-", 8211)
>> CHAR("em", "--", 8212)
>>
>> So, unless people put \(hy, \(en, or \(em into their example code,
>> i would expect copy and paste to work just fine even in UTF-8 mode.
>
> I don't think hyphens will be the problem, but quotes, where people
> might have used .Dq when they actually want the literal ASCII quotes ""
> as they are to be used in some shell or other code.
Thankfully, in my experience (using -Tlocale for well over a year)
this does not happen often--indeed, I haven't seen it at all. Any such
cases would be a bug in the manpage, but this is not a bug that would
be common enough to make -Tlocale an impractical default.
On the other hand, groff's hyphen substitution is extremely irritating
when it's turned on, since you'd be hard pressed to find a manual
*not* affected by it.
--
Anthony J. Bentley
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-02-17 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20140214-152923-+048.24-1@spamfilter.osbf.lua>
2014-02-14 13:06 ` Ingo Schwarze
2014-02-15 8:43 ` Thomas Klausner
2014-02-15 9:42 ` Ingo Schwarze
2014-02-16 20:56 ` Ingo Schwarze
2014-02-17 11:41 ` Ulrich Spörlein
2014-02-17 11:55 ` Anthony J. Bentley [this message]
2014-03-13 9:16 ` Thomas Klausner
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='CAFRrxym-ODuoW6mSFv+Qhc97Wr6ob=dXqZ-+nuqiczYOj7jx7w@mail.gmail.com' \
--to=anthony@cathet.us \
--cc=discuss@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).