FW: Publishers stylesheet files

[Scott Hudson <scott.hudson@schneider-electric.com>]

Folks,

please try the attached stylesheets on our samples in sourceforge, as well
as any of your publishers content!

Please send any problems to the list and also to Bob Stayton.

Thanks and best regards,

--Scott

Scott Hudson |  Pelco by Schneider Electric | United States | Standards Lead
Site: pdn.pelco.com | scott.hudson@schneider-electric.com



------ Forwarded Message
From: Bob Stayton <bobs@sagehill.net>
Date: Fri, 24 Feb 2012 13:58:31 -0800
To: Scott Hudson <scott.hudson@schneider-electric.com>
Subject: Publishers stylesheet files

Here are the Publishers stylesheet files that Nic Gibson sent to me.  Let me
know if 
they are good enough to check in and add to the XSL distribution.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


----- Original Message -----
From: "Nic Gibson" <nicg@corbas.net>
To: "Bob Stayton" <bobs@sagehill.net>
Sent: Thursday, July 28, 2011 7:56 AM
Subject: Re: DocBook and XSLT and EPUBs


Hi Bob

I've split this into two files (one has the parameters) and I've included my
test 
driver file. I haven't copied all the code from the initial Penguin work
over but I'd 
appreciate a quick look over it to make sure I'm not doing anything that
makes 
integration additionally hard. I've spent a bit of today writing some code
to map from 
Dublin Core to DocBook metadata but it's not even beta ready yet.

EPUB and chunking - I'll take a look at the the variable - that will make
generating 
an OPF much simpler.

nic




----------------------------------------------------------------------------
----




On 28 Jul 2011, at 16:48, Bob Stayton wrote:

> Hi Nic,
> Yes, please send me what you have.
>
> Regarding the manifest, there already exists code for tracking the chunks. If
you 
> look in html/chunk-common.xsl, there is an xsl:variable named
'chunk.hierarchy' that
> gets computed when chunkfast is used.  It populates a tree of <cf:div>
elements that 
> capture the chunk hierarchy.  Just below that in the template named
> 'process-chunk-element' is an example of its usage.   I'll probably use that
in the 
> update I'm planning.
>
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
>
>
> ----- Original Message ----- From: "Nic Gibson" <nicg@corbas.net>
> To: "Bob Stayton" <bobs@sagehill.net>
> Sent: Wednesday, July 27, 2011 7:42 AM
> Subject: DocBook and XSLT and EPUBs
>
>
> Hi Bob
>
> I've done a fair bit of work on the DocBook Publishers XSLT getting it into a
shape 
> I'm happy to hand over. I'm just looking at changed content models - luckily
the 
> model for sidebar will (unless some publisher creates some very bizarre
content ) 
> work just fine. Could I send you some code for you to take a look over and see
if 
> there is anything you think I should do differently?
>
> As part of what I'm doing I'm looking at the set of XSLT and XProc code we are
using 
> (only in proof of concept work right now) at Penguin to generate our content.
I was 
> wondering if it might be worth exchanging ideas on those as you're going to be
> working on similar things for O'Reilly.  One of the issues that concerns me at
the 
> moment is the chunking - some way to generate the manifest for the EPUB based
on the 
> chunking code would be incredibly useful. Keith's current code hardcodes the
> elements that form the manifest which, well, worries me. Is there anything in
the 
> current HTML output (toc generation perhaps) that I could take a look at as a
> starting point?
>
> cheers
>
> nic
> --
> Nic Gibson
> Corbas Consulting
> Digital Publishing Consultancy and Training
> http://www.corbas.co.uk, +44 (0)7718 906817
>
>
>
>

Nic Gibson
Corbas Consulting
Digital Publishing Consultancy and Training
http://www.corbas.co.uk, +44 (0)7718 906817




______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

------ End of Forwarded Message

Attachment: docbook.xslt
Description: Binary data

Attachment: line-based.xslt
Description: Binary data

Attachment: param.xslt
Description: Binary data