DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint

[Vitaly Ostanin]

On Tue, 03 Dec 2002 09:19:19 -0600
Paul Grosso <[EMAIL PROTECTED]> wrote:



> >In modular set of docbook/xml after processing XInclude some
> >documents may to have duplicates of ID. 
> 
> True, and this would be a validation error.  The same is
> true if you used external parsed entities.  XInclude does
> nothing to solve the ID uniqueness problem.  
> 
> In particular, if you reuse the same chunk of XML in two places
> in the same document and any element therein contains an ID,
> you will end up with a document that is not valid (whether you
> use external parsed entities or XInclude).

You right. Thanks for the answer.



-- 
Regards, Vyt
mailto:  [EMAIL PROTECTED]
JID: [EMAIL PROTECTED]

Re: DOCBOOK-APPS: Attributes for figures

[Togan Muftuoglu]

* Bob Stayton; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:

On Tue, Dec 03, 2002 at 10:23:33PM +0200, Togan Muftuoglu wrote:
I cut and pasted the above into a customization layer, ran
xsltproc to generate the FO file using DocBook XSL 1.57.0,
and then ran FOP 0.20.4 on that and it worked.
Does your FO output include the 
element?  If not, then then XSLT stage is failing somehow.


The FO output does have the . I am using 1.58.1
with Saxon 6.5.2 . I'll try with  xsltproc and see if it makes a
difference 

--

Togan Muftuoglu

Re: DOCBOOK-APPS: XML catalog documentation

[Bob Stayton]

On Tue, Dec 03, 2002 at 12:30:29PM +0100, Jeanson Mauritz wrote:
> > -Original Message-
> > From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, November 11, 2002 10:44 AM
> > To: [EMAIL PROTECTED]
> > Subject: DOCBOOK-APPS: XML catalog documentation
> > 
> > 
> > I've rewritten my chapter on using XML catalogs with
> > DocBook XSL so that it is more complete and accurate.  It
> > is available at
> > 
> > http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> > 
> > Comments welcome.
> 
> Regarding the Xalan command line example:
> 
> I can't prevent Xalan from trying to go out on the web. This means it 
> doesn't work when I'm offline. The log looks like this: 
> 
> Parse catalog: catalog.xml
> Loading catalog: catalog.xml
> Default BASE: file:/C:/XMLtest/catalogs/test/Xalan/catalog.xml
> uri: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
>   file:///c:/doctypes/docbook/xsl/html/docbook.xsl
> URI: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
>   file:/c:/doctypes/docbook/xsl/html/docbook.xsl
> rewriteURI: http://docbook.sourceforge.net/release/xsl/current/
>   file:///c:/doctypes/docbook/xsl/
> REWRITE_URI: http://docbook.sourceforge.net/release/xsl/current/
>   file:/c:/doctypes/docbook/xsl/
> 
> (Location of error unknown)XSLT Error (javax.xml.transform.TransformerConfigurat
> ionException): javax.xml.transform.TransformerException: java.net.ConnectExcepti
> on: Connection refused: connect
> 
> The catalog file:
>  
>xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
>   
>  name="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl";
>   uri="file:///c:/doctypes/docbook/xsl/html/docbook.xsl"/> 
>   
>uriStartString="http://docbook.sourceforge.net/release/xsl/current/";
> rewritePrefix="file:///c:/doctypes/docbook/xsl/"/>
> 
>  
> 
> 
> What am I missing?

Well, I could have sworn I had the Xalan example working,
but it doesn't.  I don't think you are missing anything.
Xalan doesn't seem to apply the catalog to URIs on the
command line.  Period.  I can put the
CatalogManager.properties verbosity setting up to 4, and I
never see a message like:

resolve(http://docbook.sourceforge.net/...).

The first resolve attempt is for:

resolve(../VERSION)

which is the first reference in docbook.xsl to another
file.  So it never even tries to look up the argument
to the -XSL option from the command line.

But if I put the stylesheet reference in the file
like this:


http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl";?>

Then the catalog is consulted and it works to find the
local file.   That shows that the catalog is working, but
how do we convince Xalan to use it on the 
command line argument?  Saxon has the -u option
to do that.

-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]


To subscribe or unsubscribe from this elist use the subscription
manager: 

Re: DOCBOOK-APPS: Attributes for figures

[Bob Stayton]

On Tue, Dec 03, 2002 at 10:23:33PM +0200, Togan Muftuoglu wrote:
> * Bob Stayton; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> >The problem is that your new match="figure" template
> >overwrites the original, which called the "formal.object"
> >template which produced the title.
> >That's why I suggested customizing formal.object instead:
> 
> Ok I understand this (just this not the whole thing :-)
> 
> >You need to test for 'figure' since formal.object is
> >used for example and table too.
> >Combined with your 'figure.properties' attribute-set,
> >this should work.
> 
> What happens is not only formal.figures disappear but also formal
> examples also disappear, only the Titles of the examples/figures are
> available. I tried with FOP 0.20.5cvs and XEP 2.77  :*( 
> 
> Somewhere I must be making a mistake that I do not see. I have the
> following in my customization
> 
>  use-attribute-sets="formal.object.properties">
>  black
>solid
>
> 
> 
> 
>   
> 
>   
> 
>   
> 
>  xsl:use-attribute-sets="formal.object.properties">
> 
>   
> 
>  
> 
>
>   
> 
> 
>   
> 
>   
> 

I cut and pasted the above into a customization layer, ran
xsltproc to generate the FO file using DocBook XSL 1.57.0,
and then ran FOP 0.20.4 on that and it worked.
Does your FO output include the 
element?  If not, then then XSLT stage is failing somehow.

-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]

