From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Hiroki Sato <hrs@allbsd.org>
Cc: discuss@mdocml.bsd.lv
Subject: Re: mandoc and UTF-8 support.
Date: Sun, 15 May 2011 11:31:25 -0400 [thread overview]
Message-ID: <4DCFF1CD.7000402@bsd.lv> (raw)
In-Reply-To: <20110515.194157.759326979137963596.hrs@ec.ss.titech.ac.jp>
> kr> Hiroki (note CC'd to the mdocml mailing list),
> kr>
> kr> This regards today's conversation about mdocml and Japanese characters
> kr> at the FreeBSD summit.
> kr>
> kr> Enclosed is a screenshot of a locally-modified mandoc producing
> kr> on-terminal UTF-8 glyphs for kanji (I have NO IDEA what these
> kr> characters mean, I just picked them from the Unicode reference). I
> kr> hacked this in as a demonstrandum that it's possible to have UTF-8
> kr> output without much effort.
>
> Great, it seems to work.
>
> kr> I used the groff \U'xxxx' input escape sequence to specify Unicode
> kr> input. Unfortunately, this doesn't seem to be officially supported by
> kr> groff.
> kr>
> kr> http://lists.gnu.org/archive/html/groff/2000-04/msg00036.html
> kr>
> kr> My question is this: do you know of the most reliable to feed groff
> kr> Unicode codepoints? I'm not sure when a -Tutf8 will exist for mandoc,
> kr> but the screenshot demonstrates that it's in principle possible.
>
> I tried UTF-8 characters directly only but it was a long time ago so
> I don't remember the details. I will check the stock version of
> groff again and give mandoc a try, then contact a manual page
> maintainer in FreeBSD project about how he feels migration from groff
> to mandoc, and get back to you.
>
> And, what do I do to subscribe this mailing-list? I could not find
> information on in at bsd.lv page.
Hiroki,
Send mail to discuss+subscribe@mdocml.bsd.lv to subscribe.
Regarding groff, their underlying Unicode input method is detailed here:
http://mdocml.bsd.lv/archives/tech/0368.html
groff also has support for arbitrary encodings by piping the output of
preconv (a groff preprocessor translating multi-byte characters, like
UTF8, into the groff escapes):
http://manpages.ubuntu.com/manpages/maverick/man1/preconv.1.html
This part I'll consider later.
I'd like to have wide-character support by the next version of mandoc;
however, I'll post versions here for testing when they're available.
Thanks again,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-05-15 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 20:42 Kristaps Dzonsons
[not found] ` <20110515.194157.759326979137963596.hrs@ec.ss.titech.ac.jp>
2011-05-15 15:31 ` 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=4DCFF1CD.7000402@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.bsd.lv \
--cc=hrs@allbsd.org \
/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).