database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

docs: ulink all references to RFC's

Browse Source 
Make sure that the first mentions of RFC's are ulinked to their ietf.org
entry, and subsequent ones are marked as acronyms. This makes references
to RFC's consistent across the documentation.

Author: Daniel Gustafsson
Discussion: https://www.postgresql.org/message-id/2C697878-4D01-4F06-8312-2FEDE931E973%40yesql.se
This commit is contained in:
Heikki Linnakangas
2020-12-01 14:36:30 +02:00
parent 0a4db67b5e
commit 415dc20096
12 changed files with 39 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/json.sgml
View File

@ -61,7 +61,7 @@
</para>
<para>
RFC 7159 specifies that JSON strings should be encoded in UTF8.
<acronym>RFC</acronym> 7159 specifies that JSON strings should be encoded in UTF8.
It is therefore not possible for the JSON
types to conform rigidly to the JSON specification unless the database
encoding is UTF8. Attempts to directly include characters that
@ -71,7 +71,7 @@
</para>
<para>
RFC 7159 permits JSON strings to contain Unicode escape sequences
<acronym>RFC</acronym> 7159 permits JSON strings to contain Unicode escape sequences
denoted by <literal>\u<replaceable>XXXX</replaceable></literal>. In the input
function for the <type>json</type> type, Unicode escapes are allowed
regardless of the database encoding, and are checked only for syntactic