ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Prototype work on XML+XSL based Ant doc
Date Thu, 24 Mar 2005 07:28:40 GMT
On Tue, 22 Mar 2005, Dominique Devienne <> wrote:

> I have several questions I was hoping could be discussed.

I'm glad you bring the discussion over here since I find it easier to
respond to an email using my mail client than my browser.

> 1) First, is there a place for such a prototype somewhere? 
> proposals/ in CVS?

Why not.

> Wait for SVN/ant/sandbox?

I could ping infrastructure to create /repos/asf/ant and we can go
from there immediately.  Right now all almost all our infrastructure
people are busy with something they call infrathon, though.  After

> 2) Second, is the XML syntax I used too verbose?

No, I like it.

> Is what I used already good enough? Where to improve?

Let me echo Jan's wish for cross linking of tasks - both inside of
whatsnew and inside of the manual.

One thing that wasn't immediately clear to me was what the equivalent
of the <td rowspan="2">Exactly one of the two</td> cells we have in
the "required" column of some pages would be.

One thing that doesn't render well in Firefox is the since attribute
on the target and propertyset nested elements in ant.xml - I see the
&nbsp;s as text, i.e. Firefox seems to either escape the ampersand or
doesn't recognize it as entity.  I tried to change the output-method
to xhtml but Firefox doesn't recognize it.

> 3) Then, is DTD/Schema support important?

Not to me, YMMV.

> I'm basically trying to avoid this work going too much further if
> there's no buy in and support right at the start.

Understandable, see Kev's work of trying to lift stuff from HTML to

> So far we've mostly discussed options, but with this initial
> 'implementation', I'd rather get a feel whether it's a dead end or
> not.

I like it and don't think it would make autogeneration later any more
difficult than what we have right now.  Probably it would make it
easier since we'd have computable semantics in our docs.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message