| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, tgl(at)sss(dot)pgh(dot)pa(dot)us, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Doc: typo in config.sgml |
| Date: | 2024-10-15 20:34:16 |
| Message-ID: | f1bc1bcd-a71c-411a-9bfd-8cd6ec2ae007@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-10-15 20:37:05 | Re: Doc: typo in config.sgml |
| Previous Message | Nathan Bossart | 2024-10-15 18:59:57 | Re: Detailed release notes |