Re: [docbook-apps] Website: Problem using olinks across websites

2008-04-10 Thread Denis Bradford
Following Bob's lead, I've tried to generate a website.database.xml that 
does not contain the offending document elements  - with no luck.


To simplify things, I built the example website that comes with the 
website 2.6 distribution, using the layout and build.xml ant file 
provided. Other than pointing at local resources, I only modified it by 
adding the last argument to this target:


==


  
  
  
  
  
  

Re: [docbook-apps] [SOT] CALS table model DTD - where to download?

2008-04-10 Thread Christian Roth
My apologies, I was completely misled by the content model definitions
in the DTD file 'calstblx.dtd' distributed with DocBook, thinking it is
a modified version already. It now appears from the comments in that
file that it actually *IS* the file I was looking for.

Sorry for the noise.

Christian


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[docbook-apps] [SOT] CALS table model DTD - where to download?

2008-04-10 Thread Christian Roth
Hello,

where did the DocBook developers get the basic CALS DTD file from before
they modified its defined entities for use within the DocBook DTD?

It seems like I just cannot find that "original" DTD file anywhere on
the web - either it's already the DocBook-modified version, or I end up
on OASIS's pages where they talk about it all over the place and are
having HTML-ified and annotated versions of what looks like the original
DTD file, but there's no place where I can download that pure file in itself!

If anyone has a link to it, that would be highly appreciated.

Christian



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[docbook-apps] table.cell.border.color not applied in HTML output

2008-04-10 Thread Xuan Ngo
table.cell.border.color doesn't applied in HTML output. However, it is 
displaying the expected
color in FO. The parameter exists in HTML as it is showing here
http://docbook.sourceforge.net/release/xsl/current/doc/html/table.cell.border.color.html.

Here is my common customization layer:

http://www.w3.org/1999/XSL/Transform"; version="1.0">
orange
 


Does someone know what I did wrong?

thx!
Xuan.


  __
Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo! 
Canada Messenger at http://ca.beta.messenger.yahoo.com/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [docbook-apps] ant and db5, xinclude and fo output

2008-04-10 Thread Samuel Wright
On Thu, Apr 10, 2008 at 2:20 PM, Johnson, Eric <[EMAIL PROTECTED]> wrote:
> one to resolve the xincludes then one to process the content. Since we are
> also using profiling that resulted in a three stage process (5 if we tagged
> on PDF processing).
>  It seemed easier and faster to use Saxon from the  command.

Separate passes certainly makes it a lot easier to figure out what is
wrong if something breaks in the publishing chain...

S

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [docbook-apps] ant and db5, xinclude and fo output

2008-04-10 Thread Johnson, Eric
When I was setting up our Ant based tool chain I could not find a way to get 
the Ant  task to support xinclude processing without doing two passes: 
one to resolve the xincludes then one to process the content. Since we are also 
using profiling that resulted in a three stage process (5 if we tagged on PDF 
processing).
It seemed easier and faster to use Saxon from the  command.


-Original Message-
From: Tony Graham [mailto:[EMAIL PROTECTED]
Sent: Thu 4/10/2008 8:46 AM
To: docbook-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] ant and db5, xinclude and fo output
 
On Thu, Apr 10 2008 11:36:06 +0100, [EMAIL PROTECTED] wrote:
> My latest foray into ant:
...
> 
> Generate the fo output
>fork="yes"
>   dir="${in.dir}"
>   failonerror="true">
>   
>line="-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration"/>
>line="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
>line="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"/>
> 
>   
>   
>   
>   
>   
> 
> 
>

The Ant manual [1] recommends  rather than .  Doing so needs more elements, but it's safer to use.

Why are you using the  task rather than the  task?  IMO,
using the  task makes using XML catalogs with Ant much easier.

You could also make a macro for the transformation so you wouldn't need
to repeat everything just to change three filenames.

...
> It might be nicer to use xmllint to expand the includes and validate,
> but I haven't figured out  how to get ant to do that.

 [2].

Regards,


Tony Graham [EMAIL PROTECTED]
Director  W3C XSL FO SG Invited Expert
Menteith Consulting Ltd
XML, XSL and XSLT consulting, programming and training
Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
Registered in Ireland - No. 428599   http://www.menteithconsulting.com
  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
xmlroff XSL Formatter   http://xmlroff.org
xslide Emacs mode  http://www.menteith.com/wiki/xslide
Unicode: A Primer   urn:isbn:0-7645-4625-2

[1] http://ant.apache.org/manual/using.html#arg
[2] http://ant.apache.org/manual/CoreTasks/exec.html
I don't know why it's showing as "beta" since it was in earlier
versions of Ant than the Ant 1.7 currently documented at this URL.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [docbook-apps] ant and db5, xinclude and fo output

2008-04-10 Thread Tony Graham
On Thu, Apr 10 2008 11:36:06 +0100, [EMAIL PROTECTED] wrote:
> My latest foray into ant:
...
> 
> Generate the fo output
>fork="yes"
>   dir="${in.dir}"
>   failonerror="true">
>   
>line="-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration"/>
>line="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
>line="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"/>
> 
>   
>   
>   
>   
>   
> 
> 
>

The Ant manual [1] recommends  rather than .  Doing so needs more elements, but it's safer to use.

Why are you using the  task rather than the  task?  IMO,
using the  task makes using XML catalogs with Ant much easier.

You could also make a macro for the transformation so you wouldn't need
to repeat everything just to change three filenames.

...
> It might be nicer to use xmllint to expand the includes and validate,
> but I haven't figured out  how to get ant to do that.

 [2].

Regards,


Tony Graham [EMAIL PROTECTED]
Director  W3C XSL FO SG Invited Expert
Menteith Consulting Ltd
XML, XSL and XSLT consulting, programming and training
Registered Office: 13 Kelly's Bay Beach, Skerries, Co. Dublin, Ireland
Registered in Ireland - No. 428599   http://www.menteithconsulting.com
  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --  --
xmlroff XSL Formatter   http://xmlroff.org
xslide Emacs mode  http://www.menteith.com/wiki/xslide
Unicode: A Primer   urn:isbn:0-7645-4625-2

[1] http://ant.apache.org/manual/using.html#arg
[2] http://ant.apache.org/manual/CoreTasks/exec.html
I don't know why it's showing as "beta" since it was in earlier
versions of Ant than the Ant 1.7 currently documented at this URL.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[docbook-apps] ant and db5, xinclude and fo output

2008-04-10 Thread Dave Pawson

My latest foray into ant:

Xinclude processing, fo output using xep.

 



   
   

  
   
 


   



 


  

 line="-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration"/>
  line="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
  line="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"/> 









  
  

  
  Finished at ${fintim}



And for the fo, both stages:


Generate the fo output

  
  line="-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration"/>
  line="-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"/>
  line="-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl"/>


  
  
  
  
  





 Generate the pdf in ${out.fo.dir}
cp is ${fo.processor.class}

  
  
 

  


  

Finished on ${fintim}




It might be nicer to use xmllint to expand the includes and validate,
but I haven't figured out  how to get ant to do that.

Real nasty if (as I did) you have
book
  chapter
  chapter
  section
where the chapters (and the section) were xincluded
Ouch :-) I'd forgotten to wrap the section in a chapter.
Docbook processes it and the fo processor blows up if it does a 
validation stage, as xep does.

  (Thanks RenderX)


HTH



regards

--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]