projects / postgresql.git / commitdiff
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 24987c6)
doc: update guidelines on non-ASCII characters in docs
authorBruce Momjian <bruce@momjian.us>
Sat, 3 May 2025 18:45:26 +0000 (14:45 -0400)
committerBruce Momjian <bruce@momjian.us>
Sat, 3 May 2025 18:45:26 +0000 (14:45 -0400)
doc/src/sgml/README.non-ASCII patch | blob | blame | history

diff --git a/doc/src/sgml/README.non-ASCII b/doc/src/sgml/README.non-ASCII
index 9c21e02e8f2205941debe9aef7e0f95dbbc9d36c..e9065a33ad6f224cc74d93a28d3a0f9e9432d57d 100644 (file)
--- a/doc/src/sgml/README.non-ASCII
+++ b/doc/src/sgml/README.non-ASCII
@@ -22,13 +22,14 @@ others only support Latin-1 characters.  Specifically, the PDF rendering
 engine can only display Latin-1 characters;  non-Latin-1 Unicode
 characters are displayed as "###".
 
-Therefore, in the SGML files, we only use Latin-1 characters.  We
-typically encode these characters as HTML entities, e.g., &Aacute;lvaro.
-It is also possible to safely represent Latin-1 characters in UTF8
-encoding for all output formats.
+Therefore, in the SGML files, we can only use Latin-1 characters.  We
+can use UTF8 representations of Latin-1 characters, or HTML entities of
+Latin-1 characters, e.g., &Aacute;lvaro.
 
 Do not use UTF numeric character escapes (&#nnn;).
 
+When building the PDF docs, problem characters will appear as warnings.
+
 HTML entities
         official:      http://www.w3.org/TR/html4/sgml/entities.html
         one page:      http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
This is the main PostgreSQL git repository.