From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: FWD: man.conf mandoc -Tlocale
Date: Fri, 14 Feb 2014 14:06:47 +0100 [thread overview]
Message-ID: <20140214130647.GF20867@iris.usta.de> (raw)
Hi,
in OpenBSD, we are discussing to move to mandoc(1) default
from -Tascii to -Tlocale, see the mail on <tech@openbsd.org>
below.
How do you feel about that idea, in particular regarding other
operating systems like DragonFly, NetBSD, FreeBSD and from the
perspective of the pkgsrc packaging system?
Yours,
Ingo
----- Forwarded message from Ingo Schwarze <schwarze@usta.de> -----
From: Ingo Schwarze <schwarze@usta.de>
Sender: owner-tech@openbsd.org
Date: Fri, 14 Feb 2014 14:02:26 +0100
To: Ted Unangst <tedu@tedunangst.com>
Cc: tech@openbsd.org
Subject: Re: man.conf mandoc -Tlocale
Hi Ted,
Ted Unangst wrote on Thu, Feb 13, 2014 at 09:22:04PM -0500:
> About 20 years after the invention of utf-8, I've decided to see what
> all the fuss is about and experiment with uxterm and whatnot.
> Naturally, this means I want to see sweet fancy quotes in all my man
> pages instead of the lame ``fake'' quotes. In order to convince mandoc
> to give me what I want, however, requires a command line option. But
> what about all those old school ascii only terminals I still sometimes
> use?
>
> mandoc fortunately has an option -Tlocale, which will pick between
> ascii and utf8 based on environment. Perfect! Let's use it.
>
> Tested to work as expected in uxterm. Tested to change nothing in a
> regular xterm by default (no LC_CTYPE set).
Even though i don't use it, i'm not opposed to your patch.
I think it makes sense.
I even considered switching the mandoc(1) default from -Tascii to
-Tlocale in general, but forgot about it again. If you like the
idea, that would be something to do after unlock; it might require
explicitly giving the -Tascii option in some build system and similar
contexts.
I think -Tlocale might be a saner default than -Tascii nowadays.
People who don't want UTF-8 shouldn't have it in their LC_CTYPE,
and it's hard to see why people who do want it and have it in their
LC_CTYPE should be forced to give -Tlocale or something similar
to each and every utility they call.
What do you think?
Ingo
> Index: man.conf
> ===================================================================
> RCS file: /cvs/src/etc/man.conf,v
> retrieving revision 1.18
> diff -u -p -r1.18 man.conf
> --- man.conf 13 Jul 2013 20:21:52 -0000 1.18
> +++ man.conf 14 Feb 2014 02:14:29 -0000
> @@ -16,15 +16,15 @@ _subdir {cat,man}1 {cat,man}8 {cat,man}
> _suffix .0
> _build .0.Z /usr/bin/zcat %s
> _build .0.gz /usr/bin/gzcat %s
> -_build .[1-9n] /usr/bin/mandoc %s
> -_build .[1-9n].Z /usr/bin/zcat %s | /usr/bin/mandoc
> -_build .[1-9n].gz /usr/bin/gzcat %s | /usr/bin/mandoc
> -_build .[1-9][a-z] /usr/bin/mandoc %s
> -_build .[1-9][a-z].Z /usr/bin/zcat %s | /usr/bin/mandoc
> -_build .[1-9][a-z].gz /usr/bin/gzcat %s | /usr/bin/mandoc
> -_build .tbl /usr/bin/mandoc %s
> -_build .tbl.Z /usr/bin/zcat %s | /usr/bin/mandoc
> -_build .tbl.gz /usr/bin/gzcat %s | /usr/bin/mandoc
> +_build .[1-9n] /usr/bin/mandoc -Tlocale %s
> +_build .[1-9n].Z /usr/bin/zcat %s | /usr/bin/mandoc -Tlocale
> +_build .[1-9n].gz /usr/bin/gzcat %s | /usr/bin/mandoc -Tlocale
> +_build .[1-9][a-z] /usr/bin/mandoc -Tlocale %s
> +_build .[1-9][a-z].Z /usr/bin/zcat %s | /usr/bin/mandoc -Tlocale
> +_build .[1-9][a-z].gz /usr/bin/gzcat %s | /usr/bin/mandoc -Tlocale
> +_build .tbl /usr/bin/mandoc -Tlocale %s
> +_build .tbl.Z /usr/bin/zcat %s | /usr/bin/mandoc -Tlocale
> +_build .tbl.gz /usr/bin/gzcat %s | /usr/bin/mandoc -Tlocale
>
> # Sections and their directories.
> # All paths ending in '/' are the equivalent of entries specifying that
>
----- End forwarded message -----
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2014-02-14 13:06 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 [this message]
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
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=20140214130647.GF20867@iris.usta.de \
--to=schwarze@usta.de \
--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).