RE: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Jeff Beal]

I knew I should have looked at the latest documentation.  (Still using 1.48
stylesheets for HTML)

-Original Message-
From: Jirka Kosek [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 3:36 PM
To: Jeff Beal; [EMAIL PROTECTED]
Subject: Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58


Jeff Beal wrote:
> 
> Oh.  In the parameter documentation for default.encoding, Norm mentions
that
> it only works for Saxon.

This parameter was renamed to chunker.output.encoding quite ago. It
works in many processor, not only in Saxon. In Saxon you must also set
saxon.character.representation=native in order to activate previous
setting.

Jirka

-- 
-
  Jirka Kosek
  e-mail: [EMAIL PROTECTED]
  http://www.kosek.cz

Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Jirka Kosek]

Jeff Beal wrote:
> 
> Oh.  In the parameter documentation for default.encoding, Norm mentions that
> it only works for Saxon.

This parameter was renamed to chunker.output.encoding quite ago. It
works in many processor, not only in Saxon. In Saxon you must also set
saxon.character.representation=native in order to activate previous
setting.

Jirka

-- 
-
  Jirka Kosek
  e-mail: [EMAIL PROTECTED]
  http://www.kosek.cz

Re: DOCBOOK-APPS: Attributes for figures

[Togan Muftuoglu]

* Bob Stayton; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:

The problem is that your new match="figure" template
overwrites the original, which called the "formal.object"
template which produced the title.
That's why I suggested customizing formal.object instead:


Ok I understand this (just this not the whole thing :-)


You need to test for 'figure' since formal.object is
used for example and table too.
Combined with your 'figure.properties' attribute-set,
this should work.


What happens is not only formal.figures disappear but also formal
examples also disappear, only the Titles of the examples/figures are
available. I tried with FOP 0.20.5cvs and XEP 2.77  :*( 

Somewhere I must be making a mistake that I do not see. I have the
following in my customization

  
use-attribute-sets="formal.object.properties">
black
  solid
  



 

 
   
 

 
	xsl:use-attribute-sets="formal.object.properties">
   
 
   

   
  
 
   
   
 
   
 




--

Togan Muftuoglu

Re: DOCBOOK-APPS: Error with Xalan-J 2.4.0 and DocBook XSL 1.58.1

[Patrick Hartling]

Hmm, it appears that my problem is related to the JDK version rather than 
to the stylesheets or the XSLT processor.  I was using 1.4.1_01, but if I 
use 1.3.1_06 instead, I get no errors (with the 1.58.1 stylesheets and 
Xalan-J 2.4.1).

To answer your question, I did not see the aforementioned error with the 
1.57.0 stylesheets.  It's easier for me to change my $JAVA_HOME 
environment variable than it is to change XSLT processors, so I think 
I'll go with JDK 1.3.1.

 -Patrick

Bob Stayton wrote:
On Tue, Dec 03, 2002 at 10:43:37AM -0600, Patrick Hartling wrote:


I just downloaded version 1.58.1 of the DocBook XSL stylesheets for 
testing, and I am getting this error quite a bit using Xalan-J 2.4.0:

file:///home/users/patrick/docbook-xsl-1.58.1/common/gentext.xsl; Line 
130; Column 57; XSLT Error (javax.xml.transform.TransformerException): 
Variable accessed before it is bound!

If I use Saxon, there is no error (though I have not reviewed the 
rendered documents for correctness yet).  Before I switch everything over 
to Saxon, I want to be sure that this is a problem with Xalan and not the 
new stylesheets.  I have attached the smallest example I could come up 
with that causes the error.  Thanks.


I don't get this error when using Xalan-J 2.4.1 (I don't
have 2.4.0 to test).  

I can't see why the line in question should produce an
error since the referrer parameter is declared:


  
  
  

  


  



 
  


Do you get this same error with the 1.57.0 stylesheets,
which had a very similar template?




--
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED]| 2624 Howe Hall: 1.515.294.4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/

Re: DOCBOOK-APPS: Attributes for figures

[Bob Stayton]

On Tue, Dec 03, 2002 at 07:35:58PM +0100, Alain NAKACHE wrote:
> It is a good approach of boxed figures but the box is as large as the whole 
> fo:block and not only the bitmap.
> 
> Is it what you expected first ?

Well, yes, the block is by default the width of the page,
so the border is the whole width.  It does look funny
on a graphic.
 
> I know that the difficulty is to guess the bounds of the picture (whatever 
> the format is) to define closely the block.
> 
> Is it possible to obtain this result ?

The figure element can contain any number of things
besides graphics, so perhaps you should be concentrating
on graphics within figure rather than on figure.

