discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Raw UTF-8?
Date: Wed, 7 Jul 2010 21:18:08 +0200	[thread overview]
Message-ID: <20100707191807.GA18154@britannica.bec.de> (raw)
In-Reply-To: <20100707185815.GA19725@iris.usta.de>

On Wed, Jul 07, 2010 at 08:58:15PM +0200, Ingo Schwarze wrote:
> For the occasional proper name of an author, use transliteration
> to ASCII.  I consider using non-ASCII-output escape sequences in
> there a discourtesy with respect to the author, because then some
> people will not be able to read the name.

Actually, I would consider the reverse the correct behavior. The escape
sequences should provide the transliteration depending on the device
capabilities. 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.

> > I use plain UTF-8 instead of the escapes documented in mandoc_char(7),
> > for a couple reasons.  I'm just wondering, is this practice
> > discouraged in any way?
> 
> Yes.  Eight-Bit characters in roff, man and mdoc source code are syntax
> errors, just like they are in C and in any sane programming language.
> The current implementation passes them through, but it could as well
> throw them away, or abort the parser, subject to change without notice.

You know that C99 just like many other modern language (dialects) allow
full 8bit input?

The primary problem I have with using 8bit input for mandoc(1) (or groff
in general) is that it doesn't have a way to specify the input character
set. If that is addressed, the discussion would move to the more
interesting point of transliteration.

Joreg
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-07-07 19: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 [this message]
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

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=20100707191807.GA18154@britannica.bec.de \
    --to=joerg@britannica.bec.de \
    --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).