[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Design Document XML resurrected (partial revert of r19836)

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2006-05-29 22:27:48 CEST

Karl Fogel wrote:
> Max Bowsher <maxb1@ukf.net> writes:
>> I've resurrected the Design Document XML on a temporary basis.
>>
>> My reason for doing this is that the current converted design.html
>> contains numerous errors in the markup - which there's really no reason
>> for, considering the source is a fully valid DocBook document.
>>
>> Therefore, it is my intention to construct some XSLT to perform the
>> conversion to HTML in a well defined and rigorous fashion.
>>
>> I have a mostly-working transformation already, by way of private
>> proof-of-concept. I'll tidy it up a little more, and commit it into the
>> doc/design directory. People can comment, and adjust the transformation
>> if necessary, then we can run it for a final time, replace the current
>> design.html with the XSLT-transformed one, and then delete doc/design again.
>
> Okay. I was just about to go hack on www/design.html to start
> bringing it up-to-date, but I'm happy to wait until you've committed a
> more rigorous one. Thanks for doing this the "right" way, Max; I
> don't know much about constructing XSLT translations and just Wanted
> It Done, but your way will be better.

Right - a new version of www/design.html is now in place.

Please review it, since it would be nice to make any possible changes
that can most easily be addressed by modifications to the XSLT before
manual edits are made to the HTML directly.

Once we're happy that we won't be needing to reconvert from the DocBook,
the doc/design directory can be deleted.

Once we are happy, I intend to make a sweep through design.html fixing
up the indentation - when I do so, should I work to a textwidth of 70,
72, or 79 ?

Max.

Received on Mon May 29 22:28:30 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.