Uppercase SGML entity declarations
Hi,
I have made very small modifications to a few files in the
documentation directory, which involve SGML entity declarations.
Currently they are all written lowercase, the patch makes them
uppercase. This won't affect SGML parsing, as SGML is case insensitive -
even though it is a good practice to write SGML declarations in uppercase.
An example is:
<!entity abort system "abort.sgml">
written
<!ENTITY abort SYSTEM "abort.sgml">
This patch makes also every single directive of them XML compliant.
The list of files that have been changed is:
doc/src/sgml/Makefile
doc/src/sgml/filelist.sgml
doc/src/sgml/postgres.sgml
doc/src/sgml/ref/allfiles.sgml
doc/src/sgml/standalone-install.sgml
Thanks.
Cheers,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
Attachments:
uppercase-sgml-entity-declarations.patchtext/plain; name=uppercase-sgml-entity-declarations.patch; x-mac-creator=0; x-mac-type=0Download
diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile
index 3041a53..c5078a8 100644
--- a/doc/src/sgml/Makefile
+++ b/doc/src/sgml/Makefile
@@ -126,8 +126,8 @@ bookindex.sgml: HTML.index
# changes.
version.sgml: $(top_srcdir)/configure
{ \
- echo "<!entity version \"$(VERSION)\">"; \
- echo "<!entity majorversion \"$(MAJORVERSION)\">"; \
+ echo "<!ENTITY version \"$(VERSION)\">"; \
+ echo "<!ENTITY majorversion \"$(MAJORVERSION)\">"; \
} > $@
features-supported.sgml: $(top_srcdir)/src/backend/catalog/sql_feature_packages.txt $(top_srcdir)/src/backend/catalog/sql_features.txt
@@ -220,9 +220,9 @@ HISTORY.html: generate_history.pl $(wildcard $(srcdir)/release*.sgml)
rm tempfile_HISTORY.sgml
regress_README.html: regress.sgml
- ( echo '<!doctype chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
- echo '<!entity % standalone-ignore "IGNORE">'; \
- echo '<!entity % standalone-include "INCLUDE"> ]>'; \
+ ( echo '<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" ['; \
+ echo '<!ENTITY % standalone-ignore "IGNORE">'; \
+ echo '<!ENTITY % standalone-include "INCLUDE"> ]>'; \
cat $< ) >tempfile_regress_README.sgml
$(JADE.text) -V nochunks tempfile_regress_README.sgml > $@
rm tempfile_regress_README.sgml
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
index 1a60796..ed39e0b 100644
--- a/doc/src/sgml/filelist.sgml
+++ b/doc/src/sgml/filelist.sgml
@@ -1,176 +1,176 @@
<!-- doc/src/sgml/filelist.sgml -->
-<!entity history SYSTEM "history.sgml">
-<!entity info SYSTEM "info.sgml">
-<!entity intro SYSTEM "intro.sgml">
-<!entity legal SYSTEM "legal.sgml">
-<!entity notation SYSTEM "notation.sgml">
-<!entity problems SYSTEM "problems.sgml">
+<!ENTITY history SYSTEM "history.sgml">
+<!ENTITY info SYSTEM "info.sgml">
+<!ENTITY intro SYSTEM "intro.sgml">
+<!ENTITY legal SYSTEM "legal.sgml">
+<!ENTITY notation SYSTEM "notation.sgml">
+<!ENTITY problems SYSTEM "problems.sgml">
<!-- tutorial -->
-<!entity advanced SYSTEM "advanced.sgml">
-<!entity query SYSTEM "query.sgml">
-<!entity start SYSTEM "start.sgml">
+<!ENTITY advanced SYSTEM "advanced.sgml">
+<!ENTITY query SYSTEM "query.sgml">
+<!ENTITY start SYSTEM "start.sgml">
<!-- currently unused, but contains some interesting information -->
-<!entity sql SYSTEM "sql.sgml">
+<!ENTITY sql SYSTEM "sql.sgml">
<!-- user's guide -->
-<!entity array SYSTEM "array.sgml">
-<!entity datatype SYSTEM "datatype.sgml">
-<!entity ddl SYSTEM "ddl.sgml">
-<!entity dml SYSTEM "dml.sgml">
-<!entity func SYSTEM "func.sgml">
-<!entity indices SYSTEM "indices.sgml">
-<!entity mvcc SYSTEM "mvcc.sgml">
-<!entity perform SYSTEM "perform.sgml">
-<!entity queries SYSTEM "queries.sgml">
-<!entity rowtypes SYSTEM "rowtypes.sgml">
-<!entity syntax SYSTEM "syntax.sgml">
-<!entity textsearch SYSTEM "textsearch.sgml">
-<!entity typeconv SYSTEM "typeconv.sgml">
+<!ENTITY array SYSTEM "array.sgml">
+<!ENTITY datatype SYSTEM "datatype.sgml">
+<!ENTITY ddl SYSTEM "ddl.sgml">
+<!ENTITY dml SYSTEM "dml.sgml">
+<!ENTITY func SYSTEM "func.sgml">
+<!ENTITY indices SYSTEM "indices.sgml">
+<!ENTITY mvcc SYSTEM "mvcc.sgml">
+<!ENTITY perform SYSTEM "perform.sgml">
+<!ENTITY queries SYSTEM "queries.sgml">
+<!ENTITY rowtypes SYSTEM "rowtypes.sgml">
+<!ENTITY syntax SYSTEM "syntax.sgml">
+<!ENTITY textsearch SYSTEM "textsearch.sgml">
+<!ENTITY typeconv SYSTEM "typeconv.sgml">
<!-- administrator's guide -->
-<!entity backup SYSTEM "backup.sgml">
-<!entity charset SYSTEM "charset.sgml">
-<!entity client-auth SYSTEM "client-auth.sgml">
-<!entity diskusage SYSTEM "diskusage.sgml">
-<!entity high-availability SYSTEM "high-availability.sgml">
-<!entity installation SYSTEM "installation.sgml">
-<!entity installw SYSTEM "install-windows.sgml">
-<!entity maintenance SYSTEM "maintenance.sgml">
-<!entity manage-ag SYSTEM "manage-ag.sgml">
-<!entity monitoring SYSTEM "monitoring.sgml">
-<!entity regress SYSTEM "regress.sgml">
-<!entity recovery-config SYSTEM "recovery-config.sgml">
-<!entity runtime SYSTEM "runtime.sgml">
-<!entity config SYSTEM "config.sgml">
-<!entity user-manag SYSTEM "user-manag.sgml">
-<!entity wal SYSTEM "wal.sgml">
+<!ENTITY backup SYSTEM "backup.sgml">
+<!ENTITY charset SYSTEM "charset.sgml">
+<!ENTITY client-auth SYSTEM "client-auth.sgml">
+<!ENTITY diskusage SYSTEM "diskusage.sgml">
+<!ENTITY high-availability SYSTEM "high-availability.sgml">
+<!ENTITY installation SYSTEM "installation.sgml">
+<!ENTITY installw SYSTEM "install-windows.sgml">
+<!ENTITY maintenance SYSTEM "maintenance.sgml">
+<!ENTITY manage-ag SYSTEM "manage-ag.sgml">
+<!ENTITY monitoring SYSTEM "monitoring.sgml">
+<!ENTITY regress SYSTEM "regress.sgml">
+<!ENTITY recovery-config SYSTEM "recovery-config.sgml">
+<!ENTITY runtime SYSTEM "runtime.sgml">
+<!ENTITY config SYSTEM "config.sgml">
+<!ENTITY user-manag SYSTEM "user-manag.sgml">
+<!ENTITY wal SYSTEM "wal.sgml">
<!-- programmer's guide -->
-<!entity dfunc SYSTEM "dfunc.sgml">
-<!entity ecpg SYSTEM "ecpg.sgml">
-<!entity extend SYSTEM "extend.sgml">
-<!entity external-projects SYSTEM "external-projects.sgml">
-<!entity func-ref SYSTEM "func-ref.sgml">
-<!entity infoschema SYSTEM "information_schema.sgml">
-<!entity libpq SYSTEM "libpq.sgml">
-<!entity lobj SYSTEM "lobj.sgml">
-<!entity rules SYSTEM "rules.sgml">
-<!entity spi SYSTEM "spi.sgml">
-<!entity trigger SYSTEM "trigger.sgml">
-<!entity xaggr SYSTEM "xaggr.sgml">
-<!entity xfunc SYSTEM "xfunc.sgml">
-<!entity xindex SYSTEM "xindex.sgml">
-<!entity xplang SYSTEM "xplang.sgml">
-<!entity xoper SYSTEM "xoper.sgml">
-<!entity xtypes SYSTEM "xtypes.sgml">
-<!entity plperl SYSTEM "plperl.sgml">
-<!entity plpython SYSTEM "plpython.sgml">
-<!entity plsql SYSTEM "plpgsql.sgml">
-<!entity pltcl SYSTEM "pltcl.sgml">
+<!ENTITY dfunc SYSTEM "dfunc.sgml">
+<!ENTITY ecpg SYSTEM "ecpg.sgml">
+<!ENTITY extend SYSTEM "extend.sgml">
+<!ENTITY external-projects SYSTEM "external-projects.sgml">
+<!ENTITY func-ref SYSTEM "func-ref.sgml">
+<!ENTITY infoschema SYSTEM "information_schema.sgml">
+<!ENTITY libpq SYSTEM "libpq.sgml">
+<!ENTITY lobj SYSTEM "lobj.sgml">
+<!ENTITY rules SYSTEM "rules.sgml">
+<!ENTITY spi SYSTEM "spi.sgml">
+<!ENTITY trigger SYSTEM "trigger.sgml">
+<!ENTITY xaggr SYSTEM "xaggr.sgml">
+<!ENTITY xfunc SYSTEM "xfunc.sgml">
+<!ENTITY xindex SYSTEM "xindex.sgml">
+<!ENTITY xplang SYSTEM "xplang.sgml">
+<!ENTITY xoper SYSTEM "xoper.sgml">
+<!ENTITY xtypes SYSTEM "xtypes.sgml">
+<!ENTITY plperl SYSTEM "plperl.sgml">
+<!ENTITY plpython SYSTEM "plpython.sgml">
+<!ENTITY plsql SYSTEM "plpgsql.sgml">
+<!ENTITY pltcl SYSTEM "pltcl.sgml">
<!-- reference pages -->
-<!entity % allfiles SYSTEM "ref/allfiles.sgml">
+<!ENTITY % allfiles SYSTEM "ref/allfiles.sgml">
%allfiles;
<!-- developer's guide -->
-<!entity arch-dev SYSTEM "arch-dev.sgml">
-<!entity bki SYSTEM "bki.sgml">
-<!entity catalogs SYSTEM "catalogs.sgml">
-<!entity geqo SYSTEM "geqo.sgml">
-<!entity gist SYSTEM "gist.sgml">
-<!entity gin SYSTEM "gin.sgml">
-<!entity planstats SYSTEM "planstats.sgml">
-<!entity indexam SYSTEM "indexam.sgml">
-<!entity nls SYSTEM "nls.sgml">
-<!entity plhandler SYSTEM "plhandler.sgml">
-<!entity fdwhandler SYSTEM "fdwhandler.sgml">
-<!entity protocol SYSTEM "protocol.sgml">
-<!entity sources SYSTEM "sources.sgml">
-<!entity storage SYSTEM "storage.sgml">
+<!ENTITY arch-dev SYSTEM "arch-dev.sgml">
+<!ENTITY bki SYSTEM "bki.sgml">
+<!ENTITY catalogs SYSTEM "catalogs.sgml">
+<!ENTITY geqo SYSTEM "geqo.sgml">
+<!ENTITY gist SYSTEM "gist.sgml">
+<!ENTITY gin SYSTEM "gin.sgml">
+<!ENTITY planstats SYSTEM "planstats.sgml">
+<!ENTITY indexam SYSTEM "indexam.sgml">
+<!ENTITY nls SYSTEM "nls.sgml">
+<!ENTITY plhandler SYSTEM "plhandler.sgml">
+<!ENTITY fdwhandler SYSTEM "fdwhandler.sgml">
+<!ENTITY protocol SYSTEM "protocol.sgml">
+<!ENTITY sources SYSTEM "sources.sgml">
+<!ENTITY storage SYSTEM "storage.sgml">
<!-- contrib information -->
-<!entity contrib SYSTEM "contrib.sgml">
-<!entity adminpack SYSTEM "adminpack.sgml">
-<!entity auth-delay SYSTEM "auth-delay.sgml">
-<!entity auto-explain SYSTEM "auto-explain.sgml">
-<!entity btree-gin SYSTEM "btree-gin.sgml">
-<!entity btree-gist SYSTEM "btree-gist.sgml">
-<!entity chkpass SYSTEM "chkpass.sgml">
-<!entity citext SYSTEM "citext.sgml">
-<!entity cube SYSTEM "cube.sgml">
-<!entity dblink SYSTEM "dblink.sgml">
-<!entity dict-int SYSTEM "dict-int.sgml">
-<!entity dict-xsyn SYSTEM "dict-xsyn.sgml">
-<!entity dummy-seclabel SYSTEM "dummy-seclabel.sgml">
-<!entity earthdistance SYSTEM "earthdistance.sgml">
-<!entity file-fdw SYSTEM "file-fdw.sgml">
-<!entity fuzzystrmatch SYSTEM "fuzzystrmatch.sgml">
-<!entity hstore SYSTEM "hstore.sgml">
-<!entity intagg SYSTEM "intagg.sgml">
-<!entity intarray SYSTEM "intarray.sgml">
-<!entity isn SYSTEM "isn.sgml">
-<!entity lo SYSTEM "lo.sgml">
-<!entity ltree SYSTEM "ltree.sgml">
-<!entity oid2name SYSTEM "oid2name.sgml">
-<!entity pageinspect SYSTEM "pageinspect.sgml">
-<!entity passwordcheck SYSTEM "passwordcheck.sgml">
-<!entity pgbench SYSTEM "pgbench.sgml">
-<!entity pgarchivecleanup SYSTEM "pgarchivecleanup.sgml">
-<!entity pgbuffercache SYSTEM "pgbuffercache.sgml">
-<!entity pgcrypto SYSTEM "pgcrypto.sgml">
-<!entity pgfreespacemap SYSTEM "pgfreespacemap.sgml">
-<!entity pgrowlocks SYSTEM "pgrowlocks.sgml">
-<!entity pgstandby SYSTEM "pgstandby.sgml">
-<!entity pgstatstatements SYSTEM "pgstatstatements.sgml">
-<!entity pgstattuple SYSTEM "pgstattuple.sgml">
-<!entity pgtestfsync SYSTEM "pgtestfsync.sgml">
-<!entity pgtrgm SYSTEM "pgtrgm.sgml">
-<!entity pgupgrade SYSTEM "pgupgrade.sgml">
-<!entity seg SYSTEM "seg.sgml">
-<!entity contrib-spi SYSTEM "contrib-spi.sgml">
-<!entity sepgsql SYSTEM "sepgsql.sgml">
-<!entity sslinfo SYSTEM "sslinfo.sgml">
-<!entity tablefunc SYSTEM "tablefunc.sgml">
-<!entity test-parser SYSTEM "test-parser.sgml">
-<!entity tsearch2 SYSTEM "tsearch2.sgml">
-<!entity unaccent SYSTEM "unaccent.sgml">
-<!entity uuid-ossp SYSTEM "uuid-ossp.sgml">
-<!entity vacuumlo SYSTEM "vacuumlo.sgml">
-<!entity xml2 SYSTEM "xml2.sgml">
+<!ENTITY contrib SYSTEM "contrib.sgml">
+<!ENTITY adminpack SYSTEM "adminpack.sgml">
+<!ENTITY auth-delay SYSTEM "auth-delay.sgml">
+<!ENTITY auto-explain SYSTEM "auto-explain.sgml">
+<!ENTITY btree-gin SYSTEM "btree-gin.sgml">
+<!ENTITY btree-gist SYSTEM "btree-gist.sgml">
+<!ENTITY chkpass SYSTEM "chkpass.sgml">
+<!ENTITY citext SYSTEM "citext.sgml">
+<!ENTITY cube SYSTEM "cube.sgml">
+<!ENTITY dblink SYSTEM "dblink.sgml">
+<!ENTITY dict-int SYSTEM "dict-int.sgml">
+<!ENTITY dict-xsyn SYSTEM "dict-xsyn.sgml">
+<!ENTITY dummy-seclabel SYSTEM "dummy-seclabel.sgml">
+<!ENTITY earthdistance SYSTEM "earthdistance.sgml">
+<!ENTITY file-fdw SYSTEM "file-fdw.sgml">
+<!ENTITY fuzzystrmatch SYSTEM "fuzzystrmatch.sgml">
+<!ENTITY hstore SYSTEM "hstore.sgml">
+<!ENTITY intagg SYSTEM "intagg.sgml">
+<!ENTITY intarray SYSTEM "intarray.sgml">
+<!ENTITY isn SYSTEM "isn.sgml">
+<!ENTITY lo SYSTEM "lo.sgml">
+<!ENTITY ltree SYSTEM "ltree.sgml">
+<!ENTITY oid2name SYSTEM "oid2name.sgml">
+<!ENTITY pageinspect SYSTEM "pageinspect.sgml">
+<!ENTITY passwordcheck SYSTEM "passwordcheck.sgml">
+<!ENTITY pgbench SYSTEM "pgbench.sgml">
+<!ENTITY pgarchivecleanup SYSTEM "pgarchivecleanup.sgml">
+<!ENTITY pgbuffercache SYSTEM "pgbuffercache.sgml">
+<!ENTITY pgcrypto SYSTEM "pgcrypto.sgml">
+<!ENTITY pgfreespacemap SYSTEM "pgfreespacemap.sgml">
+<!ENTITY pgrowlocks SYSTEM "pgrowlocks.sgml">
+<!ENTITY pgstandby SYSTEM "pgstandby.sgml">
+<!ENTITY pgstatstatements SYSTEM "pgstatstatements.sgml">
+<!ENTITY pgstattuple SYSTEM "pgstattuple.sgml">
+<!ENTITY pgtestfsync SYSTEM "pgtestfsync.sgml">
+<!ENTITY pgtrgm SYSTEM "pgtrgm.sgml">
+<!ENTITY pgupgrade SYSTEM "pgupgrade.sgml">
+<!ENTITY seg SYSTEM "seg.sgml">
+<!ENTITY contrib-spi SYSTEM "contrib-spi.sgml">
+<!ENTITY sepgsql SYSTEM "sepgsql.sgml">
+<!ENTITY sslinfo SYSTEM "sslinfo.sgml">
+<!ENTITY tablefunc SYSTEM "tablefunc.sgml">
+<!ENTITY test-parser SYSTEM "test-parser.sgml">
+<!ENTITY tsearch2 SYSTEM "tsearch2.sgml">
+<!ENTITY unaccent SYSTEM "unaccent.sgml">
+<!ENTITY uuid-ossp SYSTEM "uuid-ossp.sgml">
+<!ENTITY vacuumlo SYSTEM "vacuumlo.sgml">
+<!ENTITY xml2 SYSTEM "xml2.sgml">
<!-- appendixes -->
-<!entity contacts SYSTEM "contacts.sgml">
-<!entity datetime SYSTEM "datetime.sgml">
-<!entity docguide SYSTEM "docguide.sgml">
-<!entity errcodes SYSTEM "errcodes.sgml">
-<!entity features SYSTEM "features.sgml">
-<!entity keywords SYSTEM "keywords.sgml">
-<!entity sourcerepo SYSTEM "sourcerepo.sgml">
-
-<!entity release SYSTEM "release.sgml">
-<!entity release-9.1 SYSTEM "release-9.1.sgml">
-<!entity release-9.0 SYSTEM "release-9.0.sgml">
-<!entity release-8.4 SYSTEM "release-8.4.sgml">
-<!entity release-8.3 SYSTEM "release-8.3.sgml">
-<!entity release-8.2 SYSTEM "release-8.2.sgml">
-<!entity release-8.1 SYSTEM "release-8.1.sgml">
-<!entity release-8.0 SYSTEM "release-8.0.sgml">
-<!entity release-7.4 SYSTEM "release-7.4.sgml">
-<!entity release-old SYSTEM "release-old.sgml">
-
-<!entity acronyms SYSTEM "acronyms.sgml">
-
-<!entity features-supported SYSTEM "features-supported.sgml">
-<!entity features-unsupported SYSTEM "features-unsupported.sgml">
-
-<!entity errcodes-table SYSTEM "errcodes-table.sgml">
+<!ENTITY contacts SYSTEM "contacts.sgml">
+<!ENTITY datetime SYSTEM "datetime.sgml">
+<!ENTITY docguide SYSTEM "docguide.sgml">
+<!ENTITY errcodes SYSTEM "errcodes.sgml">
+<!ENTITY features SYSTEM "features.sgml">
+<!ENTITY keywords SYSTEM "keywords.sgml">
+<!ENTITY sourcerepo SYSTEM "sourcerepo.sgml">
+
+<!ENTITY release SYSTEM "release.sgml">
+<!ENTITY release-9.1 SYSTEM "release-9.1.sgml">
+<!ENTITY release-9.0 SYSTEM "release-9.0.sgml">
+<!ENTITY release-8.4 SYSTEM "release-8.4.sgml">
+<!ENTITY release-8.3 SYSTEM "release-8.3.sgml">
+<!ENTITY release-8.2 SYSTEM "release-8.2.sgml">
+<!ENTITY release-8.1 SYSTEM "release-8.1.sgml">
+<!ENTITY release-8.0 SYSTEM "release-8.0.sgml">
+<!ENTITY release-7.4 SYSTEM "release-7.4.sgml">
+<!ENTITY release-old SYSTEM "release-old.sgml">
+
+<!ENTITY acronyms SYSTEM "acronyms.sgml">
+
+<!ENTITY features-supported SYSTEM "features-supported.sgml">
+<!ENTITY features-unsupported SYSTEM "features-unsupported.sgml">
+
+<!ENTITY errcodes-table SYSTEM "errcodes-table.sgml">
<!-- back matter -->
-<!entity biblio SYSTEM "biblio.sgml">
-<!entity bookindex SYSTEM "bookindex.sgml">
+<!ENTITY biblio SYSTEM "biblio.sgml">
+<!ENTITY bookindex SYSTEM "bookindex.sgml">
<!--
Some parts of the documentation are also source for some plain-text
@@ -178,11 +178,11 @@
some parts (e.g., external xref's) when generating these files we use
these parameter entities. See also standalone-install.sgml.
-->
-<!entity % standalone-ignore "INCLUDE">
-<!entity % standalone-include "IGNORE">
+<!ENTITY % standalone-ignore "INCLUDE">
+<!ENTITY % standalone-include "IGNORE">
<!--
By default, no index is included. Use -i include-index on the command line
to include it.
-->
-<!entity % include-index "IGNORE">
+<!ENTITY % include-index "IGNORE">
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
index 98d19a5..ac1da22 100644
--- a/doc/src/sgml/postgres.sgml
+++ b/doc/src/sgml/postgres.sgml
@@ -2,12 +2,12 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
-<!entity % version SYSTEM "version.sgml">
+<!ENTITY % version SYSTEM "version.sgml">
%version;
-<!entity % filelist SYSTEM "filelist.sgml">
+<!ENTITY % filelist SYSTEM "filelist.sgml">
%filelist;
-<!entity reference SYSTEM "reference.sgml">
+<!ENTITY reference SYSTEM "reference.sgml">
]>
diff --git a/doc/src/sgml/ref/allfiles.sgml b/doc/src/sgml/ref/allfiles.sgml
index ac6ac5b..8a8616b 100644
--- a/doc/src/sgml/ref/allfiles.sgml
+++ b/doc/src/sgml/ref/allfiles.sgml
@@ -5,177 +5,177 @@ Complete list of usable sgml source files in this directory.
-->
<!-- SQL commands -->
-<!entity abort system "abort.sgml">
-<!entity alterAggregate system "alter_aggregate.sgml">
-<!entity alterCollation system "alter_collation.sgml">
-<!entity alterConversion system "alter_conversion.sgml">
-<!entity alterDatabase system "alter_database.sgml">
-<!entity alterDefaultPrivileges system "alter_default_privileges.sgml">
-<!entity alterDomain system "alter_domain.sgml">
-<!entity alterExtension system "alter_extension.sgml">
-<!entity alterForeignDataWrapper system "alter_foreign_data_wrapper.sgml">
-<!entity alterForeignTable system "alter_foreign_table.sgml">
-<!entity alterFunction system "alter_function.sgml">
-<!entity alterGroup system "alter_group.sgml">
-<!entity alterIndex system "alter_index.sgml">
-<!entity alterLanguage system "alter_language.sgml">
-<!entity alterLargeObject system "alter_large_object.sgml">
-<!entity alterOperator system "alter_operator.sgml">
-<!entity alterOperatorClass system "alter_opclass.sgml">
-<!entity alterOperatorFamily system "alter_opfamily.sgml">
-<!entity alterRole system "alter_role.sgml">
-<!entity alterSchema system "alter_schema.sgml">
-<!entity alterServer system "alter_server.sgml">
-<!entity alterSequence system "alter_sequence.sgml">
-<!entity alterTable system "alter_table.sgml">
-<!entity alterTableSpace system "alter_tablespace.sgml">
-<!entity alterTSConfig system "alter_tsconfig.sgml">
-<!entity alterTSDictionary system "alter_tsdictionary.sgml">
-<!entity alterTSParser system "alter_tsparser.sgml">
-<!entity alterTSTemplate system "alter_tstemplate.sgml">
-<!entity alterTrigger system "alter_trigger.sgml">
-<!entity alterType system "alter_type.sgml">
-<!entity alterUser system "alter_user.sgml">
-<!entity alterUserMapping system "alter_user_mapping.sgml">
-<!entity alterView system "alter_view.sgml">
-<!entity analyze system "analyze.sgml">
-<!entity begin system "begin.sgml">
-<!entity checkpoint system "checkpoint.sgml">
-<!entity close system "close.sgml">
-<!entity cluster system "cluster.sgml">
-<!entity commentOn system "comment.sgml">
-<!entity commit system "commit.sgml">
-<!entity commitPrepared system "commit_prepared.sgml">
-<!entity copyTable system "copy.sgml">
-<!entity createAggregate system "create_aggregate.sgml">
-<!entity createCast system "create_cast.sgml">
-<!entity createCollation system "create_collation.sgml">
-<!entity createConversion system "create_conversion.sgml">
-<!entity createDatabase system "create_database.sgml">
-<!entity createDomain system "create_domain.sgml">
-<!entity createExtension system "create_extension.sgml">
-<!entity createForeignDataWrapper system "create_foreign_data_wrapper.sgml">
-<!entity createForeignTable system "create_foreign_table.sgml">
-<!entity createFunction system "create_function.sgml">
-<!entity createGroup system "create_group.sgml">
-<!entity createIndex system "create_index.sgml">
-<!entity createLanguage system "create_language.sgml">
-<!entity createOperator system "create_operator.sgml">
-<!entity createOperatorClass system "create_opclass.sgml">
-<!entity createOperatorFamily system "create_opfamily.sgml">
-<!entity createRole system "create_role.sgml">
-<!entity createRule system "create_rule.sgml">
-<!entity createSchema system "create_schema.sgml">
-<!entity createSequence system "create_sequence.sgml">
-<!entity createServer system "create_server.sgml">
-<!entity createTable system "create_table.sgml">
-<!entity createTableAs system "create_table_as.sgml">
-<!entity createTableSpace system "create_tablespace.sgml">
-<!entity createTrigger system "create_trigger.sgml">
-<!entity createTSConfig system "create_tsconfig.sgml">
-<!entity createTSDictionary system "create_tsdictionary.sgml">
-<!entity createTSParser system "create_tsparser.sgml">
-<!entity createTSTemplate system "create_tstemplate.sgml">
-<!entity createType system "create_type.sgml">
-<!entity createUser system "create_user.sgml">
-<!entity createUserMapping system "create_user_mapping.sgml">
-<!entity createView system "create_view.sgml">
-<!entity deallocate system "deallocate.sgml">
-<!entity declare system "declare.sgml">
-<!entity delete system "delete.sgml">
-<!entity discard system "discard.sgml">
-<!entity do system "do.sgml">
-<!entity dropAggregate system "drop_aggregate.sgml">
-<!entity dropCast system "drop_cast.sgml">
-<!entity dropCollation system "drop_collation.sgml">
-<!entity dropConversion system "drop_conversion.sgml">
-<!entity dropDatabase system "drop_database.sgml">
-<!entity dropDomain system "drop_domain.sgml">
-<!entity dropExtension system "drop_extension.sgml">
-<!entity dropForeignDataWrapper system "drop_foreign_data_wrapper.sgml">
-<!entity dropForeignTable system "drop_foreign_table.sgml">
-<!entity dropFunction system "drop_function.sgml">
-<!entity dropGroup system "drop_group.sgml">
-<!entity dropIndex system "drop_index.sgml">
-<!entity dropLanguage system "drop_language.sgml">
-<!entity dropOperator system "drop_operator.sgml">
-<!entity dropOperatorClass system "drop_opclass.sgml">
-<!entity dropOperatorFamily system "drop_opfamily.sgml">
-<!entity dropOwned system "drop_owned.sgml">
-<!entity dropRole system "drop_role.sgml">
-<!entity dropRule system "drop_rule.sgml">
-<!entity dropSchema system "drop_schema.sgml">
-<!entity dropSequence system "drop_sequence.sgml">
-<!entity dropServer system "drop_server.sgml">
-<!entity dropTable system "drop_table.sgml">
-<!entity dropTableSpace system "drop_tablespace.sgml">
-<!entity dropTrigger system "drop_trigger.sgml">
-<!entity dropTSConfig system "drop_tsconfig.sgml">
-<!entity dropTSDictionary system "drop_tsdictionary.sgml">
-<!entity dropTSParser system "drop_tsparser.sgml">
-<!entity dropTSTemplate system "drop_tstemplate.sgml">
-<!entity dropType system "drop_type.sgml">
-<!entity dropUser system "drop_user.sgml">
-<!entity dropUserMapping system "drop_user_mapping.sgml">
-<!entity dropView system "drop_view.sgml">
-<!entity end system "end.sgml">
-<!entity execute system "execute.sgml">
-<!entity explain system "explain.sgml">
-<!entity fetch system "fetch.sgml">
-<!entity grant system "grant.sgml">
-<!entity insert system "insert.sgml">
-<!entity listen system "listen.sgml">
-<!entity load system "load.sgml">
-<!entity lock system "lock.sgml">
-<!entity move system "move.sgml">
-<!entity notify system "notify.sgml">
-<!entity prepare system "prepare.sgml">
-<!entity prepareTransaction system "prepare_transaction.sgml">
-<!entity reassignOwned system "reassign_owned.sgml">
-<!entity reindex system "reindex.sgml">
-<!entity releaseSavepoint system "release_savepoint.sgml">
-<!entity reset system "reset.sgml">
-<!entity revoke system "revoke.sgml">
-<!entity rollback system "rollback.sgml">
-<!entity rollbackPrepared system "rollback_prepared.sgml">
-<!entity rollbackTo system "rollback_to.sgml">
-<!entity savepoint system "savepoint.sgml">
-<!entity securityLabel system "security_label.sgml">
-<!entity select system "select.sgml">
-<!entity selectInto system "select_into.sgml">
-<!entity set system "set.sgml">
-<!entity setConstraints system "set_constraints.sgml">
-<!entity setRole system "set_role.sgml">
-<!entity setSessionAuth system "set_session_auth.sgml">
-<!entity setTransaction system "set_transaction.sgml">
-<!entity show system "show.sgml">
-<!entity startTransaction system "start_transaction.sgml">
-<!entity truncate system "truncate.sgml">
-<!entity unlisten system "unlisten.sgml">
-<!entity update system "update.sgml">
-<!entity vacuum system "vacuum.sgml">
-<!entity values system "values.sgml">
+<!ENTITY abort SYSTEM "abort.sgml">
+<!ENTITY alterAggregate SYSTEM "alter_aggregate.sgml">
+<!ENTITY alterCollation SYSTEM "alter_collation.sgml">
+<!ENTITY alterConversion SYSTEM "alter_conversion.sgml">
+<!ENTITY alterDatabase SYSTEM "alter_database.sgml">
+<!ENTITY alterDefaultPrivileges SYSTEM "alter_default_privileges.sgml">
+<!ENTITY alterDomain SYSTEM "alter_domain.sgml">
+<!ENTITY alterExtension SYSTEM "alter_extension.sgml">
+<!ENTITY alterForeignDataWrapper SYSTEM "alter_foreign_data_wrapper.sgml">
+<!ENTITY alterForeignTable SYSTEM "alter_foreign_table.sgml">
+<!ENTITY alterFunction SYSTEM "alter_function.sgml">
+<!ENTITY alterGroup SYSTEM "alter_group.sgml">
+<!ENTITY alterIndex SYSTEM "alter_index.sgml">
+<!ENTITY alterLanguage SYSTEM "alter_language.sgml">
+<!ENTITY alterLargeObject SYSTEM "alter_large_object.sgml">
+<!ENTITY alterOperator SYSTEM "alter_operator.sgml">
+<!ENTITY alterOperatorClass SYSTEM "alter_opclass.sgml">
+<!ENTITY alterOperatorFamily SYSTEM "alter_opfamily.sgml">
+<!ENTITY alterRole SYSTEM "alter_role.sgml">
+<!ENTITY alterSchema SYSTEM "alter_schema.sgml">
+<!ENTITY alterServer SYSTEM "alter_server.sgml">
+<!ENTITY alterSequence SYSTEM "alter_sequence.sgml">
+<!ENTITY alterTable SYSTEM "alter_table.sgml">
+<!ENTITY alterTableSpace SYSTEM "alter_tablespace.sgml">
+<!ENTITY alterTSConfig SYSTEM "alter_tsconfig.sgml">
+<!ENTITY alterTSDictionary SYSTEM "alter_tsdictionary.sgml">
+<!ENTITY alterTSParser SYSTEM "alter_tsparser.sgml">
+<!ENTITY alterTSTemplate SYSTEM "alter_tstemplate.sgml">
+<!ENTITY alterTrigger SYSTEM "alter_trigger.sgml">
+<!ENTITY alterType SYSTEM "alter_type.sgml">
+<!ENTITY alterUser SYSTEM "alter_user.sgml">
+<!ENTITY alterUserMapping SYSTEM "alter_user_mapping.sgml">
+<!ENTITY alterView SYSTEM "alter_view.sgml">
+<!ENTITY analyze SYSTEM "analyze.sgml">
+<!ENTITY begin SYSTEM "begin.sgml">
+<!ENTITY checkpoint SYSTEM "checkpoint.sgml">
+<!ENTITY close SYSTEM "close.sgml">
+<!ENTITY cluster SYSTEM "cluster.sgml">
+<!ENTITY commentOn SYSTEM "comment.sgml">
+<!ENTITY commit SYSTEM "commit.sgml">
+<!ENTITY commitPrepared SYSTEM "commit_prepared.sgml">
+<!ENTITY copyTable SYSTEM "copy.sgml">
+<!ENTITY createAggregate SYSTEM "create_aggregate.sgml">
+<!ENTITY createCast SYSTEM "create_cast.sgml">
+<!ENTITY createCollation SYSTEM "create_collation.sgml">
+<!ENTITY createConversion SYSTEM "create_conversion.sgml">
+<!ENTITY createDatabase SYSTEM "create_database.sgml">
+<!ENTITY createDomain SYSTEM "create_domain.sgml">
+<!ENTITY createExtension SYSTEM "create_extension.sgml">
+<!ENTITY createForeignDataWrapper SYSTEM "create_foreign_data_wrapper.sgml">
+<!ENTITY createForeignTable SYSTEM "create_foreign_table.sgml">
+<!ENTITY createFunction SYSTEM "create_function.sgml">
+<!ENTITY createGroup SYSTEM "create_group.sgml">
+<!ENTITY createIndex SYSTEM "create_index.sgml">
+<!ENTITY createLanguage SYSTEM "create_language.sgml">
+<!ENTITY createOperator SYSTEM "create_operator.sgml">
+<!ENTITY createOperatorClass SYSTEM "create_opclass.sgml">
+<!ENTITY createOperatorFamily SYSTEM "create_opfamily.sgml">
+<!ENTITY createRole SYSTEM "create_role.sgml">
+<!ENTITY createRule SYSTEM "create_rule.sgml">
+<!ENTITY createSchema SYSTEM "create_schema.sgml">
+<!ENTITY createSequence SYSTEM "create_sequence.sgml">
+<!ENTITY createServer SYSTEM "create_server.sgml">
+<!ENTITY createTable SYSTEM "create_table.sgml">
+<!ENTITY createTableAs SYSTEM "create_table_as.sgml">
+<!ENTITY createTableSpace SYSTEM "create_tablespace.sgml">
+<!ENTITY createTrigger SYSTEM "create_trigger.sgml">
+<!ENTITY createTSConfig SYSTEM "create_tsconfig.sgml">
+<!ENTITY createTSDictionary SYSTEM "create_tsdictionary.sgml">
+<!ENTITY createTSParser SYSTEM "create_tsparser.sgml">
+<!ENTITY createTSTemplate SYSTEM "create_tstemplate.sgml">
+<!ENTITY createType SYSTEM "create_type.sgml">
+<!ENTITY createUser SYSTEM "create_user.sgml">
+<!ENTITY createUserMapping SYSTEM "create_user_mapping.sgml">
+<!ENTITY createView SYSTEM "create_view.sgml">
+<!ENTITY deallocate SYSTEM "deallocate.sgml">
+<!ENTITY declare SYSTEM "declare.sgml">
+<!ENTITY delete SYSTEM "delete.sgml">
+<!ENTITY discard SYSTEM "discard.sgml">
+<!ENTITY do SYSTEM "do.sgml">
+<!ENTITY dropAggregate SYSTEM "drop_aggregate.sgml">
+<!ENTITY dropCast SYSTEM "drop_cast.sgml">
+<!ENTITY dropCollation SYSTEM "drop_collation.sgml">
+<!ENTITY dropConversion SYSTEM "drop_conversion.sgml">
+<!ENTITY dropDatabase SYSTEM "drop_database.sgml">
+<!ENTITY dropDomain SYSTEM "drop_domain.sgml">
+<!ENTITY dropExtension SYSTEM "drop_extension.sgml">
+<!ENTITY dropForeignDataWrapper SYSTEM "drop_foreign_data_wrapper.sgml">
+<!ENTITY dropForeignTable SYSTEM "drop_foreign_table.sgml">
+<!ENTITY dropFunction SYSTEM "drop_function.sgml">
+<!ENTITY dropGroup SYSTEM "drop_group.sgml">
+<!ENTITY dropIndex SYSTEM "drop_index.sgml">
+<!ENTITY dropLanguage SYSTEM "drop_language.sgml">
+<!ENTITY dropOperator SYSTEM "drop_operator.sgml">
+<!ENTITY dropOperatorClass SYSTEM "drop_opclass.sgml">
+<!ENTITY dropOperatorFamily SYSTEM "drop_opfamily.sgml">
+<!ENTITY dropOwned SYSTEM "drop_owned.sgml">
+<!ENTITY dropRole SYSTEM "drop_role.sgml">
+<!ENTITY dropRule SYSTEM "drop_rule.sgml">
+<!ENTITY dropSchema SYSTEM "drop_schema.sgml">
+<!ENTITY dropSequence SYSTEM "drop_sequence.sgml">
+<!ENTITY dropServer SYSTEM "drop_server.sgml">
+<!ENTITY dropTable SYSTEM "drop_table.sgml">
+<!ENTITY dropTableSpace SYSTEM "drop_tablespace.sgml">
+<!ENTITY dropTrigger SYSTEM "drop_trigger.sgml">
+<!ENTITY dropTSConfig SYSTEM "drop_tsconfig.sgml">
+<!ENTITY dropTSDictionary SYSTEM "drop_tsdictionary.sgml">
+<!ENTITY dropTSParser SYSTEM "drop_tsparser.sgml">
+<!ENTITY dropTSTemplate SYSTEM "drop_tstemplate.sgml">
+<!ENTITY dropType SYSTEM "drop_type.sgml">
+<!ENTITY dropUser SYSTEM "drop_user.sgml">
+<!ENTITY dropUserMapping SYSTEM "drop_user_mapping.sgml">
+<!ENTITY dropView SYSTEM "drop_view.sgml">
+<!ENTITY end SYSTEM "end.sgml">
+<!ENTITY execute SYSTEM "execute.sgml">
+<!ENTITY explain SYSTEM "explain.sgml">
+<!ENTITY fetch SYSTEM "fetch.sgml">
+<!ENTITY grant SYSTEM "grant.sgml">
+<!ENTITY insert SYSTEM "insert.sgml">
+<!ENTITY listen SYSTEM "listen.sgml">
+<!ENTITY load SYSTEM "load.sgml">
+<!ENTITY lock SYSTEM "lock.sgml">
+<!ENTITY move SYSTEM "move.sgml">
+<!ENTITY notify SYSTEM "notify.sgml">
+<!ENTITY prepare SYSTEM "prepare.sgml">
+<!ENTITY prepareTransaction SYSTEM "prepare_transaction.sgml">
+<!ENTITY reassignOwned SYSTEM "reassign_owned.sgml">
+<!ENTITY reindex SYSTEM "reindex.sgml">
+<!ENTITY releaseSavepoint SYSTEM "release_savepoint.sgml">
+<!ENTITY reset SYSTEM "reset.sgml">
+<!ENTITY revoke SYSTEM "revoke.sgml">
+<!ENTITY rollback SYSTEM "rollback.sgml">
+<!ENTITY rollbackPrepared SYSTEM "rollback_prepared.sgml">
+<!ENTITY rollbackTo SYSTEM "rollback_to.sgml">
+<!ENTITY savepoint SYSTEM "savepoint.sgml">
+<!ENTITY securityLabel SYSTEM "security_label.sgml">
+<!ENTITY select SYSTEM "select.sgml">
+<!ENTITY selectInto SYSTEM "select_into.sgml">
+<!ENTITY set SYSTEM "set.sgml">
+<!ENTITY setConstraints SYSTEM "set_constraints.sgml">
+<!ENTITY setRole SYSTEM "set_role.sgml">
+<!ENTITY setSessionAuth SYSTEM "set_session_auth.sgml">
+<!ENTITY setTransaction SYSTEM "set_transaction.sgml">
+<!ENTITY show SYSTEM "show.sgml">
+<!ENTITY startTransaction SYSTEM "start_transaction.sgml">
+<!ENTITY truncate SYSTEM "truncate.sgml">
+<!ENTITY unlisten SYSTEM "unlisten.sgml">
+<!ENTITY update SYSTEM "update.sgml">
+<!ENTITY vacuum SYSTEM "vacuum.sgml">
+<!ENTITY values SYSTEM "values.sgml">
<!-- applications and utilities -->
-<!entity clusterdb system "clusterdb.sgml">
-<!entity createdb system "createdb.sgml">
-<!entity createlang system "createlang.sgml">
-<!entity createuser system "createuser.sgml">
-<!entity dropdb system "dropdb.sgml">
-<!entity droplang system "droplang.sgml">
-<!entity dropuser system "dropuser.sgml">
-<!entity ecpgRef system "ecpg-ref.sgml">
-<!entity initdb system "initdb.sgml">
-<!entity pgBasebackup system "pg_basebackup.sgml">
-<!entity pgConfig system "pg_config-ref.sgml">
-<!entity pgControldata system "pg_controldata.sgml">
-<!entity pgCtl system "pg_ctl-ref.sgml">
-<!entity pgDump system "pg_dump.sgml">
-<!entity pgDumpall system "pg_dumpall.sgml">
-<!entity pgResetxlog system "pg_resetxlog.sgml">
-<!entity pgRestore system "pg_restore.sgml">
-<!entity postgres system "postgres-ref.sgml">
-<!entity postmaster system "postmaster.sgml">
-<!entity psqlRef system "psql-ref.sgml">
-<!entity reindexdb system "reindexdb.sgml">
-<!entity vacuumdb system "vacuumdb.sgml">
+<!ENTITY clusterdb SYSTEM "clusterdb.sgml">
+<!ENTITY createdb SYSTEM "createdb.sgml">
+<!ENTITY createlang SYSTEM "createlang.sgml">
+<!ENTITY createuser SYSTEM "createuser.sgml">
+<!ENTITY dropdb SYSTEM "dropdb.sgml">
+<!ENTITY droplang SYSTEM "droplang.sgml">
+<!ENTITY dropuser SYSTEM "dropuser.sgml">
+<!ENTITY ecpgRef SYSTEM "ecpg-ref.sgml">
+<!ENTITY initdb SYSTEM "initdb.sgml">
+<!ENTITY pgBasebackup SYSTEM "pg_basebackup.sgml">
+<!ENTITY pgConfig SYSTEM "pg_config-ref.sgml">
+<!ENTITY pgControldata SYSTEM "pg_controldata.sgml">
+<!ENTITY pgCtl SYSTEM "pg_ctl-ref.sgml">
+<!ENTITY pgDump SYSTEM "pg_dump.sgml">
+<!ENTITY pgDumpall SYSTEM "pg_dumpall.sgml">
+<!ENTITY pgResetxlog SYSTEM "pg_resetxlog.sgml">
+<!ENTITY pgRestore SYSTEM "pg_restore.sgml">
+<!ENTITY postgres SYSTEM "postgres-ref.sgml">
+<!ENTITY postmaster SYSTEM "postmaster.sgml">
+<!ENTITY psqlRef SYSTEM "psql-ref.sgml">
+<!ENTITY reindexdb SYSTEM "reindexdb.sgml">
+<!ENTITY vacuumdb SYSTEM "vacuumdb.sgml">
diff --git a/doc/src/sgml/standalone-install.sgml b/doc/src/sgml/standalone-install.sgml
index 87f9779..c94b397 100644
--- a/doc/src/sgml/standalone-install.sgml
+++ b/doc/src/sgml/standalone-install.sgml
@@ -21,7 +21,7 @@ Running 'make INSTALL' in the doc/src/sgml directory will do 1 through
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
-<!entity % version SYSTEM "version.sgml">
+<!ENTITY % version SYSTEM "version.sgml">
%version;
<!--
@@ -32,8 +32,8 @@ equivalent of C's #ifdef and friends. The other end of this is in
installation.sgml.
-->
- <!entity % standalone-ignore "IGNORE">
- <!entity % standalone-include "INCLUDE">
+ <!ENTITY % standalone-ignore "IGNORE">
+ <!ENTITY % standalone-include "INCLUDE">
<!--
When you're building the full documentation set, you want to flip the
On Mon, Apr 4, 2011 at 5:11 AM, Gabriele Bartolini
<gabriele.bartolini@2ndquadrant.it> wrote:
I have made very small modifications to a few files in the documentation
directory, which involve SGML entity declarations. Currently they are all
written lowercase, the patch makes them uppercase. This won't affect SGML
parsing, as SGML is case insensitive - even though it is a good practice to
write SGML declarations in uppercase.An example is:
<!entity abort system "abort.sgml">
written
<!ENTITY abort SYSTEM "abort.sgml">
This patch makes also every single directive of them XML compliant.
Forgive me for asking what may seem like a stupid question, but what's
not XML compliant about them now, and why do we care? The text is
only ever going to parse as SGML (not XML) so I guess I don't see why
it matters. I don't really object to the proposed patch but I guess
I'm not sure what it accomplishes.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it> writes:
I have made very small modifications to a few files in the
documentation directory, which involve SGML entity declarations.
Currently they are all written lowercase, the patch makes them
uppercase. This won't affect SGML parsing, as SGML is case insensitive -
even though it is a good practice to write SGML declarations in uppercase.
What's the point of this exactly? I don't think we'd accept changing
every tag in the documentation to upper case, so why should we change
a small subset of them?
regards, tom lane
Hi Robert (and Tom),
Il 04/04/11 16:57, Robert Haas ha scritto:
Forgive me for asking what may seem like a stupid question, but what's
not XML compliant about them now, and why do we care? The text is
only ever going to parse as SGML (not XML) so I guess I don't see why
it matters. I don't really object to the proposed patch but I guess
I'm not sure what it accomplishes.
My apologies, I should have explained it better and at once.
Here is the context. I am coordinating the Italian translation of the
documentation and we are about to create a branch for 9.1. The
publishing mechanism is based on DocBook XML (as well as the French
one), as we are facing extreme difficulties publishing using SGML tools.
My intention was to start and change some simple documentation files in
order to make our conversion process from SGML to XML smoother, while
keeping the SGML compatibility of the original documentation intact.
Also I was trying to make the ENTITY declarations consistent throughout
the documents.
I hope I gave you a more clear explanation.
Cheers,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
Gabriele Bartolini <gabriele.bartolini@2ndQuadrant.it> writes:
My intention was to start and change some simple documentation files in
order to make our conversion process from SGML to XML smoother, while
keeping the SGML compatibility of the original documentation intact.
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie, <foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?
regards, tom lane
Il 04/04/11 18:37, Tom Lane ha scritto:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,<foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?
We do it. However, given that the files that have been changed are
edited very rarely, the scope of the patch is limited and compatibility
with SGML is kept, I thought changing this at source level would be
something to propose and submit.
Ciao,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
On 04.04.2011 18:37, Tom Lane wrote:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,<foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?
Tom,
Honestly, for German I don't mind yet if it is XML or SGML. XML might
be better in future for maintenance tools.
Anyway, I figured out there is another argument for XML:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
Susanne
P.S.:
Btw. I change <foo>whatever</> into <foo>whatever</foo> when it
is in the parts which I am translating because my emacs indent don't
like </>.
--
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
www.2ndQuadrant.com
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht <susanne@2ndquadrant.com> wrote:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
Ouch.
Even if that doesn't turn out to be the case, this is pretty harmless,
so maybe we should just apply it and move on.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Robert Haas <robertmhaas@gmail.com> writes:
Even if that doesn't turn out to be the case, this is pretty harmless,
so maybe we should just apply it and move on.
I have no great objection to the patch as such; just wondering what the
roadmap is.
regards, tom lane
On Mon, Apr 4, 2011 at 2:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Robert Haas <robertmhaas@gmail.com> writes:
Even if that doesn't turn out to be the case, this is pretty harmless,
so maybe we should just apply it and move on.I have no great objection to the patch as such; just wondering what the
roadmap is.
Me, too.
On a practical level, if we're going to do this, shouldn't we also do
!entity -> !ENTITY in Solution.pm?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht <susanne@2ndquadrant.com> wrote:
Anyway, I figured out there is another argument for XML:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
Yes, indeed.
I don't think that during the 9.1 alpha phase is the right time to
think about this, but this certainly seems appropriate to consider as
a 9.2 "ToDo" item.
There are arguments as to why to switch to version 5, which is,
indeed, XML-only.
http://www.docbook.org/tdg5/en/html/ch01.html#introduction-why-to-switch
They argue that version 5
- Is what will get fixes. Which may not matter to us, as I don't
think we have been getting bitten by "horrible DocBook problems."
- Has new functionality. Which may not matter, as we're doubtless not
using all of the functionality of elder versions of DocBook either.
- Is more extensible. Which I imagine doesn't matter, as we weren't
extending earlier versions.
- Is easier to customize. Almost anything would be better than
DSSSL... (http://www.biglist.com/lists/dssslist/archives/200005/msg00120.html
is my little contribution that apparently got used a fair bit by
people)
There is also a possible counter-position to be taken, namely that the
existing tooling works, is mature, and isn't too likely to disappear
in any sort of short term.
In any case, the ToDo shouldn't be about how to convert the SGML to
XML - that's merely one of the tasks. There is already a ToDo item,
which points here:
<http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php>
It needs to cover making sure such things as that:
a) The output forms presently used (e.g. - PDF, man pages, perhaps
.chm/.rtf) continue to be available
b) We can clearly document what new toolchain is needed to process the
various output forms, and validate that it's sufficiently free,
sufficiently robust, sufficiently portable, and so forth.
c) Integrating the toolchain into the Postgres build process.
This represents a fair bit of work, so it's a bit of a presumption
that it's a wise move to do this in 9.2. I don't think the benefits
that the DocBook folk present for moving to v5 are necessarily
compelling to the Postgres community.
BTW, I wear most of the "DocBook hat" for the Slony project, and I
don't see it being valuable to us ("Slony project") to migrate to v5.
It would require quite a bit of work, and I don't see any of the
claimed benefits being helpful to the "Slony us."
--
http://linuxfinances.info/info/linuxdistributions.html
On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne <cbbrowne@gmail.com> wrote:
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht <susanne@2ndquadrant.com> wrote:
Anyway, I figured out there is another argument for XML:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
Yes, indeed.
I don't think that during the 9.1 alpha phase is the right time to
think about this, but this certainly seems appropriate to consider as
a 9.2 "ToDo" item.There are arguments as to why to switch to version 5, which is,
indeed, XML-only.
http://www.docbook.org/tdg5/en/html/ch01.html#introduction-why-to-switch
AFAICT, the biggest problem with our existing toolchain is that it's
hard for some people to get it working. In theory, we have
documentation that explains this:
http://www.postgresql.org/docs/current/static/docguide-toolsets.html
However, in contrast to the vast majority of our documentation, it stinks.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Robert Haas <robertmhaas@gmail.com> writes:
On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne <cbbrowne@gmail.com> wrote:
There are arguments as to why to switch to version 5, which is,
indeed, XML-only.
http://www.docbook.org/tdg5/en/html/ch01.html#introduction-why-to-switch
AFAICT, the biggest problem with our existing toolchain is that it's
hard for some people to get it working.
Indeed. One thing I'd like to know is whether docbook v5 is any more
portable/easier to install.
regards, tom lane
On 4/4/11, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Apr 4, 2011 at 2:50 PM, Christopher Browne <cbbrowne@gmail.com>
wrote:On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht <susanne@2ndquadrant.com>
wrote:Anyway, I figured out there is another argument for XML:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
Yes, indeed.
I don't think that during the 9.1 alpha phase is the right time to
think about this, but this certainly seems appropriate to consider as
a 9.2 "ToDo" item.There are arguments as to why to switch to version 5, which is,
indeed, XML-only.
http://www.docbook.org/tdg5/en/html/ch01.html#introduction-why-to-switchAFAICT, the biggest problem with our existing toolchain is that it's
hard for some people to get it working. In theory, we have
documentation that explains this:http://www.postgresql.org/docs/current/static/docguide-toolsets.html
However, in contrast to the vast majority of our documentation, it stinks.
I've certainly wasted non-trivial amounts of time trying to get it to
work on some platforms. I'd be *very* glad to see us using a
simplified toolchain if possible.
Another point to note is that whilst it will still be possible to
install older versions of docbook for a while, presumably that'll
become more and more of a pain, as distros update to 5.x, requiring
users to start building manually, and having to deal with parallel
installations of two versions.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On 04.04.2011 21:08, Tom Lane wrote:
Indeed. One thing I'd like to know is whether docbook v5 is any more
portable/easier to install
Unfortunately, as far as I know - there isn't a huge difference.
regards,
Susanne
--
Susanne Ebrecht - 2ndQuadrant
PostgreSQL Development, 24x7 Support, Training and Services
www.2ndQuadrant.com
Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400 2011:
Il 04/04/11 18:37, Tom Lane ha scritto:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,<foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?We do it. However, given that the files that have been changed are
edited very rarely, the scope of the patch is limited and compatibility
with SGML is kept, I thought changing this at source level would be
something to propose and submit.
Given the lack of objections, I have pushed this patch. Thanks.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On Mon, Apr 4, 2011 at 4:15 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400 2011:
Il 04/04/11 18:37, Tom Lane ha scritto:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,<foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?We do it. However, given that the files that have been changed are
edited very rarely, the scope of the patch is limited and compatibility
with SGML is kept, I thought changing this at source level would be
something to propose and submit.Given the lack of objections, I have pushed this patch. Thanks.
I think you still need to update Solution.pm to match.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Excerpts from Robert Haas's message of lun abr 04 16:26:07 -0400 2011:
On Mon, Apr 4, 2011 at 4:15 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:Excerpts from Gabriele Bartolini's message of lun abr 04 13:18:21 -0400 2011:
Il 04/04/11 18:37, Tom Lane ha scritto:
AFAIK, the main stumbling block for that is that XML doesn't allow
abbreviated close tags (ie,<foo>whatever</>). Which is something that
we are not likely to give up. So I'm not sure of the point of changing
something as trivial as entity declaration casing. You're going to end
up having to fork the documentation anyway, or at least feed it through
an SGML to XML converter. So why not fix the entity casing then?We do it. However, given that the files that have been changed are
edited very rarely, the scope of the patch is limited and compatibility
with SGML is kept, I thought changing this at source level would be
something to propose and submit.Given the lack of objections, I have pushed this patch. Thanks.
I think you still need to update Solution.pm to match.
Oops, sorry, done.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Il 04/04/11 22:26, Robert Haas ha scritto:
I think you still need to update Solution.pm to match.
Here it is, including change of 3 'Id' attributes (I made them lowercase).
Thanks,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
Attachments:
uppercase-sgml-entity-declarations-2.patchtext/plain; name=uppercase-sgml-entity-declarations-2.patch; x-mac-creator=0; x-mac-type=0Download
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index bb5527c..9266558 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,6 +1,6 @@
<!-- doc/src/sgml/config.sgml -->
-<chapter Id="runtime-config">
+<chapter id="runtime-config">
<title>Server Configuration</title>
<indexterm>
diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml
index 7f515dc..144b880 100644
--- a/doc/src/sgml/recovery-config.sgml
+++ b/doc/src/sgml/recovery-config.sgml
@@ -1,6 +1,6 @@
<!-- doc/src/sgml/recovery-config.sgml -->
-<chapter Id="recovery-config">
+<chapter id="recovery-config">
<title>Recovery Configuration</title>
<indexterm>
diff --git a/doc/src/sgml/typeconv.sgml b/doc/src/sgml/typeconv.sgml
index 71ddc0f..f233e9d 100644
--- a/doc/src/sgml/typeconv.sgml
+++ b/doc/src/sgml/typeconv.sgml
@@ -1,6 +1,6 @@
<!-- doc/src/sgml/typeconv.sgml -->
-<chapter Id="typeconv">
+<chapter id="typeconv">
<title>Type Conversion</title>
<indexterm zone="typeconv">
diff --git a/src/tools/msvc/Solution.pm b/src/tools/msvc/Solution.pm
index e1fe4e9..1a7b94d 100644
--- a/src/tools/msvc/Solution.pm
+++ b/src/tools/msvc/Solution.pm
@@ -389,8 +389,8 @@ EOF
open(O, ">doc/src/sgml/version.sgml") || croak "Could not write to version.sgml\n";
print O <<EOF;
-<!entity version "$self->{strver}">
-<!entity majorversion "$self->{majorver}">
+<!ENTITY version "$self->{strver}">
+<!ENTITY majorversion "$self->{majorver}">
EOF
close(O);
}
On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
AFAICT, the biggest problem with our existing toolchain is that it's
hard for some people to get it working. In theory, we have
documentation that explains this:http://www.postgresql.org/docs/current/static/docguide-toolsets.html
However, in contrast to the vast majority of our documentation, it
stinks.
Umm, if you look under "Debian Packages", there is a one-line command to
execute, which, as far as I can tell, is pretty much guaranteed to get
you going. If that doesn't apply to the OS you are working, then either
a) You haven't contributed better installation documentation, or
b) The makers of your OS haven't bothered to package it properly.
No other toolchain will make that principle easier.
On mån, 2011-04-04 at 15:08 -0400, Tom Lane wrote:
One thing I'd like to know is whether docbook v5 is any more
portable/easier to install.
I don't see why. It's just a newer version of the same thing.
If you change the sources to XML and switch to the XSL toolchain, you
don't have to install the DTD or other schema as such, which would
simplify the installation. But that could already be had with DocBook
4.
The drawback of not having the schema is that you can't verify the
correct structure of the document, and the XSLT processor will just
produce garbage.
Excerpts from Gabriele Bartolini's message of lun abr 04 16:47:26 -0400 2011:
Il 04/04/11 22:26, Robert Haas ha scritto:
I think you still need to update Solution.pm to match.
Here it is, including change of 3 'Id' attributes (I made them lowercase).
Pushed this one also.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
On mån, 2011-04-04 at 19:26 +0200, Susanne Ebrecht wrote:
Honestly, for German I don't mind yet if it is XML or SGML. XML might
be better in future for maintenance tools.Anyway, I figured out there is another argument for XML:
My information is that DocBook 5.0 won't support SGML anymore.
Which means - sooner or later a reaction is needed.
In the spirit of CVS_to_Git, I have started this page now:
http://wiki.postgresql.org/wiki/Switching_PostgreSQL_documentation_from_SGML_to_XML
Edit away.
On Tue, Apr 5, 2011 at 2:18 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
On mån, 2011-04-04 at 15:02 -0400, Robert Haas wrote:
AFAICT, the biggest problem with our existing toolchain is that it's
hard for some people to get it working. In theory, we have
documentation that explains this:http://www.postgresql.org/docs/current/static/docguide-toolsets.html
However, in contrast to the vast majority of our documentation, it
stinks.Umm, if you look under "Debian Packages", there is a one-line command to
execute, which, as far as I can tell, is pretty much guaranteed to get
you going. If that doesn't apply to the OS you are working, then eithera) You haven't contributed better installation documentation, or
b) The makers of your OS haven't bothered to package it properly.
No other toolchain will make that principle easier.
I don't know whether some other toolchain would be easier or not. I
believe that the directions for RPM installation aren't completely
up-to-date; I think you need docbook-style-dsssl at least on newer
Fedoras, and there isn't any stylesheet package on such systems.
There are also no directions for MacOS X at all. My biggest gripe is
that when things fail, it's often not obvious what the problem is.
I've had failures due to missing packages (but the package that's
missing is far from obvious) and I've also had failures, I believe,
from not being connected to the Internet, which is surprising because
it's not at all obvious that building the docs should require an
Internet connection. At least if you are missing something like zlib
it says "checking for zlib... not found". And while it may be that
you have zlib and are missing zlib-devel, it at least gets you pointed
in the right direction, whereas the docbook stuff tends to spew out 50
pages of error messages that I at least don't find terribly intuitive.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Tue, Apr 5, 2011 at 7:55 PM, Robert Haas <robertmhaas@gmail.com> wrote:
I've also had failures, I believe,
from not being connected to the Internet, which is surprising because
it's not at all obvious that building the docs should require an
Internet connection.
Oh, I've run into that and had it cause delays when I've been building
release installers before now (sourceforge were having issues iirc) -
not good.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
and I've also had failures, I believe,
from not being connected to the Internet, which is surprising because
it's not at all obvious that building the docs should require an
Internet connection.
I understand this problem, but just to clarify, this is supposed to
help, because then you don't need to install anything, as whatever is
necessary will be downloaded automatically. This is a feature of the
XSLT processor. In the case of xsltproc, it can be turned off with the
--nonet option.
On the other hand, if you have a proper local installation, then it
should map the Internet URIs to the local installation. -- "should"
On Tue, Apr 5, 2011 at 4:59 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
On tis, 2011-04-05 at 14:55 -0400, Robert Haas wrote:
and I've also had failures, I believe,
from not being connected to the Internet, which is surprising because
it's not at all obvious that building the docs should require an
Internet connection.I understand this problem, but just to clarify, this is supposed to
help, because then you don't need to install anything, as whatever is
necessary will be downloaded automatically. This is a feature of the
XSLT processor. In the case of xsltproc, it can be turned off with the
--nonet option.On the other hand, if you have a proper local installation, then it
should map the Internet URIs to the local installation. -- "should"
Well, that explains why it worked without a network connection on some
systems but not others. I don't really object to the toolchain we're
using; it works OK for me, and switching would be a pain in the neck.
But I find it's not as easy to use as some things.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas <robertmhaas@gmail.com> wrote:
In theory, we have
documentation that explains this:http://www.postgresql.org/docs/current/static/docguide-toolsets.html
While we're on the subject..
Attached is a patch against that page suggesting using openjade 1.3,
not 1.4devel as part of the doc build toolset. Source of this
recommendation:
<http://old.nabble.com/openjade-segfault-on-Postgres-PDF%3A-flow-object-not-accepted-by-port-to30764268.html>
I just double checked, and with the latest openjade package (1.4devel)
on Ubuntu 10.10, I still see the same segfault; downgrading to package
"openjade1.3" allows me to make postgres-A4.pdf successfully.
Josh
Attachments:
docguide_openjade.difftext/x-diff; charset=US-ASCII; name=docguide_openjade.diffDownload
diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml
index 7ec75a3..7bbe324 100644
*** a/doc/src/sgml/docguide.sgml
--- b/doc/src/sgml/docguide.sgml
*************** CATALOG "docbook/4.2/catalog"
*** 268,274 ****
available for <productname>Debian GNU/Linux</productname>.
To install, simply use:
<programlisting>
! apt-get install docbook docbook-dsssl docbook-xsl openjade xsltproc
</programlisting>
</para>
</sect2>
--- 268,274 ----
available for <productname>Debian GNU/Linux</productname>.
To install, simply use:
<programlisting>
! apt-get install docbook docbook-dsssl docbook-xsl openjade1.3 xsltproc
</programlisting>
</para>
</sect2>
*************** make install
*** 309,314 ****
--- 309,327 ----
installed and you want to install the rest of the toolchain
locally.)
</para>
+
+ <note>
+ <para>
+ Some users have reported encountering a segmentation fault using
+ openjade 1.4devel to build the PDFs, with a message like:
+ <screen>
+ openjade:./stylesheet.dsl:664:2:E: flow object not accepted by port; only display flow objects accepted
+ make: *** [postgres-A4.tex-pdf] Segmentation fault
+ </screen>
+ Downgrading to openjade 1.3 should get rid of this error.
+ </para>
+ </note>
+
</step>
<step id="doc-openjade-install">
On Tue, Apr 5, 2011 at 6:55 PM, Josh Kupershmidt <schmiddy@gmail.com> wrote:
On Mon, Apr 4, 2011 at 3:02 PM, Robert Haas <robertmhaas@gmail.com> wrote:
In theory, we have
documentation that explains this:http://www.postgresql.org/docs/current/static/docguide-toolsets.html
While we're on the subject..
Attached is a patch against that page suggesting using openjade 1.3,
not 1.4devel as part of the doc build toolset. Source of this
recommendation:
<http://old.nabble.com/openjade-segfault-on-Postgres-PDF%3A-flow-object-not-accepted-by-port-to30764268.html>I just double checked, and with the latest openjade package (1.4devel)
on Ubuntu 10.10, I still see the same segfault; downgrading to package
"openjade1.3" allows me to make postgres-A4.pdf successfully.
OK, committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company