If the generated  object has the
border properties, they should fit tightly to the graphic.
This works in RenderX's XEP, but the border doesn't
show at all in FOP when I do that.  If you are using FOP,
I think the imagemagik solution is probably the best.


Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]
> 
> At 10:10 03/12/02 -0800, Bob Stayton wrote:
> >On Tue, Dec 03, 2002 at 04:15:17PM +0200, Togan Muftuoglu wrote:
> > > * Togan Muftuoglu; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> > > >* Alain NAKACHE; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> > > >>At 14:49 03/12/02 +0200, Togan Muftuoglu wrote:
> > > >>>Hi,
> > > >>figure bitmap.
> > > >>
> > > >>Bob Stayton pointed to me the following advice :
> > > >>"You would need to customize the template named
> > > >>'formal.object' in the stylesheet file fo/formal.xsl.
> > > >>But you would need to learn XSL-FO in order to put
> > > >>the border attributes in the right place.  Then you
> > > >>have to hope that FOP can output it correctly."
> > > >>but my result was to enclose the whole Block and not only the figure.
> > > >
> > > >Strange I had the exact same result :-) Also fighting with FOP is
> > > >another major issue
> > >
> > > Ok I have progressed a bit further I am able to make a frame all around
> > > the figure and only figure.
> > >
> > >> > use-attribute-sets="formal.object.properties">
> > > black
> > >   solid
> > >   
> > >
> > > 
> > >   
> > > 
> > > 
> > > 
> > >
> > >
> > > The only thing missing is the Figure title ie "Figure 1.1 Bla Bla"
> >
> >
> >The problem is that your new match="figure" template
> >overwrites the original, which called the "formal.object"
> >template which produced the title.
> >That's why I suggested customizing formal.object instead:
> >
> >
> >   
> >
> >   
> > 
> >   
> >
> >> xsl:use-attribute-sets="formal.object.properties">
> > 
> >   
> > 
> >  
> > 
> >
> >   
> > 
> > 
> >   
> > 
> >   
> >
> >
> >You need to test for 'figure' since formal.object is
> >used for example and table too.
> >Combined with your 'figure.properties' attribute-set,
> >this should work.
> >
> >--
> >
> >Bob Stayton 400 Encinal Street
> >Publications Architect  Santa Cruz, CA  95060
> >Technical Publications  voice: (831) 427-7796
> >The SCO Group   fax:   (831) 429-1887
> > email: [EMAIL PROTECTED]
> 

Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[ABX]

Bob Stayton <[EMAIL PROTECTED]>:
> The latest version of xsltproc has changes to make it
> better support xhtml output.  You might try upgrading.

I upgraded but it does not helped. Strangest thing is that when I use
_chunked_ output with
   
then each small html has
  
while when I use
   
then long file xhtml has
  
in header

ABX

Re: DOCBOOK-APPS: Re: problems with publishing cvs refguide

[Dumas Patrice]

On Fri, Oct 11, 2002 at 12:55:01PM -0400, Norman Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> / [EMAIL PROTECTED] (Patrice DUMAS - DOCT) was heard to say:
> | book.xml:9: warning: failed to load external entity 
>"../../docbook/ebnf/ebnf-4.2CR1.dtd"
> | ]>
> 
> You need the custom DTD that I'm using for the book. Uhm, the best thing to do is
> probably change the 

Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Bob Stayton]

On Tue, Dec 03, 2002 at 06:25:36PM +0100, ABX wrote:
> Jeff Beal <[EMAIL PROTECTED]>:
> > Set the XSL parameter 'default-encoding' to ISO-8859-1.
> 
> It does not help. I tried as empty customization layer as possible:
> 
> 
> http://www.w3.org/1999/XSL/Transform";
> xmlns:doc="http://nwalsh.com/xsl/documentation/1.0";
> xmlns:exsl="http://exslt.org/common";
> xmlns:set="http://exslt.org/sets";
> version="1.0"
> exclude-result-prefixes="doc exsl set">
>   
>   ISO-8859-1
> 
> 
> The only solution was to switch from xhtml to html but I'd prefer xhtml.
> 
> I used xsltproc, btw.

The latest version of xsltproc has changes to make it
better support xhtml output.  You might try upgrading.

-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]

Re: DOCBOOK-APPS: Attributes for figures

[Alain NAKACHE]

It is a good approach of boxed figures but the box is as large as the whole 
fo:block and not only the bitmap.

Is it what you expected first ?

I know that the difficulty is to guess the bounds of the picture (whatever 
the format is) to define closely the block.

Is it possible to obtain this result ?

At 10:10 03/12/02 -0800, Bob Stayton wrote:
On Tue, Dec 03, 2002 at 04:15:17PM +0200, Togan Muftuoglu wrote:
> * Togan Muftuoglu; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> >* Alain NAKACHE; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> >>At 14:49 03/12/02 +0200, Togan Muftuoglu wrote:
> >>>Hi,
> >>figure bitmap.
> >>
> >>Bob Stayton pointed to me the following advice :
> >>"You would need to customize the template named
> >>'formal.object' in the stylesheet file fo/formal.xsl.
> >>But you would need to learn XSL-FO in order to put
> >>the border attributes in the right place.  Then you
> >>have to hope that FOP can output it correctly."
> >>but my result was to enclose the whole Block and not only the figure.
> >
> >Strange I had the exact same result :-) Also fighting with FOP is
> >another major issue
>
> Ok I have progressed a bit further I am able to make a frame all around
> the figure and only figure.
>
>use-attribute-sets="formal.object.properties">
> black
>   solid
>   
>
> 
>   
> 
> 
> 
>
>
> The only thing missing is the Figure title ie "Figure 1.1 Bla Bla"


The problem is that your new match="figure" template
overwrites the original, which called the "formal.object"
template which produced the title.
That's why I suggested customizing formal.object instead:


  

  

  

  

  

 

   
  


  

  


You need to test for 'figure' since formal.object is
used for example and table too.
Combined with your 'figure.properties' attribute-set,
this should work.

