From: "Anthony J. Bentley" <anthonyjbentley@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: tech@mdocml.bsd.lv
Subject: Re: ISO-8859-1 character in manpage
Date: Wed, 16 Mar 2011 20:21:16 -0600 [thread overview]
Message-ID: <AANLkTin_6mpAQfYHTTqznim_sS6E3GKZL0roBXnOJi_v@mail.gmail.com> (raw)
In-Reply-To: <20110316235423.GD12736@iris.usta.de>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
To: Ingo Schwarze <schwarze@usta.de>
cc: tech@openbsd.org
Fcc: +outbox
Subject: Re: ISO-8859-1 character in manpage
In-reply-to: <20110316235423.GD12736@iris.usta.de>
References: <4d811192.4800e70a.0914.0777@mx.google.com>
<20110316235423.GD12736@iris.usta.de>
Comments: In-reply-to Ingo Schwarze <schwarze@usta.de>
message dated "Thu, 17 Mar 2011 00:54:23 +0100."
--------
Hi Ingo,
I hope you don't mind me moving this to the Mandoc list, as I think it
makes more sense here.
> ... however the German noun "Koenig" does not contain "o diaeresis",
> but "o umlaut". As this is a common source of confusion even
> among native Germans, here is my commit message to explain the
> situation:
I'm aware that the distinction exists, but as a monolingual American
I was unsure which one to use ;) so I picked the one that matches
their website: http://worldofkonig.com/
> There is no mandoc_char(7) escape for "o umlaut", so we must give
> the digraph as plain text in the mdoc(7) source code.
Is there anything preventing one from being made? E.g., adding
CHAR("oe", "oe", 246)
seems like we could have best rendering in all modes. Of course,
care would have to be taken to pick escapes that don't conflict
(like that one does)...
Also, attached is a patch for a typo in mandoc_char.7.
--
Anthony J. Bentley
[-- Attachment #2: mchar.diff --]
[-- Type: application/octet-stream, Size: 618 bytes --]
Index: mandoc_char.7
===================================================================
RCS file: /cvs/src/share/man/man7/mandoc_char.7,v
retrieving revision 1.8
diff -u mandoc_char.7
--- mandoc_char.7 9 Feb 2011 22:53:18 -0000 1.8
+++ mandoc_char.7 17 Mar 2011 02:15:10 -0000
@@ -350,7 +350,7 @@
.It \e(`a Ta \(`a Ta grave a
.It \e(`e Ta \(`e Ta grave e
.It \e(`i Ta \(`i Ta grave i
-.It \e(`o Ta \(`i Ta grave o
+.It \e(`o Ta \(`o Ta grave o
.It \e(`u Ta \(`u Ta grave u
.It \e(~A Ta \(~A Ta tilde A
.It \e(~N Ta \(~N Ta tilde N
parent reply other threads:[~2011-03-17 2:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20110316235423.GD12736@iris.usta.de>]
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=AANLkTin_6mpAQfYHTTqznim_sS6E3GKZL0roBXnOJi_v@mail.gmail.com \
--to=anthonyjbentley@gmail.com \
--cc=schwarze@usta.de \
--cc=tech@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).