From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: Full mandoc locale support committed.
Date: Fri, 20 May 2011 09:26:15 +0200 [thread overview]
Message-ID: <20110520072615.GQ31223@acme.spoerlein.net> (raw)
In-Reply-To: <4DD59E71.7030607@bsd.lv>
On Fri, 20.05.2011 at 00:49:21 +0200, Kristaps Dzonsons wrote:
> On 19/05/2011 22:28, Ulrich Spörlein wrote:
> > On Wed, 18.05.2011 at 01:07:28 +0200, Kristaps Dzonsons wrote:
> >> Hi,
> >>
> >> With this last commit, initial [full] locale support has been fitted
> >> into mandoc! Attached is eye-candy: a manual full of random Unicode
> >> input (\[uNNNN]) first with -Tascii, then with -Tlocale.
> >>
> >> From the manual:
> >>
> >> Locale Output
> >> Locale-depending output encoding is triggered with -Tlocale.
> >> This option is not available on all systems: systems without
> >> locale support, or those whose internal representation is not
> >> natively UCS-4, will fall back to -Tascii. See ASCII Output
> >> for font style specification and available command-line
> >> arguments.
> >
> > Cool stuff! However, and this might be due to a case of "we've always
> > been doing it that way"-thinking: I think this automagic is in the wrong
> > place.
> >
> > There might be cases, where I really want ASCII output no matter what my
> > locale is (this is covered by -Tascii right now), and there might be
> > cases where I want UTF-8 output, no matter what the current locale is.
> > Perhaps because I write the output to disk or to some other
> > postprocessor.
> >
> > What I'm arguing is that we need to have a -Tutf8 mode and that perhaps
> > *not* specifying *any* -T value turns on the automagic? This would make
> > more sense from a users standpoint, IMHO.
>
> Ulrich,
>
> I agree. And we also want -Tutf8 for groff compatibility.
>
> In short, I'll have -Tutf8 done for the next release. It's simply a
> matter of indicating *which* locale when using setlocale().
>
> (By the way, does FreeBSD have the STDC_ISO_10646, whether explicitly or
> implicitly?)
It certainly isn't defined anywhere, and it also doesn't seem to be
implemented, as a short test using \[uc3bc] didn't produce ü but a
missing-glyph symbol. :(
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-05-20 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 23:07 Kristaps Dzonsons
2011-05-18 6:21 ` Yuri Pankov
2011-05-18 9:53 ` Kristaps Dzonsons
2011-05-19 20:28 ` Ulrich Spörlein
2011-05-19 22:49 ` Kristaps Dzonsons
2011-05-20 7:26 ` Ulrich Spörlein [this message]
2011-05-20 7:59 ` Yuri Pankov
2011-05-20 15:52 ` 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=20110520072615.GQ31223@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--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).