Skip site navigation (1) Skip section navigation (2)

Re: Authoring Tools WAS: Switching to XML

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, David Fetter <david(at)fetter(dot)org>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Authoring Tools WAS: Switching to XML
Date: 2006-12-11 19:23:28
Message-ID: 1165865008.19970.56.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
> Can you show me an authoring tool that does *not* think it's OK to
> mangle the low-level text in "semantically irrelevant" ways?

No. :) I mentioned this previously. Any word processor is going to blow
stuff away in an ugly way. The closest we could get is:

Create a custom style in OpenOffice that works in a similar fashion to

Use Tidy and or a custom script to clean after the fact.

IMHO the only tools for Docbook that are usable are editors, preferrably
validating editors such as Emacs, Bluefish (actually Word Perfect does
this too). We are not going to get what we want out of WYSIWYG.

>   We might
> as well forget about the concept of a doc patch if people start using
> tools like this --- if a one-word change results in diffs across the
> whole file, the tool is not usable.

You are correct, we would have to run some kind of clean script and then
diff between the two versions.


Joshua D. Drake


      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997

Donate to the PostgreSQL Project:

In response to

pgsql-docs by date

Next:From: Josh BerkusDate: 2006-12-11 19:27:37
Subject: Re: Authoring Tools WAS: Switching to XML
Previous:From: Tom LaneDate: 2006-12-11 19:08:03
Subject: Re: Authoring Tools WAS: Switching to XML

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group