public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: non-ASCII characters in SGML documentation (and elsewhere)
Date: Fri, 20 May 2011 07:56:58 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Peter Eisentraut <[email protected]> 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.
> * 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.
> * Should we allow non-ASCII characters in general source files?
Prefer "no" here.
regards, tom lane
view thread (10+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: non-ASCII characters in SGML documentation (and elsewhere)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox