From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: discuss@mdocml.bsd.lv
Subject: Re: Raw UTF-8?
Date: Fri, 9 Jul 2010 22:05:39 +0100 [thread overview]
Message-ID: <20100709210539.GA2465@roadrunner.spoerlein.net> (raw)
In-Reply-To: <20100707211725.GA29241@britannica.bec.de>
On Wed, 07.07.2010 at 23:17:25 +0200, Joerg Sonnenberger wrote:
> On Wed, Jul 07, 2010 at 11:12:12PM +0200, Ingo Schwarze wrote:
> > Hi Joerg,
> >
> > Joerg Sonnenberger wrote on Wed, Jul 07, 2010 at 09:18:08PM +0200:
> >
> > > Consider my name -- I would strongly hope that output devices with
> > > proper Latin1/Latin15/UTF-8 support to use the diacrit, but fall
> > > back to the transliterated version otherwise.
> >
> > You hope in vain. Did you try?
>
> Yes. lp(1) on NetBSD is such an example. It does the right thing with
> groff. Depending on the output device (-Tlatin1 vs -Tascii), it will
> either use the umlaut for \(:o or the oe transliteration.
This also works fine with FreeBSD's groff when rendering to UTF-8 aware
terminals using -Tutf8 (and of course in -Tps and -Thtml mode).
I really hope the sentiment expressed in this thread is in jest, as I
would stop considering mandoc(1) a viable alternative for FreeBSD's man
subsystem if it will never support UTF-8 output (and then render \(:o as
ö like it should).
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-07-09 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 3:13 Anthony J. Bentley
2010-07-07 9:33 ` Kristaps Dzonsons
2010-07-07 14:39 ` Anthony J. Bentley
2010-07-07 20:13 ` Ingo Schwarze
2010-07-07 18:58 ` Ingo Schwarze
2010-07-07 19:18 ` Joerg Sonnenberger
2010-07-07 21:12 ` Ingo Schwarze
2010-07-07 21:17 ` Joerg Sonnenberger
2010-07-09 21:05 ` Ulrich Spörlein [this message]
2010-07-10 18:11 ` J.C. Roberts
2010-07-11 22:17 ` Ingo Schwarze
2010-07-11 22:38 ` Kristaps Dzonsons
2010-07-13 19:23 ` Ulrich Spörlein
2010-07-13 23:25 ` 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=20100709210539.GA2465@roadrunner.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).