Excerpts from Bruce Momjian's message of mié oct 12 18:21:19 -0300 2011:
> Alvaro Herrera wrote:
> > Excerpts from Susanne Ebrecht's message of vie may 20 09:04:26 -0400 2011:
> > > On 20.05.2011 13:56, Tom Lane wrote:
> > > >>* Should we allow non-ASCII characters in general source files?
Alvaro Herrera wrote:
> Excerpts from Susanne Ebrecht's message of vie may 20 09:04:26 -0400 2011:
> > On 20.05.2011 13:56, Tom Lane wrote:
> > >>* Should we allow non-ASCII characters in general source files?
> > > Prefer "no" here.
> >
> > I only see two reasons for non-ASCII signs in En
On fre, 2011-05-20 at 08:16 -0400, Alvaro Herrera wrote:
> > > * 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 reco
On fre, 2011-05-20 at 07:56 -0400, Tom Lane wrote:
> > * Should we allow non-ASCII characters in general source
> files?
>
> Prefer "no" here.
Going through this I felt a little bad butchering up people's names that
hadn't bothered anyone before now. So as a compromise, I made
contributor
Excerpts from Susanne Ebrecht's message of vie may 20 09:04:26 -0400 2011:
> On 20.05.2011 13:56, Tom Lane wrote:
> >>* Should we allow non-ASCII characters in general source files?
> > Prefer "no" here.
>
> I only see two reasons for non-ASCII signs in English.
> Either it is a foreign na
On 20.05.2011 13:56, Tom Lane wrote:
* Should we allow non-ASCII characters in general source files?
Prefer "no" here.
I only see two reasons for non-ASCII signs in English.
Either it is a foreign name of e.g. a person
or it is a word that English took from French like in déjà vu.
For t
Excerpts from Tom Lane's message of vie may 20 07:56:58 -0400 2011:
> Peter Eisentraut 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
>
Peter Eisentraut 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 tha
Hello Peter,
On 19.05.2011 23:49, Peter Eisentraut wrote:
So, some questions:
* Should we consistently use entities for encoding non-ASCII
characters in SGML? Or use LATIN1 freely?
* Should we allow/use non-ASCII characters in the release notes?
* What encoding sh
There are a few literal non-ASCII characters in the SGML documentation,
namely in
isn.sgml
release-7.4.sgml
release-8.4.sgml
Also, there are some encoded (&foo;) non-ASCII characters in
release-8.0.sgml
release-8.1.sgml
release-8.2.sgml
unaccent.sgml
These all work fine, because they are all LA
10 matches
Mail list logo