Skip to content

Commit bc49968

Browse files
peterepetere
committed
Add more appropriate markup.
1 parent 7233aae commit bc49968

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

77 files changed

+1489
-1355
lines changed

‎doc/src/sgml/array.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.21 2002/08/05 19:43:30 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.22 2002/09/21 18:32:52 petere Exp $ -->
22

33
<sect1 id="arrays">
44
<title>Arrays</title>
@@ -251,8 +251,8 @@ SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
251251
<note>
252252
<para>
253253
A limitation of the present array implementation is that individual
254-
elements of an array cannot be SQL NULLs. The entire array can be set
255-
to NULL, but you can't have an array with some elements NULL and some
254+
elements of an array cannot be SQL null values. The entire array can be set
255+
to null, but you can't have an array with some elements null and some
256256
not. Fixing this is on the to-do list.
257257
</para>
258258
</note>
@@ -267,7 +267,7 @@ SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
267267
around the array value plus delimiter characters between adjacent items.
268268
The delimiter character is usually a comma (<literal>,</>) but can be
269269
something else: it is determined by the <literal>typdelim</> setting
270-
for the array's element type. (Among the standard datatypes provided
270+
for the array's element type. (Among the standard data types provided
271271
in the <productname>PostgreSQL</productname> distribution, type
272272
<literal>box</> uses a semicolon (<literal>;</>) but all the others
273273
use comma.) In a multidimensional array, each dimension (row, plane,
@@ -300,8 +300,8 @@ SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
300300
if they are empty strings or contain curly braces, delimiter characters,
301301
double quotes, backslashes, or white space. Double quotes and backslashes
302302
embedded in element values will be backslash-escaped. For numeric
303-
datatypes it is safe to assume that double quotes will never appear, but
304-
for textual datatypes one should be prepared to cope with either presence
303+
data types it is safe to assume that double quotes will never appear, but
304+
for textual data types one should be prepared to cope with either presence
305305
or absence of quotes. (This is a change in behavior from pre-7.2
306306
<productname>PostgreSQL</productname> releases.)
307307
</para>

‎doc/src/sgml/charset.sgml

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.28 2002/09/18 20:09:31 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.29 2002/09/21 18:32:52 petere Exp $ -->
22

33
<chapter id="charset">
44
<title>Localization</>
@@ -405,27 +405,27 @@ perl: warning: Falling back to the standard locale ("C").
405405
</row>
406406
<row>
407407
<entry><literal>LATIN1</literal></entry>
408-
<entry>ISO 8859-1 ECMA-94 Latin Alphabet No.1</entry>
408+
<entry>ISO 8859-1 <acronym>ECMA</>-94 Latin Alphabet No.1</entry>
409409
</row>
410410
<row>
411411
<entry><literal>LATIN2</literal></entry>
412-
<entry>ISO 8859-2 ECMA-94 Latin Alphabet No.2</entry>
412+
<entry>ISO 8859-2 <acronym>ECMA</>-94 Latin Alphabet No.2</entry>
413413
</row>
414414
<row>
415415
<entry><literal>LATIN3</literal></entry>
416-
<entry>ISO 8859-3 ECMA-94 Latin Alphabet No.3</entry>
416+
<entry>ISO 8859-3 <acronym>ECMA</>-94 Latin Alphabet No.3</entry>
417417
</row>
418418
<row>
419419
<entry><literal>LATIN4</literal></entry>
420-
<entry>ISO 8859-4 ECMA-94 Latin Alphabet No.4</entry>
420+
<entry>ISO 8859-4 <acronym>ECMA</>-94 Latin Alphabet No.4</entry>
421421
</row>
422422
<row>
423423
<entry><literal>LATIN5</literal></entry>
424-
<entry>ISO 8859-9 ECMA-128 Latin Alphabet No.5</entry>
424+
<entry>ISO 8859-9 <acronym>ECMA</>-128 Latin Alphabet No.5</entry>
425425
</row>
426426
<row>
427427
<entry><literal>LATIN6</literal></entry>
428-
<entry>ISO 8859-10 ECMA-144 Latin Alphabet No.6</entry>
428+
<entry>ISO 8859-10 <acronym>ECMA</>-144 Latin Alphabet No.6</entry>
429429
</row>
430430
<row>
431431
<entry><literal>LATIN7</literal></entry>
@@ -441,23 +441,23 @@ perl: warning: Falling back to the standard locale ("C").
441441
</row>
442442
<row>
443443
<entry><literal>LATIN10</literal></entry>
444-
<entry>ISO 8859-16 ASRO SR 14111 Latin Alphabet No.10</entry>
444+
<entry>ISO 8859-16 <acronym>ASRO</> SR 14111 Latin Alphabet No.10</entry>
445445
</row>
446446
<row>
447447
<entry><literal>ISO-8859-5</literal></entry>
448-
<entry>ECMA-113 Latin/Cyrillic</entry>
448+
<entry><acronym>ECMA</>-113 Latin/Cyrillic</entry>
449449
</row>
450450
<row>
451451
<entry><literal>ISO-8859-6</literal></entry>
452-
<entry>ECMA-114 Latin/Arabic</entry>
452+
<entry><acronym>ECMA</>-114 Latin/Arabic</entry>
453453
</row>
454454
<row>
455455
<entry><literal>ISO-8859-7</literal></entry>
456-
<entry>ECMA-118 Latin/Greek</entry>
456+
<entry><acronym>ECMA</>-118 Latin/Greek</entry>
457457
</row>
458458
<row>
459459
<entry><literal>ISO-8859-8</literal></entry>
460-
<entry>ECMA-121 Latin/Hebrew</entry>
460+
<entry><acronym>ECMA</>-121 Latin/Hebrew</entry>
461461
</row>
462462
<row>
463463
<entry><literal>KOI8</literal></entry>
@@ -477,7 +477,7 @@ perl: warning: Falling back to the standard locale ("C").
477477
</row>
478478
<row>
479479
<entry><literal>TCVN</literal></entry>
480-
<entry>Vietnamese TCVN-5712(Windows CP1258)</entry>
480+
<entry>Vietnamese <acronym>TCVN</>-5712 (Windows CP1258)</entry>
481481
</row>
482482
<row>
483483
<entry><literal>WIN874</literal></entry>
@@ -500,7 +500,7 @@ perl: warning: Falling back to the standard locale ("C").
500500

501501
<important>
502502
<para>
503-
Not all APIs supports all the encodings listed above. For example, the
503+
Not all <acronym>API</>s supports all the encodings listed above. For example, the
504504
<productname>PostgreSQL</>
505505
JDBC driver does not support <literal>MULE_INTERNAL</>, <literal>LATIN6</>,
506506
<literal>LATIN8</>, and <literal>LATIN10</>.
@@ -572,7 +572,7 @@ $ <userinput>psql -l</userinput>
572572
<para>
573573
<productname>PostgreSQL</productname> supports an automatic
574574
encoding conversion between server and client for some
575-
encodings. The conversion info is stored in pg_converson system
575+
encodings. The conversion info is stored in <literal>pg_conversion</> system
576576
catalog. You can create a new conversion by using <command>CREATE
577577
CONVERSION</command>. PostgreSQL comes with some predefined
578578
conversions. They are listed in <xref
@@ -878,7 +878,7 @@ RESET CLIENT_ENCODING;
878878
<para>
879879
Using client_encoding variable.
880880

881-
If client_encoding variable in postgresql.conf is set, that
881+
If the <varname>client_encoding</> variable in <filename>postgresql.conf</> is set, that
882882
client encoding is automatically selected when a connection to the
883883
server is made. (This can subsequently be overridden using any of the
884884
other methods mentioned above.)

‎doc/src/sgml/client-auth.sgml

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.38 2002/09/18 20:09:31 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.39 2002/09/21 18:32:52 petere Exp $
33
-->
44

55
<chapter id="client-authentication">
@@ -261,7 +261,7 @@ hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <
261261
<term><literal>password</></term>
262262
<listitem>
263263
<para>
264-
Same as "md5", but the password is sent in cleartext over the
264+
Same as "md5", but the password is sent in clear text over the
265265
network. This should not be used on untrusted networks.
266266
See <xref linkend="auth-password"> for details.
267267
</para>
@@ -314,8 +314,10 @@ hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <
314314

315315
<para>
316316
For local connections, this only works on machines that
317-
support Unix-domain socket credentials (currently Linux,
318-
FreeBSD, NetBSD, and BSD/OS).
317+
support Unix-domain socket credentials (currently
318+
<systemitem class=osname>Linux</>, <systemitem
319+
class=osname>FreeBSD</>, <systemitem class=osname>NetBSD</>,
320+
and <systemitem class=osname>BSD/OS</>).
319321
</para>
320322

321323
<para>
@@ -504,7 +506,7 @@ local db1,db2,@demodbs all md5
504506
if you trust every user on every machine that is allowed to connect
505507
to the postmaster by the <filename>pg_hba.conf</> lines that specify
506508
<literal>trust</>. It is seldom reasonable to use <literal>trust</>
507-
for any TCP connections other than those from localhost (127.0.0.1).
509+
for any TCP connections other than those from <systemitem>localhost</> (127.0.0.1).
508510
</para>
509511

510512
</sect2>

‎doc/src/sgml/datatype.sgml

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.103 2002/09/18 21:35:20 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.104 2002/09/21 18:32:52 petere Exp $
33
-->
44

55
<chapter id="datatype">
@@ -703,7 +703,7 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
703703
implied <literal>UNIQUE</literal>. This is no longer automatic. If
704704
you wish a serial column to be <literal>UNIQUE</literal> or a
705705
<literal>PRIMARY KEY</literal> it must now be specified, same as with
706-
any other datatype.
706+
any other data type.
707707
</para></note>
708708
</sect2>
709709
</sect1>
@@ -2028,7 +2028,7 @@ January 8 04:05:06 1999 PST
20282028
<listitem>
20292029
<para>
20302030
The default time zone is specified as a constant integer offset
2031-
from GMT/UTC. It is not possible to adapt to daylight-saving
2031+
from <acronym>GMT</>/<acronym>UTC</>. It is not possible to adapt to daylight-saving
20322032
time when doing date/time arithmetic across
20332033
<acronym>DST</acronym> boundaries.
20342034
</para>
@@ -3025,14 +3025,14 @@ SELECT * FROM test;
30253025

30263026
<row>
30273027
<entry><type>regproc</></entry>
3028-
<entry>pg_proc</entry>
3028+
<entry><structname>pg_proc</></entry>
30293029
<entry>Function name</entry>
30303030
<entry>sum</entry>
30313031
</row>
30323032

30333033
<row>
30343034
<entry><type>regprocedure</></entry>
3035-
<entry>pg_proc</entry>
3035+
<entry><structname>pg_proc</></entry>
30363036
<entry>Function with argument types</entry>
30373037
<entry>sum(int4)</entry>
30383038
</row>
@@ -3098,7 +3098,7 @@ SELECT * FROM test;
30983098

30993099
<para>
31003100
Another identifier type used by the system is <type>xid</>, or transaction
3101-
(abbreviated xact) identifier. This is the datatype of the system columns
3101+
(abbreviated <abbrev>xact</>) identifier. This is the data type of the system columns
31023102
<structfield>xmin</> and <structfield>xmax</>.
31033103
Transaction identifiers are 32-bit quantities. In a long-lived
31043104
database it is possible for transaction IDs to wrap around. This
@@ -3110,7 +3110,7 @@ SELECT * FROM test;
31103110

31113111
<para>
31123112
A third identifier type used by the system is <type>cid</>, or command
3113-
identifier. This is the datatype of the system columns
3113+
identifier. This is the data type of the system columns
31143114
<structfield>cmin</> and <structfield>cmax</>.
31153115
Command identifiers are also 32-bit quantities. This creates a hard
31163116
limit of 2<superscript>32</> (4 billion) SQL commands within a single
@@ -3121,7 +3121,7 @@ SELECT * FROM test;
31213121

31223122
<para>
31233123
A final identifier type used by the system is <type>tid</>, or tuple
3124-
identifier. This is the datatype of the system column
3124+
identifier. This is the data type of the system column
31253125
<structfield>ctid</>. A tuple ID is a pair
31263126
(block number, tuple index within block) that identifies the
31273127
physical location of the tuple within its table.
@@ -3172,10 +3172,10 @@ SELECT * FROM test;
31723172
The <productname>PostgreSQL</productname> type system contains a number
31733173
of special-purpose entries that are collectively called
31743174
<firstterm>pseudo-types</>. A pseudo-type cannot be used as a column
3175-
datatype, but it can be used to declare a function's argument or result
3175+
data type, but it can be used to declare a function's argument or result
31763176
type. Each of the available pseudo-types is useful in situations where
31773177
a function's behavior does not correspond to simply taking or returning
3178-
a value of a specific SQL datatype.
3178+
a value of a specific SQL data type.
31793179
</para>
31803180

31813181
<para>
@@ -3198,12 +3198,12 @@ SELECT * FROM test;
31983198

31993199
<row>
32003200
<entry><type>any</></entry>
3201-
<entry>Indicates that a function accepts any input datatype whatever</entry>
3201+
<entry>Indicates that a function accepts any input data type whatever</entry>
32023202
</row>
32033203

32043204
<row>
32053205
<entry><type>anyarray</></entry>
3206-
<entry>Indicates that a function accepts any array datatype</entry>
3206+
<entry>Indicates that a function accepts any array data type</entry>
32073207
</row>
32083208

32093209
<row>
@@ -3243,7 +3243,7 @@ SELECT * FROM test;
32433243

32443244
<para>
32453245
Functions coded in C (whether built-in or dynamically loaded) may be
3246-
declared to accept or return any of these pseudo datatypes. It is up to
3246+
declared to accept or return any of these pseudo data types. It is up to
32473247
the function author to ensure that the function will behave safely
32483248
when a pseudo-type is used as an argument type.
32493249
</para>

‎doc/src/sgml/ddl.sgml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.4 2002/09/12 22:05:35 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ddl.sgml,v 1.5 2002/09/21 18:32:52 petere Exp $ -->
22

33
<chapter id="ddl">
44
<title>Data Definition</title>
@@ -765,7 +765,7 @@ CREATE TABLE order_items (
765765
Note that these do not excuse you from observing any constraints.
766766
For example, if an action specifies <literal>SET DEFAULT</literal>
767767
but the default value would not satisfy the foreign key, the
768-
deletion of the primary key wil fail.
768+
deletion of the primary key will fail.
769769
</para>
770770

771771
<para>
@@ -1425,7 +1425,7 @@ SHOW search_path;
14251425
</para>
14261426

14271427
<para>
1428-
The first schema in the seach path that exists is the default
1428+
The first schema in the search path that exists is the default
14291429
location for creating new objects. That is the reason that by
14301430
default objects are created in the public schema. When objects
14311431
are referenced in any other context without schema qualification
@@ -1466,8 +1466,8 @@ SET search_path TO myschema;
14661466
</para>
14671467

14681468
<para>
1469-
The search path works in the same way for datatype names, function names,
1470-
and operator names as it does for table names. Datatype and function
1469+
The search path works in the same way for data type names, function names,
1470+
and operator names as it does for table names. Data type and function
14711471
names can be qualified in exactly the same way as table names. If you
14721472
need to write a qualified operator name in an expression, there is a
14731473
special provision: you must write
@@ -1519,7 +1519,7 @@ REVOKE CREATE ON public FROM PUBLIC;
15191519
<para>
15201520
In addition to <literal>public</> and user-created schemas, each
15211521
database contains a <literal>pg_catalog</> schema, which contains
1522-
the system tables and all the built-in datatypes, functions, and
1522+
the system tables and all the built-in data types, functions, and
15231523
operators. <literal>pg_catalog</> is always effectively part of
15241524
the search path. If it is not named explicitly in the path then
15251525
it is implicitly searched <emphasis>before</> searching the path's

‎doc/src/sgml/developer.sgml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/developer.sgml,v 1.6 2001/10/09 18:45:59 petere Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/developer.sgml,v 1.7 2002/09/21 18:32:52 petere Exp $ -->
22
<!-- PostgreSQL Developer's Guide -->
33

44
<book id="developer">
@@ -17,13 +17,14 @@
1717
</bookinfo>
1818

1919
&sources;
20-
&arch-dev;
20+
&arch-dev;
2121
&catalogs;
2222
&protocol;
2323
&compiler;
2424
&bki;
2525
&page;
2626
&geqo;
27+
&gist;
2728
&nls;
2829
<!-- appendices -->
2930
&cvs;

0 commit comments

Comments
 (0)