Re: non-ASCII characters in SGML documentation (and elsewhere)

Excerpts from Tom Lane's message of vie may 20 07:56:58 -0400 2011:
> Peter Eisentraut <peter_e(at)gmx(dot)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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support