Content-Type: text/plain; charset=UTF-8
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: non-ASCII characters in SGML documentation (and elsewhere)
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
In-reply-to: <8242.1305892618@sss.pgh.pa.us>
References: <1305841740.3952.32.camel@vanquo.pezone.net>
	<8242.1305892618@sss.pgh.pa.us>
Date: Fri, 20 May 2011 08:16:19 -0400
Message-Id: <1305893700-sup-7077@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Tom Lane's message of vie may 20 07:56:58 -0400 2011:
> Peter Eisentraut <peter_e@gmx.net> writes:
> >       * Should we consistently use entities for encoding non-ASCII
> >         characters in SGML?  Or use LATIN1 freely?
> 
> I think we previously discussed this and agreed that all non-ASCII in
> the SGML docs should be written as entities.  The existence of
> violations of that rule is just, well, a violation that ought to be
> fixed.

+1

> >       * Should we allow/use non-ASCII characters in the release notes?
> >       * What encoding should the HISTORY file have?
> 
> Ideally "sure, if entity-ified", but I don't know what to do about
> HISTORY.

Can we recode that to plain ascii?  I think iconv has a //TRANSLIT flag
or something like that.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support