Hi Bruce, > On Wed, Oct 16, 2024 at 09:54:57AM -0400, Bruce Momjian wrote: >> On Wed, Oct 16, 2024 at 10:00:15AM +0200, Peter Eisentraut wrote: >> > On 15.10.24 23:51, Bruce Momjian wrote: >> > > On Tue, Oct 15, 2024 at 05:27:49PM -0400, Tom Lane wrote: >> > > > Bruce Momjian <br...@momjian.us> writes: >> > > > > Well, we can only use Latin-1, so the idea is that we will be >> > > > > explicit >> > > > > about specifying Latin-1 only as HTML entities, rather than letting >> > > > > non-Latin-1 creep in as UTF8. We can exclude certain UTF8 or SGML >> > > > > files >> > > > > if desired. >> > > > >> > > > That policy would cause substantial problems with contributor names >> > > > in the release notes. I agree with Peter that we don't need this. >> > > > Catching otherwise-invisible characters seems sufficient. >> > > >> > > Uh, why can't we use HTML entities going forward? Is that harder? >> > >> > I think the question should be the other way around. The entities are a >> > historical workaround for when encoding support and rendering support was >> > poor. Now you can just type in the characters you want as is, which seems >> > nicer. >> >> Yes, that does make sense, and if we fully supported Unicode, we could >> ignore all of this. > > Patch applied to master --- no new UTF8 restrictions.
I thought the conclusion of the discussion was allowing to use LATIN1 (or UTF-8 encoded LATIN1) characters in SGML files without converting them to HTML entities. Your patch seems to do opposite. https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=641a5b7a1447954076728f259342c2f9201bb0b5 Best reagards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp
