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

Doc: get rid of <foreignphrase> tags.

Browse Source 
We italicized some, but not all, instances of "per se", "pro forma", and
"ad hoc". These phrases are widespread in formal registers of English,
so it"s debatable whether they even qualify as foreign. We could instead
try to be more consistent in the use of <foreignphrase>, but that"s
difficult to enforce, so let"s just remove the tags for those words.

The one case that seems to deserve the tag is "voilà". Instead of keeping
just one instance of the tag, change that to a more standard phrase.

John Naylor

Discussion: https://postgr.es/m/CAFBsxsHtWs_NsccAVgQ=tTUKkXHpHdkjZXtp_Cd9dGWyBDxfbQ@mail.gmail.com
This commit is contained in:
Tom Lane
2021-03-10 12:38:43 -05:00
parent 227338b00d
commit b12436340a
4 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2763,8 +2763,8 @@ CREATE SCHEMA myschema;
<synopsis> <synopsis>
<replaceable>database</replaceable><literal>.</literal><replaceable>schema</replaceable><literal>.</literal><replaceable>table</replaceable> <replaceable>database</replaceable><literal>.</literal><replaceable>schema</replaceable><literal>.</literal><replaceable>table</replaceable>
</synopsis> </synopsis>
can be used too, but at present this is just for <foreignphrase>pro can be used too, but at present this is just for pro forma
forma</foreignphrase> compliance with the SQL standard. If you write a database name, compliance with the SQL standard. If you write a database name,
it must be the same as the database you are connected to. it must be the same as the database you are connected to.
</para> </para>

2
doc/src/sgml/ref/create_role.sgml
View File

@ -358,7 +358,7 @@ in sync when changing the above synopsis!
<para> <para>
The <literal>VALID UNTIL</literal> clause defines an expiration time for a The <literal>VALID UNTIL</literal> clause defines an expiration time for a
password only, not for the role <foreignphrase>per se</foreignphrase>. In password only, not for the role per se. In
particular, the expiration time is not enforced when logging in using particular, the expiration time is not enforced when logging in using
a non-password-based authentication method. a non-password-based authentication method.
</para> </para>

2
doc/src/sgml/rules.sgml
View File

@ -1946,7 +1946,7 @@ DELETE FROM shoelace WHERE EXISTS
WHERE sl_name = shoelace.sl_name); WHERE sl_name = shoelace.sl_name);
</programlisting> </programlisting>
<foreignphrase>Voil&agrave;</foreignphrase>: The results are:
<programlisting> <programlisting>
SELECT * FROM shoelace; SELECT * FROM shoelace;

2
doc/src/sgml/typeconv.sgml
View File

@ -40,7 +40,7 @@ has an associated data type which determines its behavior and allowed usage.
<productname>PostgreSQL</productname> has an extensible type system that is <productname>PostgreSQL</productname> has an extensible type system that is
more general and flexible than other <acronym>SQL</acronym> implementations. more general and flexible than other <acronym>SQL</acronym> implementations.
Hence, most type conversion behavior in <productname>PostgreSQL</productname> Hence, most type conversion behavior in <productname>PostgreSQL</productname>
is governed by general rules rather than by <foreignphrase>ad hoc</foreignphrase> is governed by general rules rather than by ad hoc
heuristics. This allows the use of mixed-type expressions even with heuristics. This allows the use of mixed-type expressions even with
user-defined types. user-defined types.
</para> </para>