#2088: DocBook XSL Stylesheets-1.70.1
----------------------------------------+-----------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [EMAIL PROTECTED]
     Type:  task                        |       Status:  assigned               
   
 Priority:  normal                      |    Milestone:  future                 
   
Component:  BOOK                        |      Version:  SVN                    
   
 Severity:  normal                      |   Resolution:                         
   
 Keywords:  DocBook XSL Stylesheets     |  
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):

 Installation changes:

  - wordml must be added to the cp command

 Contents changes:

  - Replace the description of "Installed files" to something like "XSL
 style sheets for several output formats, including HTML and FO."


 Tested against current LFS-SVN I found this issues:

 HTML:

   Some headers are moved from H2 to H3 and from H3 to H4.

   In the Index, our customized "Packages", "Programs", etc. headers are
 replaced by
   "A", "B", etc.

   There is some warnings about sectX and table tags that don't have an ID.

 PDF:

   The "Table of Contents" header is lost.

   The same Index issue than in HTML.


 That issues aren't very hard to solve, but this XSL version includes a lot
 of new output customization params, most notably for FO, that may replace
 some of our current hacks. I would to rewritte our stylesheets based on
 1.70.1, making first a qick fix to can update ASAP the package in the BLFS
 pages.

 Due that we are very close to LFS and CLFS releases there is no time to me
 to migrate it to this new XSL version. Thus IMHO, BLFS-6.2 should be
 released also with 1.69.1.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/2088>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to