From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] utf8 locals, man pages and copy-n-paste
Date: 06 Dec 2002 16:38:24 -0500 [thread overview]
Message-ID: <m3el8u6d67.fsf@lugabout.jhcloos.org> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 1638 bytes --]
From: Mike FABIAN <mfabian@suse.de>
Subject: Re: filename and normalization
Date: Thu, 05 Dec 2002 15:46:49 +0100
Message-ID: <s3tptsg8qw6.fsf@magellan.suse.de>
Werner LEMBERG <wl@gnu.org> [wrote]:
> A better temporary solution is to add the following to man.local:
>
> .if '\*[.T]'utf8' \
> . char \- \N'45'
>
> At least SuSE and Debian are already doing this.
I extended it a little bit shortly after the release of SuSE Linux 8.1:
.if '\*[.T]'utf8' \{\
. char \- \N'45'
. char - \N'45'
.\}
because I found quite a few man pages which used just "-o" to write
command line options of programs not "\-o", for example the man page
of "less" does this. Without that hack, groff translates "-" into
yet another variant of "-": U+2010 (HYPHEN).
Recently I discovered that
opendir(DIR, $some_dir) || die "can't opendir $some_dir: $!";
written like that in the nroff source of the perlfunc(1) man page also
gets rendered strangely for the terminal by groff.
The apostrophe in can't becomes U+2019 (RIGHT SINGLE QUOTATION MARK).
Shouldn't that remain U+0027 (APOSTROPHE)?
And even worse, the U+007C (VERTICAL LINE) in || becomes
U+2502 (BOX DRAWINGS LIGHT VERTICAL).
I think that should be typeset verbatim, because it is intended as
verbatim quote of program text.
--
Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian
[...]
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
[-- Attachment #2: Type: text/plain, Size: 37 bytes --]
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2002-12-06 21:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3el8u6d67.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=gentoo-dev@gentoo.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