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

From Bruce Momjian
Subject Re: Doc: typo in config.sgml
Date
Msg-id Zw1_j_jofafQbNKl@momjian.us
Whole thread Raw
In response to Re: Doc: typo in config.sgml  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Oct 14, 2024 at 03:05:35PM -0400, Bruce Momjian wrote:
> I did some more research and we able to clarify our behavior in
> release.sgml:

I have specified some more details in my patched version:

        We can only use Latin1 characters, not all UTF8 characters,
        because some rendering engines do not support non-Latin1 UTF8
        characters.  Specifically, the HTML rendering engine can display
        all UTF8 characters, but the PDF rendering engine can only display
        Latin1 characters.  In PDF files, non-Latin1 UTF8 characters are
        displayed as "###".

        In the SGML files we encode non-ASCII Latin1 characters as HTML
        entities, e.g., Álvaro.  Oddly, it is possible to safely
        represent Latin1 characters in SGML files as UTF8 for HTML and
        PDF output, but we we currently disallow this via the Makefile
        "check-non-ascii" rule.

-- 
  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: Nathan Bossart
Date:
Subject: Re: Make foreach_ptr macro work in C++ extensions
Next
From: Bruce Momjian
Date:
Subject: Re: Make foreach_ptr macro work in C++ extensions