--

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]

Re: DOCBOOK-APPS: Customization Problem - Chapter TOCs

[Bob Stayton]

On Tue, Dec 03, 2002 at 02:32:46PM +, Nicholas Atkinson wrote:
> I have a number of customizations which I use when generating HTML Help from my 
>docbook documents.
> 
> However there is one customization which causes problems when I add it to the 
>customization layer, which works fine (in the v 1.56.1 transforms) when I modify 
>html\component.xsl directly.  I would like to resolve this if possible as modifying 
>the transforms themselves is, well, messy!
> 
> Basically I want the chapter toc to appear after the text of the chapter (before any 
>subsections of course) rather than before it.  I already have a customization which 
>gets rid of the "Table of Contents" text.  The desired end result is that links to 
>child sections appear at the bottom of the page rather than the top.
> 
> If I change this template in html\component.xsl:
> 
> 
>   
> 
>   
> 
>   
> 
> 
> 
> 
> 
> 
>   
> 
>   
> 
>
>   
> 
>   
> 
> 
> 
>   
> 
> 
> to this:
> 
> 
>   
> 
>   
> 
>   
> 
> 
> 
> 
> 
> 
> 
>   
> 
>   
> 
>
>   
> 
>   
> 
> 
>   
> 
> 
> 
> then I get what I want.   (All I have done is move the  up).
> 
> However if I put this template, or the original of the template, in my customization 
>layer and use the original html\component.xsl, then the chunking goes all wrong.
> 
> Does anyone know why this is the case, or what the preferred way of achieving such 
>behaviour might be?

The problem here is that the chunk.xsl stylesheet
also has a template match on chapter, to do the chunking,
and that template then does apply-imports to use the
components.xsl chapter template.  When you put
a match="chapter" template in your customization layer,
it has higher import precedence than the one
in chunk.xsl, and you lose your chunking.

To preserve chunking, you will need to copy the template
in chunk.xsl that starts with:

  

Re: DOCBOOK-APPS: Attributes for figures

[Bob Stayton]

On Tue, Dec 03, 2002 at 04:15:17PM +0200, Togan Muftuoglu wrote:
> * Togan Muftuoglu; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> >* Alain NAKACHE; <[EMAIL PROTECTED]> on 03 Dec, 2002 wrote:
> >>At 14:49 03/12/02 +0200, Togan Muftuoglu wrote:
> >>>Hi,
> >>figure bitmap.
> >>
> >>Bob Stayton pointed to me the following advice :
> >>"You would need to customize the template named
> >>'formal.object' in the stylesheet file fo/formal.xsl.
> >>But you would need to learn XSL-FO in order to put
> >>the border attributes in the right place.  Then you
> >>have to hope that FOP can output it correctly."
> >>but my result was to enclose the whole Block and not only the figure.
> >
> >Strange I had the exact same result :-) Also fighting with FOP is
> >another major issue
> 
> Ok I have progressed a bit further I am able to make a frame all around
> the figure and only figure. 
> 
>use-attribute-sets="formal.object.properties">
> black
>   solid
>   
> 
> 
>   
> 
> 
> 
> 
> 
> The only thing missing is the Figure title ie "Figure 1.1 Bla Bla"


The problem is that your new match="figure" template
overwrites the original, which called the "formal.object"
template which produced the title.
That's why I suggested customizing formal.object instead:


  

  

  

  

  

 

   
  


  

  


You need to test for 'figure' since formal.object is
used for example and table too.
Combined with your 'figure.properties' attribute-set,
this should work.

-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]

RE: DOCBOOK-APPS: Including Procedures in TOC?

[David Cramer]

This isn't too hard to do, but would make a good feature request. I added the same 
thing and the notion of 'Procedures' has been popular with the users of our docs. One 
even asked if we could include procedures in the pdf bookmarks pane. 

There's a list.of.unknowns hook in autotoc.xsl that makes it easier to add. Be sure 
not to include procedures without titles. The changes below are from the fo xsls:

You need this (modifying a template in autotoc.xsl):
 

  


In division.xsl, you'll need to add something like this in a few places:

  

  

  
  
auto-odd
  

...so you can use the generate.toc param to control whether a list of procedures 
appears.

You'll need to add this to your l10n customizations so the list of procedures will 
have a title:
   
 
  
   

There are probably some other things I'm forgetting, but that should get you started :)

David

> -Original Message-
> From: Andy Jewell [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 03, 2002 11:15 AM
> To: Docbook List
> Subject: DOCBOOK-APPS: Including Procedures in TOC?
> 
> 
> I have a lot of procedures in my documents.  Currently, the TOC
> generation is working great but doesn't by default include 
> procedures -
> which also don't seem to be classified as "formal" components such as
> are figures (am I getting this right?).
> 
> Can anyone give me an idea on what I would do to go about getting
> procedures included in the TOC - either with the TOC or as a separate
> list?  Thanks for any help you can offer!
> 
> 
> -- Andy
> 
> 
> 

RE: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Jeff Beal]

Oh.  In the parameter documentation for default.encoding, Norm mentions that
it only works for Saxon.

