I have read the two long XML threads, and see these issues for
converting to XML:
o authoring, in two parts:
o WYSIWYG - this seems unattainable because such editors are
going to modify the surrounding XML, which will affect
hand-edited changes
o tag assistance - this seems possible, e.g. tag completion,
drop down list of tags available for this section
o output generation - the XML toolchain is more widely used, but Tom has
fixed the performance issue we have had for years. The fact that the
tool maintainers were unable to fix it themselves reflects badly on
their maintenance of this toolchain.
o translation - does XML have better tools to assist in translating our
manuals, and is this better than outputting XML via our makefile?
It would be nice to use htmltidy to clean up the xml before each
release, but I wonder whether it understand the tags well enough to
provide better formatting than we do now manually.
Tom, I think we need that SGML patch placed on our ftp site and a
reference to it made in our documentation. I can do it of you want.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
