El Martes, 17 de Octubre de 2006 23:08, Dan Nicholson escribió:

>
> Maybe I'm in the minority, but I think that's a useful goal. To me, it
> seems like most of the editors are just following XSL convention
> anyway. I.e., in BLFS we're adding role="root" because somebody said
> to do it. If we were to start saying add role="install" and did the
> initial mass changeover, I don't think anyone would have too big a
> problem.

The basic problem is to develop the XML tags+attributes framework that would 
allow to extract the commands and packages info separated by type, without 
breaking validation and/or HTML/PDF output.

Then show it to all books editors and hope that they agree with implementing 
the changes.

The first point requires time to find a working and editor-friendly solution. 
The second point is an unknown variable and may depend on who and when the 
proposal is made.

> Could you point me to some XSL documentation? Maybe some newbie level
> stuff, too? This is my major stumbling block in mapping between book
> and build. You guys are doing kick ass work on jhalfs, but I think
> there's some lower level work that could be done to make it more
> powerful without requiring lots of workarounds at the higher level.

Well, I learn XSL/Xpath/Xpointer/CSS reading the W3C specifications and 
playing with the DocBook XSl code and books sources.

I don't have in my bookmarks links to XSL manuals, but a quick search sow this 
ones:

http://ils.unc.edu/~pottl/inls259/xml/xsl.html
http://www.quepublishing.com/articles/article.asp?p=26312&rl=1
http://publib.boulder.ibm.com/infocenter/wsphelp/topic/com.ibm.etools.xsl.source.doc/tasks/tcrtxsl.htm


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to