aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2025-05-03 14:45:26 -0400
committerBruce Momjian <bruce@momjian.us>2025-05-03 14:45:26 -0400
commitfb21ed6c38da719149443e78048790c0347e2c9b (patch)
tree25a8165a7af161598fad96f848307c950eb36342
parent24987c6f0687576da97b593c6dd5740ccdd23277 (diff)
downloadpostgresql-fb21ed6c38da719149443e78048790c0347e2c9b.tar.gz
postgresql-fb21ed6c38da719149443e78048790c0347e2c9b.zip
doc: update guidelines on non-ASCII characters in docs
-rw-r--r--doc/src/sgml/README.non-ASCII9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/src/sgml/README.non-ASCII b/doc/src/sgml/README.non-ASCII
index 9c21e02e8f2..e9065a33ad6 100644
--- 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