OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

Mail Index message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: docbook-apps-digest Digest #440


RE: DOCBOOK-APPS: Re: CSS stylesheet for DocBook
Re: DOCBOOK-APPS: CSS stylesheet for DocBook
DOCBOOK-APPS: Re: DocBook XSL-FO: content-width="scale-to-fit"
DOCBOOK-APPS: Re: Problem with scaling Images
Re: DOCBOOK-APPS: Strange problem: no footnotes generated
Re: DOCBOOK-APPS: REPOST: Double-sided gives error
DOCBOOK-APPS: REPOST: Double-sided gives error
DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDF output
Re: DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDF
 output
DOCBOOK-APPS: 'pgwide' attribute in 'figure' element as a child of
 'glossdef'
Re: DOCBOOK-APPS: REPOST: Double-sided gives error
Re: DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDF
 output
Re: DOCBOOK-APPS: trying to use "xmlto" in red hat to customize PDF
 output
DOCBOOK-APPS: Page Number Prefixes
Re: DOCBOOK-APPS: 'pgwide' attribute in 'figure' element as a child of
 'glossdef'
DOCBOOK-APPS: Versioning
DOCBOOK-APPS: TEI & DocBook
RE: DOCBOOK-APPS: Versioning
DOCBOOK-APPS: First page of a PDF
Re: DOCBOOK-APPS: TEI & DocBook
Re: DOCBOOK-APPS: 'pgwide' attribute in 'figure' element as a child of
 'glossdef'

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


There's a nice one included with the XXE distribution:

  http://www.xmlmind.com/xmleditor


kind regards

Peter Ring



-----Original Message-----
From: ed nixon [mailto:ed.nixon@lynnparkplace.org]
Sent: 3. marts 2003 16:44
To: Shlomi Fish
Cc: Jonathan Lo; docbook-apps@lists.oasis-open.org
Subject: Re: DOCBOOK-APPS: Re: CSS stylesheet for DocBook


Shlomi Fish wrote:
> On Mon, 3 Mar 2003, Jonathan Lo wrote:
> <snip/>
> 
> CSS stylesheet are used on the web to customize the look and feel of HTML
> files. DocBook is not compatible with HTML and many of the tags and
> semantics are different.
> 
> It may be possible to convert a DocBook/XML file into HTML on the fly
> using an XSLT stylesheet. Generally speaking, DocBook is intended for
> off-line processing.

This information is misleading. CSS can be used to display XML files 
assuming the Cascading Style Sheet uses selectors that conform to the 
XML file syntax and also that the display facility is capable of 
rendering the combination. Examples of such tools are, Mozilla, Netscape 
7, IE6, XMetaL and numerous other XML editing products.

I believe there is a prototypical CSS to be found in the contrib section 
of the SourceForge distribution point. It was quite rudimentary the last 
time I looked. I you would like an alternative, contact me off line and 
I will send you a copy of one I use with XMetaL for editing purposes. 
Caveat: there may be selector syntax that is not supported by all 
browsers, in particular Internet Explorer.

Regards.                ...edN






> 1) Is there any CSS stylesheet for DocBook available?

	In

http://my.core.com/~dhorton/linux/diy/xml/index.xmlhttp://my.core.com/~dhorton/linux/diy/xml/style/davebook.css,

	you can find find another example.
-- 
Jaime Davila




>>>>> Bob Stayton <bobs@sco.com>:

> Well, I don't actually have SVG working in FOP 0.2.5rc.
> Did they adopt a new image library that isn't included?

Newer binary builds of FOP are missing the Jimi library from Sun,
which is used to include pixmaps.  The binaries are built with Jimi
support, but you have to fetch the jimi.jar file yourself, because of
licensing issues.

But SVG support in FOP is handled by Batik
	http://xml.apache.org/batik/
which I belive _is_ included in the binary builds.




>>>>> Brian Burridge <maillist@burridge.net>:

> I am including a bunch of PNG's in my DocBook, and converting the
> DocBook to PDF, using stylesheets and the Apache FOP.

