Re: Doc: typo in config.sgml - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Doc: typo in config.sgml
Date
Msg-id f1bc1bcd-a71c-411a-9bfd-8cd6ec2ae007@eisentraut.org
Whole thread Raw
In response to Re: Doc: typo in config.sgml  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Doc: typo in config.sgml
List pgsql-hackers
On 15.10.24 18:54, Bruce Momjian wrote:
>> I agree with encoding non-Latin1 characters and disallowing non-ASCII
>> characters totally.
>>
>> I found your patch includes fixes in *.svg files, so how about checking
>> also them by check-non-ascii? Also, I think it is better to use perl instead
>> of grep because non-GNU grep doesn't support hex escape sequences. I've attached
>> a updated patch for Makefile. The changes in release.sgml above is not applied
>> yet, though.
> Yes, good idea on using Perl and checking svg files --- I have used your
> Makefile rule.
> 
> Attached is an updated patch.  I realized that the new rules apply to
> all SGML files, not just the release notes, so I have created
> README.non-ASCII and moved the description there.

I don't understand the point of this.  Maybe it's okay to try to detect 
certain "hidden" whitespace characters, like in the case that started 
this thread.  But I don't see the value in prohibiting all non-ASCII 
characters, as is being proposed here.




pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Detailed release notes
Next
From: Bruce Momjian
Date:
Subject: Re: Doc: typo in config.sgml