Hi Bob, yes, that's what I was asking, but seeing it written out so plainly (and not fuzzily in my brain), it's looks like a silly question. I do *wish* I could hand over a single file when I need to share, but I guess it will have to be a zip and not a DB XML.
thanks, --Tim On Fri, Feb 3, 2012 at 11:53 AM, Bob Stayton <[email protected]> wrote: > Hi Tim, > Can you clarify this question: > > >> Is there any method I can use to create a valid DocBook XML file that >> doesn't require me to ship the external xhtml files? > > > Does this mean you want to insert into your document the edited xhtml code? > And then have that xhtml code output as working xhtml? > > Bob Stayton > Sagehill Enterprises > [email protected] > > > ----- Original Message ----- From: "Tim Arnold" <[email protected]> > To: "DocBook Apps" <[email protected]> > Sent: Thursday, February 02, 2012 7:18 AM > Subject: [docbook-apps] including xhtml questions > > >> Hi, >> I create DocBook 5 XML and use the html stylesheets to produce html. >> I also use the dbhtml file= processing instruction to insert some >> xhtml files that have been externally generated. Unfortunately I have >> no control over the external process and the xhtml contains >> entities and duplicate IDs. >> I have been postprocessing the files to remove these before running >> the DocBook html stylesheets (using a Python script). >> >> I'd rather not do that because >> (a) it adds another external step to the build process and >> (b) I have to include these modified xhtml files if I need to deliver >> the DocBook content to others. >> >> My questions: >> Is there any method I can use to create a valid DocBook XML file that >> doesn't require me to ship the external xhtml files? >> If not, then would it be better (maintenance, simplicity) to create a >> custom processing instruction to include these files instead of using >> Python? >> >> thanks, >> --Tim Arnold >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