-Original Message-
From: ABX [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 12:26 PM
To: [EMAIL PROTECTED]
Subject: Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58


Jeff Beal <[EMAIL PROTECTED]>:
> Set the XSL parameter 'default-encoding' to ISO-8859-1.

It does not help. I tried as empty customization layer as possible:


http://www.w3.org/1999/XSL/Transform";
xmlns:doc="http://nwalsh.com/xsl/documentation/1.0";
xmlns:exsl="http://exslt.org/common";
xmlns:set="http://exslt.org/sets";
version="1.0"
exclude-result-prefixes="doc exsl set">
  
  ISO-8859-1


The only solution was to switch from xhtml to html but I'd prefer xhtml.

I used xsltproc, btw.

ABX

RE: DOCBOOK-APPS: Including Procedures in TOC?

[Jeff Beal]

If you're using XSL, there's a "formal.procedures" parameter that you can
turn on for the latter option.  It won't put them into the TOC, though.

-Original Message-
From: Andy Jewell [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 12:15 PM
To: Docbook List
Subject: DOCBOOK-APPS: Including Procedures in TOC?


I have a lot of procedures in my documents.  Currently, the TOC
generation is working great but doesn't by default include procedures -
which also don't seem to be classified as "formal" components such as
are figures (am I getting this right?).

Can anyone give me an idea on what I would do to go about getting
procedures included in the TOC - either with the TOC or as a separate
list?  Thanks for any help you can offer!


-- Andy

Re: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[ABX]

Jeff Beal <[EMAIL PROTECTED]>:
> Set the XSL parameter 'default-encoding' to ISO-8859-1.

It does not help. I tried as empty customization layer as possible:


http://www.w3.org/1999/XSL/Transform";
xmlns:doc="http://nwalsh.com/xsl/documentation/1.0";
xmlns:exsl="http://exslt.org/common";
xmlns:set="http://exslt.org/sets";
version="1.0"
exclude-result-prefixes="doc exsl set">
  
  ISO-8859-1


The only solution was to switch from xhtml to html but I'd prefer xhtml.

I used xsltproc, btw.

ABX

Re: DOCBOOK-APPS: Error with Xalan-J 2.4.0 and DocBook XSL 1.58.1

[Bob Stayton]

On Tue, Dec 03, 2002 at 10:43:37AM -0600, Patrick Hartling wrote:
> I just downloaded version 1.58.1 of the DocBook XSL stylesheets for 
> testing, and I am getting this error quite a bit using Xalan-J 2.4.0:
> 
> file:///home/users/patrick/docbook-xsl-1.58.1/common/gentext.xsl; Line 
> 130; Column 57; XSLT Error (javax.xml.transform.TransformerException): 
> Variable accessed before it is bound!
> 
> If I use Saxon, there is no error (though I have not reviewed the 
> rendered documents for correctness yet).  Before I switch everything over 
> to Saxon, I want to be sure that this is a problem with Xalan and not the 
> new stylesheets.  I have attached the smallest example I could come up 
> with that causes the error.  Thanks.

I don't get this error when using Xalan-J 2.4.1 (I don't
have 2.4.0 to test).  

I can't see why the line in question should produce an
error since the referrer parameter is declared:


  
  
  

  


  



 
  


Do you get this same error with the 1.57.0 stylesheets,
which had a very similar template?

-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
The SCO Group   fax:   (831) 429-1887
email: [EMAIL PROTECTED]

DOCBOOK-APPS: Including Procedures in TOC?

[Andy Jewell]

I have a lot of procedures in my documents.  Currently, the TOC
generation is working great but doesn't by default include procedures -
which also don't seem to be classified as "formal" components such as
are figures (am I getting this right?).

Can anyone give me an idea on what I would do to go about getting
procedures included in the TOC - either with the TOC or as a separate
list?  Thanks for any help you can offer!


-- Andy

DOCBOOK-APPS: Error with Xalan-J 2.4.0 and DocBook XSL 1.58.1

[Patrick Hartling]

I just downloaded version 1.58.1 of the DocBook XSL stylesheets for 
testing, and I am getting this error quite a bit using Xalan-J 2.4.0:

file:///home/users/patrick/docbook-xsl-1.58.1/common/gentext.xsl; Line 
130; Column 57; XSLT Error (javax.xml.transform.TransformerException): 
Variable accessed before it is bound!

If I use Saxon, there is no error (though I have not reviewed the 
rendered documents for correctness yet).  Before I switch everything over 
to Saxon, I want to be sure that this is a problem with Xalan and not the 
new stylesheets.  I have attached the smallest example I could come up 
with that causes the error.  Thanks.

 -Patrick


--
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED]| 2624 Howe Hall: 1.515.294.4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/

http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd";>

   
  Sample Section
  Refer to .
  
 Table
 
 
  
   

RE: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Jeff Beal]

Set the XSL parameter 'default-encoding' to ISO-8859-1.

