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

From Bruce Momjian
Subject Re: Doc: typo in config.sgml
Date
Msg-id Zw_FwsWATC8Ht5ze@momjian.us
Whole thread Raw
In response to Re: Doc: typo in config.sgml  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Oct 16, 2024 at 09:58:23AM +0200, Peter Eisentraut wrote:
> On 15.10.24 23:51, Bruce Momjian wrote:
> > > I don't see why we need to enforce this at this level.  Whatever downstream
> > > toolchain has requirements about which characters are allowed will complain
> > > if it encounters a character it doesn't like.
> > 
> > Uh, the PDF build does not complain if you pass it a non-Latin-1 UTF8
> > characters.  To test this I added some Russian characters (non-Latin-1)
> > to release.sgml:
> > 
> >     (⟨б⟩, ⟨в⟩, ⟨г⟩, ⟨д⟩, ⟨ж⟩, ⟨з⟩, ⟨к⟩, ⟨л⟩, ⟨м⟩, ⟨н⟩, ⟨п⟩, ⟨р⟩, ⟨с⟩, ⟨т⟩,
> >     ⟨ф⟩, ⟨х⟩, ⟨ц⟩, ⟨ч⟩, ⟨ш⟩, ⟨щ⟩), ten vowels (⟨а⟩, ⟨е⟩, ⟨ё⟩, ⟨и⟩, ⟨о⟩, ⟨у⟩,
> >     ⟨ы⟩, ⟨э⟩, ⟨ю⟩, ⟨я⟩), a semivowel / consonant (⟨й⟩), and two modifier
> >     letters or "signs" (⟨ъ⟩, ⟨ь⟩)
> > 
> > and I ran 'make postgres-US.pdf', and then removed the Russian
> > characters and ran the same command again.  The output, including stderr
> > was identical.  The PDFs, of course, were not, with the Russian
> > characters showing as "####".  Makefile output attached.
> 
> Hmm, mine complains:

My Debian 12 toolchain must be older.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  When a patient asks the doctor, "Am I going to die?", he means 
  "Am I going to die soon?"



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Doc: typo in config.sgml
Next
From: Ashutosh Bapat
Date:
Subject: Misleading error "permission denied for table"