From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: Raw UTF-8?
Date: Wed, 14 Jul 2010 01:25:25 +0200 [thread overview]
Message-ID: <4C3CF5E5.7060700@bsd.lv> (raw)
In-Reply-To: <20100713192341.GB25163@roadrunner.spoerlein.net>
>>> 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).
>> I think there's a little confusion here. I see Ingo just wrote and
>> answered most questions. Well, no point in wasting a response...
>>
>> The state of affairs follows:
>>
>> - mandoc/groff accept and understand ASCII input
>> - mandoc/groff [sometimes] accept but DO NOT understand non-ASCII input
>>
>> That UTF-8 input renders on your screen is coincidence: you happen to
>> have a UTF-8 terminal and groff hasn't puked on the characters. You
>> implicitly assume your readers' mediums have the same capabilities.
>>
>> Now for the \[foo] syntax. First, it exists. Second, it covers most
>> European characters. Is it general? No. Why let it stay? Because it
>> lets \(:u be both "u" (my terminal) and ü (e.g. www output). If you
>> don't use the \[foo] escapes, you're screwing readers. Yes, we're
>> screwing non-western-European manual writers ("me") already, but this is
>> not a problem we need to solve right now.
>
> I completely agree here, there's nothing fancy we could or should do
> regarding input.
Yes. Note that the problem space lies entirely within -Tps, which for
now has hard-coded glyph widths.
>
>> Now for output and The Good Stuff.
>>
>> -Tutf8 is not hard. I think I can manage this in coming releases
>> without any negative effects. In fact, it will cut the binary size, as
>> I'd key special chars as integers and rewrite them on the fly into
>> UTF-8, Latin-1, or whatever, for all outputs.
>
> Sounds great, do you also plan on adding "special chars" support to -Tps
> (mostly for latin1 accents and umlauts)?
Yes. I want to roll it into the next release along with the chars.in
upgrade.
Thanks,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-07-13 23:24 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
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 [this message]
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=4C3CF5E5.7060700@bsd.lv \
--to=kristaps@bsd.lv \
--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).