On Thu, 2006-11-02 at 11:34, KP Kirchdoerfer wrote:
> Am Donnerstag, 2. November 2006 15:24 schrieb Mike Noyes:
> > On Thu, 2006-11-02 at 06:02, Mike Noyes wrote:
> > > On Mon, 2006-10-16 at 11:25, KP Kirchdoerfer wrote:
> > > > It's really hard to design and write doc's (esp. if one's native
> > > > language isn't english) - and a lot of people tried hard to provide
> > > > guides and howto's to alleviate the usage of LEAF appliances and to
> > > > teach new developers about the LEAF specifics.
> > > > But as the documentation page presents itself to the users today, all
> > > > of the work is nearly useless. Even die-hard LEAF users do have
> > > > difficulties to find the chapters they are interested in.
> > > > And it is discouraging to work on new docs, if they are buried in a
> > > > conglomerate of titles, subtitles and subsubtitles.
> > >
> > > I've posted numerous times mentioning the DocBook XSL guide. The last
> > > time was on Jul 04, 2006.
> > >
> > > DocBook XSL: The Complete Guide
> > > http://www.sagehill.net/docbookxsl/
> > >
> > > All the information on xsl customization of our docbook content
> > > presentation is in that guide.
> > >
> > > I haven't had time to generate a customization layer for us.
> >
> > KP,
> > My customization layer notes are in doc-build.sh.
> >
> > http://leaf.cvs.sourceforge.net/leaf/sourceforge/admin/doc-build.sh?revisio
> >n=1.13&view=markup
> >
> > The main issue is an inability to use.id.as.filename. Generic chunking
> > (file names like bk01ch01.html) wouldn't happen with ID attributes.
> >
> > ID recommended on section: ?????????
>
> Sorry Mike; I don't get it what you want to explain to me.
KP,
See the "Chunk filenames" section on the page linked below.
http://www.sagehill.net/docbookxsl/Chunking.html
"The chunk element's id attribute value (but only if the
use.id.as.filename parameter is set)."
Someone needs to add a unique ID attribute for each chunked section to
our docbook xml content in CVS. This will take quite a bit of time. It
is necessary for proper file name generation when processing XML with
XSL.
Note: duplicate ID attributes will cause validation failure.
> Is there something we as documentation writers can do have a reasonable
> representation of the contents?
Changing the xinclude content order, omitting content, etc. in
doc/leaf-doc-set.xml is the easiest partial solution. It should provide
some of the clarity you're looking for.
> Or is a change necessary by someone who understands to deal with xsl/xml?
Knowledge of DocBook XSL is necessary.
--
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
