I think it is a matter of planning for the future.
Changing 10 pages of HTML may not be a big deal or
even a hundred, but as the site's documentation keeps
expanding it's easier to keep the documentation in XML
so Struts and other Jakarta projects can easily be
reformatted and released with a new look and feel with
minimal effort. Maybe there will be a version of the
site for hand held devices one day. With everything
in XML it would be feasible to do something like this.
I would just work on it in plain text as Ted
suggested so you can get something together without
being distracted and then worry about adding the tags.
David
--- Jonathan Asbell <[EMAIL PROTECTED]> wrote:
> Mike, I am forced to work with xslt every day, and
> each day I find a new
> reason to say "what in the WORLD do people see in
> this?!". It has its place
> in changing from schema to scema, but who want to
> get so deep into a
> technology which is very hard to control, and in
> complex schemas consumes
> more effort than it is worth to get what you want
> out of it.
>
> ----- Original Message -----
> From: "Michael Westbay" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 17, 2001 7:45 PM
> Subject: Re: The documentation, xml, and stylesheets
>
>
> > Jonathan-san wrote:
> >
> > > Yea, but now I will have to learn the dtd and
> create complex
> stylesheets.
> > > Gentlemen. if I may be frank, this is an
> excercise in technical
> > > masturbation. If I ever want to redo it
> all.....than I will.
> Stylesheets
> > > do not help, and those that have had to use them
> know exactly what I am
> > > talking about.
> >
> > I use them. And the more I use them, the more I
> like them. Just look at
> the
> > power behind the current Struts' documentation
> xml, namely DTD and the
> user
> > manuals for the tags get generated from a single
> XML file. The next
> logical
> > step is to have that XML file generated from
> JavaDoc, so that if the
> > specification of a tag changes, the change can
> easily be reflected in the
> DTD
> > and manual without having to edit external
> documents.
> >
> > I'm currently looking at the idea of creating
> pages in XML that generate
> JSP
> > pages (with Struts tags among others) and help
> HTML files. The help files
> > can also be processed with FOP for a PDF manual.
> One source, multiple
> > integrated, cross referenced outputs.
> >
> > No, it isn't easy. But for building a complex
> system where source and
> > documentation may be managed together, it's a very
> powerful tool.
> >
> > MS Word attachments and mail in HTML format (70%
> of the spam I recieve)
> get
> > filtered to /dev/null. I won't touch them. (Why
> does Outlook's HTML
> > messages take up to 32 times the plain text size?)
> In fact, lot of
> messages
> > got filtered the past couple of weeks since. Even
> though most of you have
> > HTML mail turned off, Outlook assumes that when
> replying to an HTML
> message,
> > you want to send in HTML format, too. Judging
> form the headers in my spam
> > log, I belive that Mozilla is equally guilty, so
> I'm not just picking on
> MS.
> >
> > Should proper mail netiquitte be included on the
> mail subscription page?
> The
> > FAQ that comes periodically in the DocBook mailing
> list spells out proper
> > quoting technique (snip-quote-reply) rather
> nicely, and establishes
> policies
> > for attachments and cross posting.
> >
> > --
> > Michael Westbay
> > Work: Beacon-IT http://www.beacon-it.co.jp/
> > Home:
> http://www.seaple.icc.ne.jp/~westbay
> > Commentary: http://www.japanesebaseball.com/
> >
>
__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/