-Original Message-
From: Wlodek Skiba [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 11:02 AM
To: [EMAIL PROTECTED]
Subject: DOCBOOK-APPS: troubles after changed encoding in XSL 1.58


I used 1.57 templates for my DocBook. When I used  than it was
rendered as ™ but codepage for xhtml was
  
after switch to 1.58 I noticed in news note about changed output to
  
Trademark is rendered now as three strange characters (trademark is only
example, other symbols and international specific characters are changed
too).
That change makes aspell to recheck many of (previously correct) words.
How can I back to old encoding or force aspell to understand encoding ?

BTW, I had  in original docbook files.

Thanks in advance,

ABX

DOCBOOK-APPS: troubles after changed encoding in XSL 1.58

[Wlodek Skiba]

I used 1.57 templates for my DocBook. When I used  than it was
rendered as ™ but codepage for xhtml was
  
after switch to 1.58 I noticed in news note about changed output to
  
Trademark is rendered now as three strange characters (trademark is only
example, other symbols and international specific characters are changed too).
That change makes aspell to recheck many of (previously correct) words.
How can I back to old encoding or force aspell to understand encoding ?

BTW, I had  in original docbook files.

Thanks in advance,

ABX

Re: DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint

[Paul Grosso]

At 16:00 2002 12 03 +0300, Vitaly Ostanin wrote:
>On Tue, 03 Dec 2002 07:30:03 -0500
>Norman Walsh <[EMAIL PROTECTED]> wrote:
>> Base URIs have no bearing on ID values.
>
>ID values used for linking and must be uniq, right?

It is a validation error if there are duplicate IDs
in a document.

>In modular set of docbook/xml after processing XInclude some
>documents may to have duplicates of ID. 

True, and this would be a validation error.  The same is
true if you used external parsed entities.  XInclude does
nothing to solve the ID uniqueness problem.  

In particular, if you reuse the same chunk of XML in two places 
in the same document and any element therein contains an ID, you
will end up with a document that is not valid (whether you
use external parsed entities or XInclude).

>I think what using 
>'xml:base' + 'filename' + 'id'
>can produce uniq values as result. 

Maybe, but that isn't how things work in XML.

paul

RE: DOCBOOK-APPS: Customization Problem - Chapter TOCs

[Jeff Beal]

The basic 
problem is that the chunking stylesheets override the chapter templates (because 
it's a chunk) and use  to call the template in 
html\component.xsl.  If you put a customization on that template, it will 
break the chunking code.  I think that in the latest version of the 
stylesheets, Norm has changed the chunking mechanism to allow customization of 
chunked elements.
 
Jeff 
Beal
-Original Message-From: Nicholas Atkinson 
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 03, 2002 9:33 
AMTo: [EMAIL PROTECTED]Subject: 
DOCBOOK-APPS: Customization Problem - Chapter TOCs
I have a number of customizations which I use when 
generating HTML Help from my docbook documents.
 
However there is one customization which causes 
problems when I add it to the customization layer, which works fine (in the v 
1.56.1 transforms) when I modify html\component.xsl directly.  I would like 
to resolve this if possible as modifying the transforms themselves is, well, 
messy!
 
Basically I want the chapter toc to appear after 
the text of the chapter (before any subsections of course) rather than 
before it.  I already have a customization which gets rid of the 
"Table of Contents" text.  The desired end result is that links to child 
sections appear at the bottom of the page rather than the top.
 
If I change this template in 
html\component.xsl:
 
  
      
    
  
    
 
        
 
          
  
    
         
  
    
    
      

 
to this:
 

  
      
    
  
    
 
        
 
    
          
  
    
         
  
    
      

then I get what I want.   (All I have 
done is move the  up).
 
However if I put this template, or the original of 
the template, in my customization layer and use the original html\component.xsl, 
then the chunking goes all wrong.
 
Does anyone know why this is the case, or what the 
preferred way of achieving such behaviour might be?
 
nik
 

DOCBOOK-APPS: Customization Problem - Chapter TOCs

[Nicholas Atkinson]

I have a number of customizations which I use when 
generating HTML Help from my docbook documents.
 
However there is one customization which causes 
problems when I add it to the customization layer, which works fine (in the v 
1.56.1 transforms) when I modify html\component.xsl directly.  I would like 
to resolve this if possible as modifying the transforms themselves is, well, 
messy!
 
Basically I want the chapter toc to appear after 
the text of the chapter (before any subsections of course) rather than 
before it.  I already have a customization which gets rid of the 
"Table of Contents" text.  The desired end result is that links to child 
sections appear at the bottom of the page rather than the top.
 
If I change this template in 
html\component.xsl:
 
  
      
    
  
    
 
        
 
          
  
    
         
  
    
    
      

 
to this:
 

  
      
    
  
    
 
        
 
    
          
  
    
         
  
    
      

then I get what I want.   (All I have 
done is move the  up).
 
However if I put this template, or the original of 
the template, in my customization layer and use the original html\component.xsl, 
then the chunking goes all wrong.
 
Does anyone know why this is the case, or what the 
preferred way of achieving such behaviour might be?
 
nik
 

Re: DOCBOOK-APPS: Attributes for figures

[Alain NAKACHE]

At 14:49 03/12/02 +0200, Togan Muftuoglu wrote:
Hi,
I maight be missing but looks like there is attribute sets for
figures.
What I mean is I would like have a border around the figure so it 
is
easily distinguished ( nnot to say that it look better :-). Sİnce
there
is no such thing How do I make the figures to have frame around them
?
Thanks
-- 
Togan Muftuoglu

Hi Togan,
Despite all my attempts, I didn't manage to obtain a border close to the
figure bitmap.
Bob Stayton pointed to me the following advice :

"You would need to customize the template named
'formal.object' in the stylesheet file fo/formal.xsl.
But you would need to learn XSL-FO in order to put
the border attributes in the right place.  Then you
have to hope that FOP can output it correctly."
but my result was to enclose the whole Block and not only the
figure.
The solution I found was to use Image Magick convert tool. The syntax :

convert -border 1x1 -bordercolor \#000 file.png result.png
The result is just as I wanted.
Regards,
Alain.

DOCBOOK-APPS: Visualizing Changes

[Mikhail Sobolev]

--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I've been using docbook/some customized stylesheets to prepare our ISO
documents.  Everything seems to be fine, however one of the requirements
is to visualize the difference between the current "draft" and the last
"approved" version by using a vertical line along the changed paragraph.

At the moment, I am just completely clueless as how to work with this
problem.

I'd appreciate any hints at all.

Thank you in advance,

--
Misha

--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE97K2FMYLUe7XufiwRAg2zAJ0bxgJNfwzpcG6cG4LvM+7tTz226ACgrU37
I5sKVXEg3aBpPttrmbGo4QY=
=9SWO
-END PGP SIGNATURE-

--M9NhX3UHpAaciwkO--

DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint

[Vitaly Ostanin]

On Tue, 03 Dec 2002 07:30:03 -0500
Norman Walsh <[EMAIL PROTECTED]> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> / Vitaly Ostanin <[EMAIL PROTECTED]> was heard to say:
> | DocBook DTD doesn't support 'xml:base' attribute from
> | XInclude.
> 
> I think we're planning to fix that[1].

Thanks.

> | Yes, this attribute appear to content model, and useful for
> | many of included documents - 'xml:base' could be useful for
> | getting uniq values of 'id', uniq names of images in
> |  in the all set of documents.
> 
> Base URIs have no bearing on ID values.

ID values used for linking and must be uniq, right?

In modular set of docbook/xml after processing XInclude some
documents may to have duplicates of ID. 

I think what using 
'xml:base' + 'filename' + 'id'
can produce uniq values as result. In this case final
value of 'xml:base' can be calculated also from 'xml:base' of
parent tags (if there exists relative values).

This changes appear 'idref' of  and .

For images we have a similar problem - files with images must
have uniq names.

BTW, all html build exist in the one dir (except 
of olinking schema from Bab Stayton). 'xml:base' could be useful
for split documents into separate dirs.

Sorry for disturb.



-- 
Regards, Vyt
mailto:  [EMAIL PROTECTED]
JID: [EMAIL PROTECTED]

DOCBOOK-APPS: Attributes for figures

[Togan Muftuoglu]

Hi,

I maight be missing but looks like there is attribute sets for figures.
What I mean is I would like have a border around the figure so it is
easily distinguished ( nnot to say that it look better :-). Sİnce there
is no such thing How do I make the figures to have frame around them ?

Thanks
--

Togan Muftuoglu

DOCBOOK-APPS: DocBook XSL Stylesheets v1.58.1 released

[Norman Walsh]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I should have posted this last week...

http://sourceforge.net/projects/docbook/

   The 1.58.1 release adds some initial support for extensions in
   xsltproc, adds a few features, and fixes bugs.

 o This release contains the first attempt at extension support for
   xsltproc. The only extension available to date is the one that adjusts
   table column widths. Run extensions/xsltproc/python/xslt.py.

 o Fixed bugs in calculation of adjusted column widths to correct for
   rounding errors.

 o Support nested refsection elements correctly.

 o Reworked gentext.template to take context into consideration. The name
   of elements in localization files is now an xpath-like context list,
   not just a simple name.

 o Made some improvements to bibliography formatting.

 o Improved graphical formatting of admonitions.

 o Added support for entrytbl.

 o Support spanning index terms.

 o Support bibliosource.

Changes since version 1.57.0 (2002-10-22)

Changes to xsl/*

  | 2002-11-29  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * Makefile: Exclude the debian directory from the distribution
  |   archive
  | 
  | * VERSION: Version 1.58.1 released.
  | 
  | 2002-11-17  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * .cvsignore: Ignore the debian directory
  | 
  | * Makefile: Don't include pyc files in distribution
  | 
  | * README: Copyright this year too, huh?
  | 
  | * RELEASE-NOTES.xml: Release notes
  | 
  | * VERSION: Version 1.58.0 released.
  | 

Changes to xsl/common/*

  | 2002-11-23  Robert Stayton <[EMAIL PROTECTED]>
  | 
  | * common.xsl: Fixed bug in orderedlist-starting-number test
  |   when @continuation not set.
  | 
  | 2002-11-14  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * common.xsl: Handle nested refsections in section.level
  | 
  | * gentext.xsl: Pass full xpath name to gentext.template
  |   instead of just the local-name
  | 
  | * l10n.xsl: Make gentext.template search through /-separated
  |   names
  | 

Changes to xsl/extensions/*

  | 2002-11-17  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * build.xml: New file.
  | 

Changes to xsl/fo/*

  | 2002-11-29  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * pagesetup.xsl: Don't output a footnote-separator for FOP
  | 
  | 2002-11-16  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * biblio.xsl: Support abstract in bibliomixed
  | 
  | * biblio.xsl, xref.xsl: Support bibliosource; improve numbered
  |   bibliography entries and cross-references to them
  | 
  | * pagesetup.xsl: Added template to create footnote separator
  |   rule (if supported by your favorite FO processor)
  | 
  | * sections.xsl: Use value-of instead of copy-of for fo:marker
  |   because I haven't thought of a better way to avoid footnotes
  |   in markers which are illegal
  | 
  | 2002-11-15  Robert Stayton <[EMAIL PROTECTED]>
  | 
  | * admon.xsl: Changed graphical.admonition template from an
  |   fo:table to an fo:list-block, so it works in both FOP and
  |   XEP.
  | 
  | * lists.xsl: Fixed two bugs in longest.term template that
  |   prevented proper calculation of longest term width in
  |   variablelist.
  | 
  | 2002-11-15  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * table.xsl: Add support for xsltproc adjustColumnWidths
  |   extension
  | 
  | 2002-11-14  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * biblio.xsl: Use xreflabel (if it's present) on bibliography
  |   entries
  | 
  | * component.xsl: Don't restart page numbers on the first
  |   preface
  | 
  | * table.xsl: Support entrytbl
  | 
  | 2002-11-08  Robert Stayton <[EMAIL PROTECTED]>
  | 
  | * pagesetup.xsl: Corrected left and right page margins for
  |   even page masters: inner and outer were reversed from what
  |   they should have been.
  | 
  | 2002-10-31  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * autoidx.xsl: Support spanning index terms
  |   (endofrange/startref)
  | 
  | * lists.xsl: Put para spacing around tabular simplelists
  | 

Changes to xsl/html/*

  | 2002-11-29  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * lists.xsl: Make opencircle=circle in itemizedlist marks
  | 
  | 2002-11-25  Robert Stayton <[EMAIL PROTECTED]>
  | 
  | * sections.xsl: Made subtitles in sections scale to proper
  |   heading level.
  | 
  | 2002-11-16  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * admon.xsl: Align titles on graphical admonitions
  | 
  | * biblio.xsl, xref.xsl: Support bibliosource; improve numbered
  |   bibliography entries and cross-references to them
  | 
  | 2002-11-15  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * table.xsl: Insignificant tweak
  | 
  | 2002-11-14  Norman Walsh <[EMAIL PROTECTED]>
  | 
  | * biblio.xsl: Use xreflabel (if it's present) on bibliography
  |   entries
  | 
  |  

Re: DOCBOOK-APPS: XInclude doesn't validate with xmllint

[Jean-Baptiste Quenot]

* Yann Dirson:

> There is even a use-case for this.  If the individual XML files do not
> validate (ie. conform to a DTD  which has the xinclude elements), then
> we cannot make use of the  existing SGML editing tools (psgml comes to
> my  mind as  one of  the most  widely used,  since its  existence even
> brought some vi adepts to launch emacs sometimes).

In my case, SGML  is the reason why I don't use  XInclude.  I would love
to use  it, but it would  require creating an intermediate  XML document
used as new master document for validating and transforming.  I avoid to
do that because then  the document you have in your  editor (ViM) is not
the same as the one for which errors are reported.

Anyway, interesting to hear your point of view.
-- 
Jean-Baptiste Quenot
http://caraldi.com/jbq/

DOCBOOK-APPS: Re: XInclude doesn't validate with xmllint

[Norman Walsh]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

/ Vitaly Ostanin <[EMAIL PROTECTED]> was heard to say:
| DocBook DTD doesn't support 'xml:base' attribute from XInclude.

I think we're planning to fix that[1].

| Yes, this attribute appear to content model, and useful for many
| of included documents - 'xml:base' could be useful for getting
| uniq values of 'id', uniq names of images in  in the
| all set of documents.

Base URIs have no bearing on ID values.

Be seeing you,
  norm
[1] http://lists.oasis-open.org/archives/docbook-tc/200211/msg00012.html
- -- 
Norman Walsh <[EMAIL PROTECTED]>  | Time is the old justice that
http://www.oasis-open.org/docbook/ | examines all
Chair, DocBook Technical Committee | offenders.--Shakespeare
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 

iD8DBQE97KPLOyltUcwYWjsRAk8IAJ0aGQBG7KT8FPuV83+5Z1IjGTcuTwCeLbF/
qe4bT9QPLEHA2JvArJzbqW0=
=eXmr
-END PGP SIGNATURE-

RE: DOCBOOK-APPS: XML catalog documentation

[Jeanson Mauritz]

> -Original Message-
> From: Bob Stayton [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 11, 2002 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: DOCBOOK-APPS: XML catalog documentation
> 
> 
> I've rewritten my chapter on using XML catalogs with
> DocBook XSL so that it is more complete and accurate.  It
> is available at
> 
> http://www.sagehill.net/xml/docbookxsl/Catalogs.html
> 
> Comments welcome.

Regarding the Xalan command line example:

I can't prevent Xalan from trying to go out on the web. This means it 
doesn't work when I'm offline. The log looks like this: 

Parse catalog: catalog.xml
Loading catalog: catalog.xml
Default BASE: file:/C:/XMLtest/catalogs/test/Xalan/catalog.xml
uri: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
file:///c:/doctypes/docbook/xsl/html/docbook.xsl
URI: http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
file:/c:/doctypes/docbook/xsl/html/docbook.xsl
rewriteURI: http://docbook.sourceforge.net/release/xsl/current/
file:///c:/doctypes/docbook/xsl/
REWRITE_URI: http://docbook.sourceforge.net/release/xsl/current/
file:/c:/doctypes/docbook/xsl/

(Location of error unknown)XSLT Error (javax.xml.transform.TransformerConfigurat
ionException): javax.xml.transform.TransformerException: java.net.ConnectExcepti
on: Connection refused: connect

The catalog file:
 

  
  http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl";
  uri="file:///c:/doctypes/docbook/xsl/html/docbook.xsl"/> 
  
  http://docbook.sourceforge.net/release/xsl/current/";
rewritePrefix="file:///c:/doctypes/docbook/xsl/"/>

 


What am I missing?


Mauritz Jeanson