On 1 Feb, Larry W. Virden wrote:
> The following would normally be reported via some sort of bug
> reporting, but I don't see a pointer to such a thing at
> http://www.tdom.org/ , so I will report here.

Since we haven't one: Please continue to report problems here.

> 1. In configure, change the word "wether" to "whether".

Changed. (Thanks! This sort of things slip thru for years, if nobody
reports them.)

> 2. In configure --help , the optional features section was a bit
> confusing. Some of the options list a default. Some list nothing, some
> list a --disable- type command, and some repeat the option. It was
> confusing to me what was going to be turned on and what was not.

Hm. All tDOM specific configure options noted the default value with
the configure option, which would have the same effect as the used
default.

The configure output always lists the choosen value. So, if in doubt,
a ../configure run without any options shows you the defaults:

...
checking whether to enable dtd support... yes
checking whether to enable namespace support... yes
checking whether to enable built-in unknown command... no
checking whether to enable tDOMs block allocator... yes
...


Anyway. I've changed the tdom m4 configure macros, to use the same
configure --help option documentation style, as it current TEA use -
with (default: on/off) at the end of the short option explanation,
where applicable.

rolf