Which version of the stylesheets, and which version of FOP?

[snip!]
> I've tried using contentWidth="4in" and nothing happens, and
> scale="75" and nothing happens.

I'm using
  <imagedata fileref="blahblah.png" format="PNG" depth="5cm" scalefit="1"/>
which seems to be working.




On Wed, Feb 19, 2003 at 11:18:32AM -0800, Bob Stayton wrote:
> > Joachim Ziegler wrote:

(Footnote 7 and 8 do not appear nowhere in the
HTML-chunks.)
> 
> I've been able to duplicate the incorrect results with
> the files Joachim sent me offlist.  I haven't been
> able to find the source of the problem yet, however.
> It happens with the chunking stylesheets only.

OK, I found the problem and fixed it in CVS.  You can
download the html/sections.xsl file from the sourceforge
CVS archive if you want the fix before the next release.

-- 

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: bobs@sco.com


-- 

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: bobs@sco.com




On Mon, Mar 03, 2003 at 10:52:07AM -0500, Brian Burridge wrote:
> (that's the second time I've posted to this maillist and never seen the
> post appear).
> 
> When I add the line below, I get "[ERROR]
> org.apache.fop.apps.StreamRenderer$RenderQueueEntry" very near the
> beginning and processing stops. That is the only change I'm making.
> 
> <xsl:param name="double.sided" select="1"/>

Actually, I did see your first post, but didn't have a
chance to respond.

I did some tests and found that some documents produce
that error but others don't.  I couldn't figure out why.

But those that did produce the error in FOP 0.20.4
did not generate the error in FOP 0.20.5rc.  I
interpret that as a bug in FOP 0.20.4, but I can't
be sure.

-- 

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: bobs@sco.com




(that's the second time I've posted to this maillist and never seen the
post appear).

When I add the line below, I get "[ERROR]
org.apache.fop.apps.StreamRenderer$RenderQueueEntry" very near the
beginning and processing stops. That is the only change I'm making.

<xsl:param name="double.sided" select="1"/>

Brian






  technically, this may be more of a red hat question, but i'll
give it a shot anyway.

  i'm using tim waugh's XML-based "selfdocbookx" working environment
as a starting point to design some new manuals.  the Makefile that
comes with that uses his "xmlto" shell script as a front end
to the appropriate processor to generate the appropriate output.

  for HTML output, the way to call "xmlto" would be something like:

  $ xmlto html -o <dirname> -m fragment -m fragment ... inputfile.xml

where the fragments are small stylesheet files that are incorporated
into a larger stylesheet underneath.  a sample fragment file that i 
use:
-------------------------------------
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:fo="http://www.w3.org/1999/XSL/Format"
                version='1.0'>

<xsl:param name="section.autolabel" select="1"/>

</xsl:stylesheet>
-------------------------------------

so i can customize the output by simply selecting the stylesheet
fragments that get passed to xmlto.  so far, so good, at least
with HTML output.

  the same holds for PDF output, with the Makefile running the
command:

  $ xmlto pdf -v --extensions -m frag1 -m frag2 ... inputfile.xml

once again, if i include the above "autolabel" fragment to be
passed to xmlto, sure enough, the resulting PDF file will have
sections auto-labelled.

  the problem comes when i try to add a stylesheet fragment whose
job it is to add page breaks before sections.  in reading bob
stayton's online docs, i'd want to add:

  <xsl:attribute-set name="section.title.level1.properties">
   <xsl:attribute name="break-before">page</xsl:attribute>
  </xsl:attribute-set>

but if i create another stylesheet fragment file, as in:

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

<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
                xmlns:fo="http://www.w3.org/1999/XSL/Format"
                version='1.0'>

<!-- Force section page breaks.. -->
<xsl:attribute-set name="section.title.level1.properties">
 <xsl:attribute name="break-before">page</xsl:attribute>
</xsl:attribute-set>

</xsl:stylesheet>

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

and add it to the xmlto command with "-m", it has no effect.
is this because it's not an xsl:param, but an xsl:attribute-set?
i'm going through the "xmlto" script now to see how it handles
fragments that are not just xsl:params, but does anyone know
if i can hand such a fragment to "xmlto" and have it processed
correctly?

  like i said, this is pretty much specifically an "xmlto"
question, so i'm hoping someone knows enough about it to 
give me some advice.

rday





On Tue, Mar 04, 2003 at 05:48:11AM -0500, Robert P. J. Day wrote:

> and add it to the xmlto command with "-m", it has no effect.
> is this because it's not an xsl:param, but an xsl:attribute-set?

The xmlto program doesn't interpret the fragments at all, just builds
a temporary stylesheet file which includes all the fragments.

If you comment out the 'trap' line in /usr/bin/xmlto and run it with
-v it will tell you the names of the temporary files it creates, and
won't remove them at exit.

Tim.
*/

PGP signature





Hello,

I'm using XSL-FO stylesheets 1.60.0 and XEP to render PS and PDF.

I have some glossary entries where I want to include figures as part
of the 'glossdef'.  Some of the images are a little wide, so I have
used 'pgwide="1"' as an attribute of the 'figure' element.  The
figures are not, however, being centred within the page, but remain
centred within the blocks that compose the text of the 'glossdef'.
I've glanced over formal.xsl, and 'pgwide="1"' should induce a
'span="all"' attribute on the fo:block in question.  This isn't
happening when the 'figure' is a child of 'glossdef' -- in fact, I
can't find a single 'span' attribute anywhere in the resulting FO
file.

Am I missing something here, or is this a bug?


-- 
Paul.

mailto:paulh@logicsquad.net
mailto:phoadley@maths.adelaide.edu.au




Thanks Bob. I upgraded and now its working.

Brian

On Mon, 2003-03-03 at 12:31, Bob Stayton wrote:
> On Mon, Mar 03, 2003 at 10:52:07AM -0500, Brian Burridge wrote:
> > (that's the second time I've posted to this maillist and never seen the
> > post appear).
> > 
> > When I add the line below, I get "[ERROR]
> > org.apache.fop.apps.StreamRenderer$RenderQueueEntry" very near the
> > beginning and processing stops. That is the only change I'm making.
> > 
> > <xsl:param name="double.sided" select="1"/>
> 
> Actually, I did see your first post, but didn't have a
> chance to respond.
> 
> I did some tests and found that some documents produce
> that error but others don't.  I couldn't figure out why.
> 
> But those that did produce the error in FOP 0.20.4
> did not generate the error in FOP 0.20.5rc.  I
> interpret that as a bug in FOP 0.20.4, but I can't
> be sure.





On Tue, 4 Mar 2003, Tim Waugh wrote:

> On Tue, Mar 04, 2003 at 05:48:11AM -0500, Robert P. J. Day wrote:
> 
> > and add it to the xmlto command with "-m", it has no effect.
> > is this because it's not an xsl:param, but an xsl:attribute-set?
> 
> The xmlto program doesn't interpret the fragments at all, just builds
> a temporary stylesheet file which includes all the fragments.
> 
> If you comment out the 'trap' line in /usr/bin/xmlto and run it with
> -v it will tell you the names of the temporary files it creates, and
> won't remove them at exit.

the temporary stylesheet looks fine -- an xsl:import and some
xsl:includes.  what's baffling me is that docbook markup that
rendered beautifully in HTML renders untelligibly or causes
the rendering to fail when trying to generate PDF.

some of the problems:

1) things which are types of lists fail to generate PDF at all
   if that list will be broken over a page (which is why i'm
   trying so hard to generate page breaks).  at least, that
   *seems* to be the problem since changing the contents of the
   document to shift the position of the list fixes the problem.

2) simple two-column tables aren't rendered in the PDF output at all

3) neither vertical or horizontal simple lists are rendered
   properly -- they appear as overstruck -- but inline simple
   lists look fine.

like i mentioned, i'm confused that simple docbook markup that
generated perfect HTML generates junk PDF or doesn't generate
anything.  puzzling.

rday







On Tue, Mar 04, 2003 at 10:42:12AM -0500, Robert P. J. Day wrote:

> the temporary stylesheet looks fine -- an xsl:import and some
> xsl:includes.  what's baffling me is that docbook markup that
> rendered beautifully in HTML renders untelligibly or causes the
> rendering to fail when trying to generate PDF.

Well, there is an extra step for PDF relative to HTML of course:
XSL-FO.  With current Red Hat Linux distributions you'll get
passivetex when using xmlto.

You could generate XSL-FO with 'xmlto fo -m ...' and try a different
XSL-FO processor than passivetex, to eliminate that and see if that's
the cause.

Tim.
*/

PGP signature





I've (mostly) implemented a customization of the DocBook stylesheets (for FO
output) that create page numbers where the numbering re-starts at each
chapter and is prefixed by the chapter number.  (e.g. page 4-13)  I wouldn't
consider this work "complete", but it's working pretty well for me so far.
Is anybody else interested in this sort of customization?  If enough people
are interested, maybe we can get a parameter into CVS.

Jeff Beal
Tools Specialist
ANSYS, Inc.
(724) 514-3150




On Tue, Mar 04, 2003 at 09:44:44AM -0800, Bob Stayton wrote:
> On Wed, Mar 05, 2003 at 12:23:35AM +1030, Paul A. Hoadley wrote:
> > I have some glossary entries where I want to include figures as part
> > of the 'glossdef'.  Some of the images are a little wide, so I have
> > used 'pgwide="1"' as an attribute of the 'figure' element.  The
> > figures are not, however, being centred within the page, but remain
> > centred within the blocks that compose the text of the 'glossdef'.
> > I've glanced over formal.xsl, and 'pgwide="1"' should induce a
> > 'span="all"' attribute on the fo:block in question.  This isn't
> > happening when the 'figure' is a child of 'glossdef' -- in fact, I
> > can't find a single 'span' attribute anywhere in the resulting FO
> > file.
> > 
> > Am I missing something here, or is this a bug?
> 
> Well, looking at the templates, the pgwide attribute is currently
> supported only for tables in the fo stylesheets.  That is a bug, so
> you could file a bug report on that.
> 
> But even if it is supported, I don't think it would do what you
> want.  The fo:span="all" property refers to spanning page columns.
> But glossentries are formatted with either fo:block or fo:list-item
> in a single page column.  Since the figure is part of the glossdef
> block, I don't think you can get it to center on the page without
> further intervention.

Interesting.  I may have to put the figure elsewhere, then, and refer
to it by label in the text.  Can anyone suggest an alternative?


-- 
Paul.

mailto:paulh@logicsquad.net
mailto:phoadley@maths.adelaide.edu.au




Hi
 
I have a question about versioning of DocBook documents.
 
Some Background Info:
I have a master copy of government legislation (called an Act)  in DocBook format. Now the guvment makes amendments to the Act (An amendment is a textual change to the original Act  - could  be  Addition, Removal or Modification of text). What I am required to do is supply a consolidated act (i.e The Original Act + all amendments) and also supply a means by which users can see the Act at a point in time.
 
For Example:
    Original Act published 27-Oct-2001
    Amendment 01 published 12-Dec-2001
    Amendment 02 published 15-July-2002
    Amendment 03 published 4-Dec-2002
 
Users want to see the Act
    (1) Original Form
    (2) Original Form + Amendment 01
    (3) Original Form + Amendment 02
    (3) Original Form + Amendment 03
    (4) Original Form + Amendment 04 = Fully Consolidated Act
 
It appears to be a similar problem to that of software version management.
 
Questions:
Does DocBook have any facility to manage this type of versioning?
Does anyone know of any tools that can be integrated into a current browser based application to solve this problem?
Does anyone have any idea of the best way to solve this problem?
 
 
Thanks in advance for any help given in this matter.
 
 
Regards
Mark Brand




Hi
 
I am trying to determine the optimum content representation for my project (displaying government legislation within a browser).
 
Why are the advantages / disadvantages to using TEI (Text Encoding Initiative) as opposed to DocBook.
 
 
Thanks again
 
 
Regards
Mark Brand
 




> I have a question about versioning of DocBook documents. 

> Some Background Info:
> I have a master copy of government legislation (called an Act)  in DocBook
format. Now the > guvment makes amendments to the Act (An amendment is a
textual change to the original Act  > - could  be  Addition, Removal or
Modification of text). What I am required to do is 
> supply a consolidated act (i.e The Original Act + all amendments) and also
supply a means > by which users can see the Act at a point in time. 
>
> It appears to be a similar problem to that of software version management.
>
That's quite right.

> Questions:
> Does DocBook have any facility to manage this type of versioning?
> Does anyone know of any tools that can be integrated into a current
browser based 
> application to solve this problem?
> Does anyone have any idea of the best way to solve this problem?

Perhaps you could use the 'role' attribute for this purpose, but you'll
probably end up duplicating parts of the text.

I'd suggest a version management tool like CVS (http://www.cvshome.org/). 

You could tag every version and check out the different versions into
different files / directories to create the documents from.

Regards
Gisbert Amm




Hi.

 

1) By default the first page generated on a PDF have only the book title, but I want to put a logo and a copyright on this same page. And have this page sequence: book title (first page), TOC, chapiter1.

 

2) After is it possible to no write the page number (Like IV ) in the footer of the TOC?

 

3) And my last problem is that I use a lot of screenshots in my PDF (and CHM), and the scaling function don’t work with FOP, have you any idea of how can I do this?

 

 Thanks

Guillaume Oblin

 





First you have to decide what kind of documents you
want to markup.

Docbook is a markup for technical documents, it has
many elements for this job and few for general text.

TEI or TEI2 designed to markup poems, romans, etc.
(designed for literature.)

In all of them you can structurise the document, insert
tables or emphasise texts, insert pictures, etc.

If your documents' not need special elements to markup
you can use both, but in this case i suggest you to
use docbook because the stylesheets are much better and
configurable then TEI's.

Mark Brand írta:
> Hi
>  
> I am trying to determine the optimum content representation for my 
> project (displaying government legislation within a browser).
>  
> Why are the advantages / disadvantages to using TEI (Text Encoding 
> Initiative) as opposed to DocBook.
>  
>  
> Thanks again
>  
>  
> Regards
> Mark Brand
>  






On Wed, Mar 05, 2003 at 12:23:35AM +1030, Paul A. Hoadley wrote:
> Hello,
> 
> I'm using XSL-FO stylesheets 1.60.0 and XEP to render PS and PDF.
> 
> I have some glossary entries where I want to include figures as part
> of the 'glossdef'.  Some of the images are a little wide, so I have
> used 'pgwide="1"' as an attribute of the 'figure' element.  The
> figures are not, however, being centred within the page, but remain
> centred within the blocks that compose the text of the 'glossdef'.
> I've glanced over formal.xsl, and 'pgwide="1"' should induce a
> 'span="all"' attribute on the fo:block in question.  This isn't
> happening when the 'figure' is a child of 'glossdef' -- in fact, I
> can't find a single 'span' attribute anywhere in the resulting FO
> file.
> 
> Am I missing something here, or is this a bug?

Well, looking at the templates, the pgwide attribute is
currently supported only for tables in the fo stylesheets.
That is a bug, so you could file a bug report on that.

But even if it is supported, I don't think it would do
what you want.  The fo:span="all" property refers to
spanning page columns.  But glossentries are formatted
with either fo:block or fo:list-item in a single page column.
Since the figure is part of the glossdef block, I don't
think you can get it to center on the page without
further intervention.

-- 

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: bobs@sco.com




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Powered by ezmlm-idx