Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitec7a6bd

Browse files
author
Neil Conway
committed
Replace "--" and "---" with "—" as appropriate, for better-looking
output.
1 parentdb1531f commitec7a6bd

37 files changed

+110
-108
lines changed

‎doc/src/sgml/advanced.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.45 2004/08/08 21:33:11 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/advanced.sgml,v 1.46 2004/11/15 06:32:13 neilc Exp $
33
-->
44

55
<chapter id="tutorial-advanced">
@@ -439,9 +439,9 @@ SELECT name, altitude
439439
indicates that the query should be run over only the
440440
<classname>cities</classname> table, and not tables below
441441
<classname>cities</classname> in the inheritance hierarchy. Many
442-
of the commands that we have already discussed--
442+
of the commands that we have already discussed&mdash;
443443
<command>SELECT</command>, <command>UPDATE</command>, and
444-
<command>DELETE</command>-- support this <literal>ONLY</literal>
444+
<command>DELETE</command>&mdash; support this <literal>ONLY</literal>
445445
notation.
446446
</para>
447447

‎doc/src/sgml/array.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/array.sgml,v 1.38 2004/08/08 05:55:55 joe Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/array.sgml,v 1.39 2004/11/15 06:32:13 neilc Exp $ -->
22

33
<sect1 id="arrays">
44
<title>Arrays</title>
@@ -49,7 +49,7 @@ CREATE TABLE tictactoe (
4949
</programlisting>
5050

5151
However, the current implementation does not enforce the array size
52-
limits--- the behavior is the same as for arrays of unspecified
52+
limits&mdash; the behavior is the same as for arrays of unspecified
5353
length.
5454
</para>
5555

‎doc/src/sgml/backup.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.50 2004/11/14 06:10:12 neilc Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.51 2004/11/15 06:32:13 neilc Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -499,7 +499,7 @@ tar -cf backup.tar /usr/local/pgsql/data
499499
the administrator specify a shell command to be executed to copy a
500500
completed segment file to wherever it needs to go. The command could be
501501
as simple as a <application>cp</>, or it could invoke a complex shell
502-
script--- it's all up to you.
502+
script&mdash; it's all up to you.
503503
</para>
504504

505505
<para>
@@ -725,7 +725,7 @@ SELECT pg_stop_backup();
725725
last base backup, the interval between base backups should usually be
726726
chosen based on how much storage you want to expend on archived WAL
727727
files. You should also consider how long you are prepared to spend
728-
recovering, if recovery should be necessary--- the system will have to
728+
recovering, if recovery should be necessary&mdash; the system will have to
729729
replay all those WAL segments, and that could take awhile if it has
730730
been a long time since the last base backup.
731731
</para>

‎doc/src/sgml/catalogs.sgml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!--
22
Documentation of the system catalogs, directed toward PostgreSQL developers
3-
$PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.91 2004/11/05 19:15:48 tgl Exp $
3+
$PostgreSQL: pgsql/doc/src/sgml/catalogs.sgml,v 2.92 2004/11/15 06:32:13 neilc Exp $
44
-->
55

66
<chapter id="catalogs">
@@ -16,7 +16,7 @@
1616
Normally, one should not change the system catalogs by hand, there
1717
are always SQL commands to do that. (For example, <command>CREATE
1818
DATABASE</command> inserts a row into the
19-
<structname>pg_database</structname> catalog--- and actually
19+
<structname>pg_database</structname> catalog&mdash; and actually
2020
creates the database on disk.) There are some exceptions for
2121
particularly esoteric operations, such as adding index access methods.
2222
</para>
@@ -2509,7 +2509,7 @@
25092509
not in its <structname>pg_opclass</structname> row, but in the associated
25102510
rows in <structname>pg_amop</structname> and
25112511
<structname>pg_amproc</structname>. Those rows are considered to be
2512-
part of the operator class definition--- this is not unlike the way
2512+
part of the operator class definition&mdash; this is not unlike the way
25132513
that a relation is defined by a single <structname>pg_class</structname>
25142514
row plus associated rows in <structname>pg_attribute</structname> and
25152515
other tables.
@@ -4275,7 +4275,7 @@
42754275
<para>
42764276
<structname>pg_stats</structname> is also designed to present the
42774277
information in a more readable format than the underlying catalog
4278-
--- at the cost that its schema must be extended whenever new slot types
4278+
&mdash; at the cost that its schema must be extended whenever new slot types
42794279
are defined for <structname>pg_statistic</structname>.
42804280
</para>
42814281

‎doc/src/sgml/charset.sgml‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.45 2004/09/17 21:59:56 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/charset.sgml,v 2.46 2004/11/15 06:32:13 neilc Exp $ -->
22

33
<chapter id="charset">
44
<title>Localization</>
@@ -829,12 +829,13 @@ RESET client_encoding;
829829
</para>
830830

831831
<para>
832-
If the conversion of a particular character is not possible --
833-
suppose you chose <literal>EUC_JP</literal> for the server and
834-
<literal>LATIN1</literal> for the client, then some Japanese
835-
characters cannot be converted to <literal>LATIN1</literal> -- it
836-
is transformed to its hexadecimal byte values in parentheses,
837-
e.g., <literal>(826C)</literal>.
832+
If the conversion of a particular character is not possible
833+
&mdash; suppose you chose <literal>EUC_JP</literal> for the
834+
server and <literal>LATIN1</literal> for the client, then some
835+
Japanese characters cannot be converted to
836+
<literal>LATIN1</literal> &mdash; it is transformed to its
837+
hexadecimal byte values in parentheses, e.g.,
838+
<literal>(826C)</literal>.
838839
</para>
839840
</sect2>
840841

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.67 2004/11/10 21:54:23 petere Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.68 2004/11/15 06:32:13 neilc Exp $
33
-->
44

55
<chapter id="client-authentication">
@@ -14,7 +14,7 @@ $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.67 2004/11/10 21:54:23 pete
1414
specifies which <productname>PostgreSQL</productname> user name it
1515
wants to connect as, much the same way one logs into a Unix computer
1616
as a particular user. Within the SQL environment the active database
17-
user name determines access privileges to database objects-- see
17+
user name determines access privileges to database objects&mdash; see
1818
<xref linkend="user-manag"> for more information. Therefore, it is
1919
essential to restrict which database users can connect.
2020
</para>

‎doc/src/sgml/datetime.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.42 2004/08/10 00:55:03 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.43 2004/11/15 06:32:13 neilc Exp $
33
-->
44

55
<appendix id="datetime-appendix">
@@ -370,7 +370,7 @@ $PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.42 2004/08/10 00:55:03 tgl Exp
370370
<xref linkend="datetime-timezone-input-table"> shows the time zone
371371
abbreviations recognized by <productname>PostgreSQL</productname>
372372
in date/time input values. Note that these names are <emphasis>not</>
373-
used for date/time output--- display is driven by the currently
373+
used for date/time output&mdash; display is driven by the currently
374374
selected <xref linkend="guc-timezone"> parameter setting. (It is
375375
likely that future releases will make some use of <varname>timezone</>
376376
for input as well.)

‎doc/src/sgml/ddl.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.31 2004/10/21 21:33:59 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.32 2004/11/15 06:32:13 neilc Exp $ -->
22

33
<chapter id="ddl">
44
<title>Data Definition</title>
@@ -350,7 +350,7 @@ DROP TABLE products;
350350
identifiers are also 32-bit quantities. This creates a hard limit
351351
of 2<superscript>32</> (4 billion) <acronym>SQL</acronym> commands
352352
within a single transaction. In practice this limit is not a
353-
problem--- note that the limit is on number of
353+
problem&mdash; note that the limit is on number of
354354
<acronym>SQL</acronym> commands, not number of rows processed.
355355
</para>
356356
</sect1>

‎doc/src/sgml/dfunc.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/dfunc.sgml,v 1.27 2003/11/29 19:51:36 pgsql Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/dfunc.sgml,v 1.28 2004/11/15 06:32:13 neilc Exp $
33
-->
44

55
<sect2 id="dfunc">
@@ -38,8 +38,8 @@ $PostgreSQL: pgsql/doc/src/sgml/dfunc.sgml,v 1.27 2003/11/29 19:51:36 pgsql Exp
3838
in memory when they are loaded by the executable. (Object files
3939
intended for executables are usually not compiled that way.) The
4040
command to link a shared library contains special flags to
41-
distinguish it from linking an executable. --- Atleastthis is the
42-
theory. Onsome systems the practice is much uglier.
41+
distinguish it from linking an executable (atleastin theory
42+
&mdash; onsome systems the practice is much uglier).
4343
</para>
4444

4545
<para>

‎doc/src/sgml/docguide.sgml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.50 2004/02/17 02:53:03 neilc Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/docguide.sgml,v 1.51 2004/11/15 06:32:13 neilc Exp $ -->
22

33
<appendix id="docguide">
44
<title>Documentation</title>
@@ -88,7 +88,7 @@
8888
This is the definition of DocBook itself. We currently use
8989
version 4.2; you cannot use later or earlier versions. Note
9090
that there is also an <acronym>XML</acronym> version of DocBook
91-
-- do not use that.
91+
&mdash; do not use that.
9292
</para>
9393
</listitem>
9494
</varlistentry>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp