Nabble - docbook apps

Re: [docbook] Add the book name to the title

2009-11-12T15:15:44Z

Thanks Bob!

For those people interested, here is the code I used to get the name
of the document and prepend it to the <title> information:

<xsl:variable name="my.title.parameter">
<xsl:call-template name="get.doc.title"/>
</xsl:variable>

<xsl:template name="head.content">
<xsl:param name="node" select="."/>
<xsl:param name="title">
<xsl:value-of select="$my.title.parameter"/>
<xsl:text>: </xsl:text>
<xsl:apply-templates select="$node" mode="object.title.markup.textonly"/>
</xsl:param>
.
.
.
More information is located at:
http://sourceware.org/ml/docbook-apps/2003-q1/msg00061.html

Thanks,
Jon

> On Thu, Nov 12, 2009 at 10:44 AM, Bob Stayton <bobs@...> wrote:
>> [moving this over to the docbook-apps mailing list where stylesheet issues
>> are discussed.]
>>
>> Hi Jon,
>> As you discovered, variable references in gentext are not processed. There
>> is a template named 'substitute.markup' in common/gentext.xsl that handles
>> replacing the % placeholders with generated text. You would need to
>> customize that template to resolve variable references.
>>
>> I would caution about adding the book title in the 'title-numbered' context,
>> as that gentext may be used in other places besides the HTML head title.
>> Instead, I would focus on the template where that HTML title element is
>> generated. That template is named 'head.content' and it is in
>> html/docbook.xsl. You could customize that template to add the book title.
>> A variable reference could be used there.
>>
>> Bob Stayton
>> Sagehill Enterprises
>> bobs@...
>>
>>
>> ----- Original Message ----- From: "Jon W" <knowdat@...>
>> To: <docbook@...>
>> Sent: Wednesday, November 11, 2009 9:28 AM
>> Subject: [docbook] Add the book name to the title
>>
>>
>>> Hi. Currently in the <title> section of our html, we list the number
>>> %n and title %t. We would like to pre-pend the name of the book to
>>> the <title> information, so the google search results contain the name
>>> of the book in the link.
>>>
>>> For example, if the name of the book is "My Book", the search would
>>> look similar to:
>>> My Book: 4.6.1 Jack and Jill go home
>>>
>>> I know about using local.l10n.xml to process generated text, but
>>> haven't found a way to use a variable in the <l:template> section. I
>>> would like to set the local.l10n.xml settings in a common xsl file
>>> that each of the 10 books can use the same xsl.
>>>
>>> Is there a way for a variable called $mybookname to be used in the
>>> local.l10n.xml settings? The following code does not expand the
>>> variable $mybookname:
>>>
>>> <xsl:param name="local.l10n.xml" select="document('')"/>
>>> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
>>> <l:l10n language="en">
>>> <l:context name="title-numbered">
>>> <l:template name="sect1" text="$mybookname %n. %t"/>
>>> </l:context>
>>> </l:l10n>
>>> </l:i18n>
>>>
>>>
>>> Here is the example of our current html, for which I would like to add
>>> the book name:
>>> <html>
>>> <head>
>>> <meta http-equiv="Content-Type" content="text/html;
>>> charset=ISO-8859-1">
>>> <title>4.6.1. Jack and Jill go home</title>
>>>
>>> Thank you,
>>> Jon
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: docbook-unsubscribe@...
>>> For additional commands, e-mail: docbook-help@...
>>>
>>>
>>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: [docbook] Add the book name to the title

2009-11-12T09:44:44Z

[moving this over to the docbook-apps mailing list where stylesheet issues
are discussed.]

Hi Jon,
As you discovered, variable references in gentext are not processed. There
is a template named 'substitute.markup' in common/gentext.xsl that handles
replacing the % placeholders with generated text. You would need to
customize that template to resolve variable references.

I would caution about adding the book title in the 'title-numbered' context,
as that gentext may be used in other places besides the HTML head title.
Instead, I would focus on the template where that HTML title element is
generated. That template is named 'head.content' and it is in
html/docbook.xsl. You could customize that template to add the book title.
A variable reference could be used there.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----
From: "Jon W" <knowdat@...>
To: <docbook@...>
Sent: Wednesday, November 11, 2009 9:28 AM
Subject: [docbook] Add the book name to the title

> Hi. Currently in the <title> section of our html, we list the number
> %n and title %t. We would like to pre-pend the name of the book to
> the <title> information, so the google search results contain the name
> of the book in the link.
>
> For example, if the name of the book is "My Book", the search would
> look similar to:
> My Book: 4.6.1 Jack and Jill go home
>
> I know about using local.l10n.xml to process generated text, but
> haven't found a way to use a variable in the <l:template> section. I
> would like to set the local.l10n.xml settings in a common xsl file
> that each of the 10 books can use the same xsl.
>
> Is there a way for a variable called $mybookname to be used in the
> local.l10n.xml settings? The following code does not expand the
> variable $mybookname:
>
> <xsl:param name="local.l10n.xml" select="document('')"/>
> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
> <l:l10n language="en">
> <l:context name="title-numbered">
> <l:template name="sect1" text="$mybookname %n. %t"/>
> </l:context>
> </l:l10n>
> </l:i18n>
>
>
> Here is the example of our current html, for which I would like to add
> the book name:
> <html>
> <head>
> <meta http-equiv="Content-Type" content="text/html;
> charset=ISO-8859-1">
> <title>4.6.1. Jack and Jill go home</title>
>
> Thank you,
> Jon
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe@...
> For additional commands, e-mail: docbook-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: space between chapter number and chapter text?

2009-11-12T00:46:14Z

This is obviously a better way to do it. And there is no need to redefine the gentexts anymore.
Works just fine.
Thanks!

Johannes

Am 11.11.2009 um 18:04 schrieb Bob Stayton:

> Hi,
> If you want to position the title at a constant distance from the left margin, regardless of the width of the chapter number, then you can use an fo:list-block. I called it 'side-by-side' formatting, and an example for section titles is described here:
>
> http://www.sagehill.net/docbookxsl/SideBySide.html
>
> The trick is to use mode="label.markup" to generate just the chapter number and mode="title.markup" to generate just the title, putting each in a separate part of the fo:list-item.
>
> Bob Stayton
> Sagehill Enterprises
> bobs@...
>
>
> ----- Original Message ----- From: "Johannes Katelaan" <jk@...>
> To: <docbook-apps@...>
> Sent: Wednesday, November 11, 2009 6:23 AM
> Subject: Re: [docbook-apps] space between chapter number and chapter text?
>
>
> OK - I found a solution myself. I don't know if this is the best way to do it, but it works fine for me.
> In case somebody is interested in my solution, here it is:
>
> Change the customization layer for the chapter and section titles as follows:
>
> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
> <l:l10n language="de">
> <l:context name="title-numbered">
> <l:template name="chapter" text="%n|%t"/>
> <l:template name="sect1" text="%n|%t"/>
> <l:template name="sect2" text="%n|%t"/>
> </l:context>
> </l:l10n>
> </l:i18n>
>
> This adds a pipe character as a separator between the chapter or section number and the text.
>
> Copy the template "component.title" to the customization layer stylesheet and modify the end of this template as follows:
>
> <xsl:otherwise>
> 
> 
> 
> 
> <fo:inline>
> <xsl:copy-of select="substring-before($title,'|')"/>
> </fo:inline>
> <fo:inline space-start="15mm">
> <xsl:copy-of select="substring-after($title,'|')"/>
> </fo:inline>
> </xsl:otherwise>
>
> Copy the template "section.heading" to the customization layer stylesheet and modify as follows:
>
> <xsl:choose>
> <xsl:when test="$level=1">
> <fo:block xsl:use-attribute-sets="section.title.level1.properties">
> 
> 
> 
> <fo:inline>
> <xsl:copy-of select="substring-before($title,'|')"/>
> </fo:inline>
> <fo:inline space-start="11.5mm">
> <xsl:copy-of select="substring-after($title,'|')"/>
> </fo:inline>
> </fo:block>
> </xsl:when>
> <xsl:when test="$level=2">
> <fo:block xsl:use-attribute-sets="section.title.level2.properties">
> 
> 
> 
> <fo:inline>
> <xsl:copy-of select="substring-before($title,'|')"/>
> </fo:inline>
> <fo:inline space-start="10mm">
> <xsl:copy-of select="substring-after($title,'|')"/>
> </fo:inline>
> </fo:block>
> </xsl:when>
>
> Yes, the space between the number and the text is hard-coded and this will break, if the font sizes for chapter and section titles are changed.
> A better solution would be to position the title text relative to the left border of the page. But I don't know how to do this.
>
> Johannes
>
> Am 11.11.2009 um 10:16 schrieb Johannes Katelaan:
>
>> Hi!
>>
>> In my customization layer I changed the chapter titles as follows:
>>
>> <xsl:param name="local.l10n.xml" select="document('')"/>
>> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
>> <l:l10n language="de">
>> <l:context name="title-numbered">
>> <l:template name="chapter" text="%n %t"/>
>> </l:context>
>> </l:l10n>
>> </l:i18n>
>>
>> I did this to get rid of the word "Kapitel" in the German chapter title. This work fine. So I get chapter titles in the form "number and text" now.
>>
>> My question: Is it possible to change the amount of space between the number and the text? I tried to insert additional space characters between the %n and the %t, but this had no effect at all.
>>
>> In my final layout I intend to have something like this:
>>
>> 1 title chapter one
>> 1.1 title section level one
>> 1.1.1 title section level two
>>
>> with all the texts starting at the same distance from the left border of the paper.
>>
>> Is this possible?
>>
>> Johannes
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-apps-unsubscribe@...
>> For additional commands, e-mail: docbook-apps-help@...
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@...
> For additional commands, e-mail: docbook-apps-help@...
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

How to use a image blob into a docbook ?

2009-11-11T12:07:15Z

Hi to all,

everybody knows, to insert an image to a docbook document have to use this example below

<figure><title>Notre Dame Cathedral</title>
<graphic srccredit="Norman Walsh, 1998" fileref="figures/notredame.png"/>
</figure>

Now
I want to insert an image to a docbook document but the image come from a blob field and I want not to use a temp files.
how to do ?
is possible to use a base64 encoded stream as input instead of the file?

Thanks
bye

Re: compiling a book without the chapter level

2009-11-11T11:29:39Z

Hi,

You can avoid creating a TOC by setting the stylesheet parameter 'generate.toc' to empty.

Regarding the structure, you could include a single article element in your book and leave its title element empty. The article would produce the fo:page-sequence you need to avoid the errors.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----

From: nancy_brndt@...

To: docbook-apps@...

Sent: Wednesday, November 11, 2009 9:03 AM

Subject: [docbook-apps] compiling a book without the chapter level

Hi all,

I need to compile a book-like document without using the <chapter> levels. I use <bridgehead> tags only to avoid creating a TOC. However, the compiler fails to produce a PDF complaining on the missing fo:child elements (as expected).]

Is it possible to compile a <book> without using <chapters>?

Thanks in advance!
Nancy

Image overflows

2009-11-11T10:15:35Z

Hi,

Recently I had a problem with image overflows using Apache as well as XEP.

I use both very wide and very high images in my documentation. When
applying my customization layers they are always scaled to match the
width of the page but I have problems if the image is still to high to
match the available page space/size.

Using Apache images are just rendered on top of the page ignoring the
page master setup (so above header, body, footer, starter ...) not
fitting into the available area in the body.
Using XEP there is just some information in the logs stating that XEP
was not able to satisfy the constraints and (!!!) does not print the
image at all.

I use <d:imagedata width="100%" contentdepth="100%" .../> in docbook.
Is there a way to enable some kind of auto-fit functionality? In a
customization layer producing some kind of powerpoint slide layout I
overwrote the graphic template to set the (maximum) height. Now,
i) very wide but not that high images are scaled to fit the available width (OK)
ii) very high but not very wide images are scaled to fit the available
height (OK)
iii) small images are upscaled to match height or respectively the
width (NOT REALLY OK)

Do somebody have a solution for point iii ?

Cheers,
Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Customizing xref to a listitem

2009-11-11T09:39:42Z

Hi,

I'm not understanding the context of this template. I presume your input document has non-DocBook <jlistref> elements so the template matches on that element, right? Then it generates DocBook <phrase> and <xref> elements. Don't those appear in the FO and HTML outputs? That's what I would expect if this template appears in a DocBook XSL customization layer. Are you somehow subsequently processing these generated DocBook elements with additional templates? Perhaps you can describe a bit more of how you are using this template.

In any case, there is an easier way to customize the text in cross references. Have you tried customizing the gentext string used in the stylesheet? That process is described here:

http://www.sagehill.net/docbookxsl/CustomXrefs.html#XrefGentext

You would customize the @text attribute inside <l:template name="listitem"> in context <l:context name="xref">. You would do this in your HTML customization layer and your PDF customization layer, using different text strings.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----

From: nancy_brndt@...

To: docbook-apps@...

Sent: Wednesday, November 11, 2009 7:33 AM

Subject: [docbook-apps] Customizing xref to a listitem

Hi folks,

I am trying to customize references to listitems as follows:

<xsl:template match="jlistref">
<phrase status="print">
<xref>
<xsl:copy-of select="@*"/>
<xsl:attribute name="linkend">
<xsl:copy-of select="@*"/>
<xsl:value-of select="@ref"/>
</xsl:attribute>

<xsl:attribute name="xrefstyle">
<xsl:value-of select="'template:Step %n on page %p'"/>
</xsl:attribute>
</xref>
</phrase>

<phrase status="html">
<xref>
<xsl:copy-of select="@*"/>
<xsl:attribute name="linkend">
<xsl:copy-of select="@*"/>
<xsl:value-of select="@ref"/>
</xsl:attribute>

<xsl:attribute name="xrefstyle">
<xsl:value-of select="'template:Step %n'"/>
</xsl:attribute>
</xref>
</phrase>
</xsl:template>

So that when I compile a PDF, an xref will look like as follows:

refer to Step <number> on page <number>.

In HTML, though, it must be just: Step <number>

However, the template above does not affect anything. The reference appears as default.

Please, advise!

Thanks a lot in advance!

Nancy

RE: automated keywords and chunking

2009-11-11T09:12:49Z

Thanks Tim,
That helps. In addition to chunk.section.depth, there are some other mechanisms for controlling chunking. One is a PI that lets you stop chunking at an arbitrary point and another is the param chunk.first.sections which lets you control whether the first child section is treated as a separate chunk. I also figure that <keyword>s should be included in the html keywords. Perhaps subjectset/subject should be included too? Anyway, I've added support for that stuff and pasted my version below.

The only other mechanism for controlling chunking that's not yet accounted for is the manual method described here http://www.sagehill.net/docbookxsl/Chunking.html (under "Manually control chunking"). I don't know much about that mechanism and don't know if it could be accounted for easily.

Oh, this also doesn't yet support sect1-style sections, just recursive sections.

David

<xsl:template name="keywordset">

<xsl:variable name="section_level">
<xsl:number value="count(ancestor-or-self::section)"/>
</xsl:variable>


<xsl:variable name="indexterms-and-keywords">
<xsl:choose>
<xsl:when test="$section_level = $chunk.section.depth or ancestor-or-self::*/processing-instruction('dbhtml')[normalize-space(.) ='stop-chunking']">
<xsl:copy-of select=".//indexterm/primary"/>
<xsl:copy-of select=".//keywordset/keyword"/>
</xsl:when>
<xsl:when test="$chunk.first.sections = '0'">
<xsl:copy-of select="./*[not(self::section)]//indexterm/primary|./section[1]//indexterm/primary|./indexterm/primary"/>
<xsl:copy-of select="./*[not(self::section)]//keywordset/keyword|./section[1]//keywordset/keyword|./keywordset/keyword"/>
</xsl:when>
<xsl:otherwise>
<xsl:copy-of select="./*[not(self::section)]//indexterm/primary|./indexterm/primary"/>
<xsl:copy-of select="./*[not(self::section)]//keywordset/keyword|./keywordset/keyword"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>


<xsl:variable name="indexterms-and-keywords-unique">
<xsl:for-each select="exslt:node-set($indexterms-and-keywords)/*[not(. = preceding-sibling::*)]">
<xsl:value-of select="normalize-space(.)"/><xsl:if test="not(position() = last())">, </xsl:if>
</xsl:for-each>
</xsl:variable>


<xsl:if test="not($indexterms-and-keywords-unique = '')">
<meta name="keywords">
<xsl:attribute name="content">
<xsl:value-of select="$indexterms-and-keywords-unique" />
</xsl:attribute>
</meta>
</xsl:if>

</xsl:template>

> -----Original Message-----
> From: Tim Arnold [mailto:Tim.Arnold@...]
> Sent: Friday, September 25, 2009 1:29 PM
> To: DocBook Apps
> Subject: RE: [docbook-apps] automated keywords and chunking
>
> Hi Bob,
> Yes that footnote processing code is pretty complex. I took a
> stab at this first, basing my ideas on the code David sent
> earlier. It works for my toy examples, but maybe it's naïve
> or only works for my situation. To repeat the original problem:
> I'd like to automatically create keywords for each output
> file that consist of the primary index terms in that file.
>
> <xsl:template name="user.head.content">
> <xsl:call-template name="keywordset"/>
> </xsl:template>
>
> 
>
> <xsl:template name="keywordset">
> 
> <xsl:variable name="section_level">
> <xsl:number value="count(ancestor-or-self::d:section)"/>
> </xsl:variable>
>
> 
> <xsl:variable name="indexterms">
> <xsl:choose>
> <xsl:when test="$section_level = $chunk.section.depth">
> <xsl:copy-of select=".//d:indexterm/d:primary"/>
> </xsl:when>
> <xsl:otherwise>
> <xsl:copy-of
> select="./*[not(self::d:section)]//d:indexterm/d:primary|./d:i

ndexterm/d:primary"/>

> </xsl:otherwise>
> </xsl:choose>
> </xsl:variable>
>
> 
> <xsl:variable name="indexterms-unique">
> <xsl:for-each select="exslt:node-set($indexterms)/*[not(.
> = preceding-sibling::*)]">
> <xsl:value-of select="normalize-space(.)"/><xsl:if
> test="not(position() = last())">, </xsl:if>
> </xsl:for-each>
> </xsl:variable>
>
> 
> <xsl:if test="not($indexterms-unique = '')">
> <meta name="keywords">
> <xsl:attribute name="content">
> <xsl:value-of select="$indexterms-unique" />
> </xsl:attribute>
> </meta>
> </xsl:if>
>
> </xsl:template>
>
> > -----Original Message-----
> > From: Bob Stayton [mailto:bobs@...]
> > Sent: Thursday, September 24, 2009 1:04 PM
> > To: Tim Arnold; DocBook Apps
> > Subject: Re: [docbook-apps] automated keywords and chunking
> >
> > Actually, David is correct, and it is more complicated than I
> > originally stated.. The context node when user.head.content
> is called
> > is a chunked section element, but it also includes *all* of its
> > children, including the sections that will be in their own
> chunks and
> > should not be processed for the keywords for the current chunk.
> >
> > The chunking process works by recursive chunking. That is,
> when the
> > current section is chunked, it is processed until a child
> section is
> > reached, at which point the processor will recursively start a new
> > chunk on that, and so on. Only when the last nested section is
> > chunked is the original chunk finished off.
> >
> > This makes it very difficult to detect which indexterms are
> contained
> > in the current chunk by just using XPath from the top of a
> chunk element.
> >
> > Footnote processing in chunked output has a similar problem, as the
> > footnote list at the end of a chunk should only include
> those footnote
> > elements within the current chunk text, not the child
> sections. See
> > the template named 'process.chunk.footnotes' in
> html/chunk-common.xsl
> > and follow where it goes to see how that works to exclude
> footnotes from other chunks.
> >
> > Bob Stayton
> > Sagehill Enterprises
> > bobs@...
> >
> >
> > ----- Original Message -----
> > From: "Tim Arnold" <a_jtim@...>
> > To: "DocBook Apps" <docbook-apps@...>
> > Sent: Thursday, September 24, 2009 6:03 AM
> > Subject: [docbook-apps] Fwd: failure notice
> >
> >
> > >> Thanks you both for thinking about this. Sorry I
> originally posted
> > >> to the wrong group--I'm still learning my way around. From the
> > >> looks of the project in front of me, my copy of Bob's
> book is going
> > >> to be dog- eared soon.
> > >>
> > >> I think David is right for my case--I'm chunking down to
> the third
> > >> section level and I only want the keywords that are
> actually in the
> > >> current html file. Otherwise I would be messing up the search
> > >> engines by advertising keywords that are not actually present in
> > >> the file. But on re-reading Bob's message, I see that that's
> > >> already taken care of since user.head.content is called
> with the node being chunked.
> > >>
> > >> I'm pretty sure my head will hurt before it's over, but
> I'll play
> > >> around with it and step though the code; it looks very close to
> > >> what I'll need to do. Thanks for the inspiration!
> > >> --Tim Arnold
> > >>
> > >> On Sep 23, 2009, at 1:39 PM, David Cramer wrote:
> > >>
> > >>> Tim may have to worry about chunking and the chunking
> settings,
> > >>> depending on his situation. Say you chunk everything.
> If you have
> > >>> a chapter with several subsections, then the first
> chunk contains
> > >>> the chapter's toc and any content before the first section. You
> > >>> probably don't want that chunk's html page to have all of the
> > >>> indexterms in the all of the child sections. Or if you stop
> > >>> chunking at a certain depth, you DO want the section
> at which you
> > >>> stop chunking to contain keywords for the indexterms
> of all its
> > >>> child sections. If he uses <?bjhtml stop-chunking?> to stop
> > >>> chunking at arbitrary places, then that would have to
> be addressed too.
> > >>>
> > >>> I wanted to do something similar to what Tim is asking
> for, but
> > >>> didn't go to the trouble of addressing all those
> because it made
> > >>> my head hurt.
> > >>>
> > >>> If I recall correctly, the following tries to assemble a
> > >>> keywordset unless there already is a keywordset and
> gets all the
> > >>> indexterms in the chapter or section but not get any from any
> > >>> child sections. It also removes duplicate index entries.
> > >>>
> > >>> Anyway, perhaps the following can be a starting point
> or source of
> > >>> inspiration.
> > >>>
> > >>> David
> > >>>
> > >>> <xsl:template name="user.head.content"> <xsl:call-template
> > >>> name="keywordset"/> </xsl:template>
> > >>>
> > >>> <xsl:template name="keywordset">
> > >>> <xsl:if test="not(self::book) and not(self::part) and
> > >>> not(./*/keywordset) and
> > >>> (./*[not(starts-with(local-name(.),'sect'))
> > >>> and
> > >>> not(self::chapter)]//indexterm or ./indexterm)">
> > >>> <xsl:variable name="indexterms">
> > >>>  <xsl:copy-of
> > >>> select="./*[not(self::section)]//indexterm/*|./indexterm/*"/>
> > >>> </xsl:variable>
> > >>> <xsl:variable name="indexterms-unique"> <xsl:for-each
> > >>> select="exslt:node-set($indexterms)/*[not(. =
> preceding- sibling::*)]">
> > >>> <xsl:value-of select="normalize-space(.)"/><xsl:if
> > >>> test="not(position() = last())">, </xsl:if> </xsl:for-each>
> > >>> </xsl:variable>
> > >>> <xsl:if test="not($indexterms-unique = '')"> <meta
> > >>> name="keywords">
> > >>> <xsl:attribute name="content">
> > >>> <xsl:value-of select="$indexterms-unique"/>
> > >>> </xsl:attribute>
> > >>> </meta>
> > >>> </xsl:if>
> > >>> </xsl:if>
> > >>> </xsl:template>
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: Bob Stayton [mailto:bobs@...]
> > >>>> Sent: Wednesday, September 23, 2009 11:11 AM
> > >>>> To: DocBook Apps; Tim Arnold
> > >>>> Subject: [docbook-apps] Re: [docbook] automated keywords and
> > >>>> chunking
> > >>>>
> > >>>> [moving this over to docbook-apps mailing list where
> stylesheet
> > >>>> issues are discussed]
> > >>>>
> > >>>> By keywords I presume you mean generating <meta
> name="keywords">
> > >>>> in the HEAD element of each chunks? If so, then you
> don't have
> > >>>> to mess with the chunking machinery, you can use the
> placeholder
> > >>>> template named 'user.head.content'
> > >>>> that is available for inserting custom content. See:
> > >>>>
> > >>>> http://www.sagehill.net/docbookxsl/HtmlHead.html
> > >>>>
> > >>>> That template is called with the node being chunked as the
> > >>>> context node, so you should be able to select
> > >>>> descendant::indexterm/primary elements and process
> them into the
> > >>>> value of the meta element.
> > >>>>
> > >>>> Bob Stayton
> > >>>> Sagehill Enterprises
> > >>>> bobs@...
> > >>>>
> > >>>>
> > >>>> ----- Original Message -----
> > >>>> From: "Tim Arnold" <a_jtim@...>
> > >>>> To: <docbook@...>
> > >>>> Sent: Tuesday, September 22, 2009 4:35 PM
> > >>>> Subject: [docbook] automated keywords and chunking
> > >>>>
> > >>>>
> > >>>>> Hi,
> > >>>>> I'm using DocBook 5 and the html chunking
> stylesheets. I'd like
> > >>>>> to automatically create keywords for each output file that
> > >>>> consist of the
> > >>>>> primary index terms in that file. I can manage that in
> > >>>> postprocessing
> > >>>>> using Python and lxml, but I wanted to ask here to see if
> > >>>> this has been
> > >>>>> done before. It seems like something people might like to
> > >>>> do, but after
> > >>>>> looking at the chunking code and reading about it, it
> > >>>> sounds like it
> > >>>>> might be pretty complicated to implement.
> > >>>>>
> > >>>>> Any ideas on this?
> > >>>>> thanks,
> > >>>>> --Tim Arnold
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> -----------------------------------------------------------------
> > >>>> ----
> > >>>>> To unsubscribe, e-mail:
> docbook-unsubscribe@...
> > >>>>> For additional commands, e-mail:
> > >>>>> docbook-help@...
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>>
> -----------------------------------------------------------------
> > >>>> ---- To unsubscribe, e-mail:
> > >>>> docbook-apps-unsubscribe@...- open.org For additional
> > >>>> commands, e-mail:
> > >>>> docbook-apps-help@...
> > >>>>
> > >>>>
> > >>
> > >
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail:
> > > docbook-apps-unsubscribe@...
> > > For additional commands, e-mail:
> > > docbook-apps-help@...
> > >
> > >
> > >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> docbook-apps-unsubscribe@...
> > For additional commands, e-mail:
> > docbook-apps-help@...
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@...
> For additional commands, e-mail:
> docbook-apps-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: space between chapter number and chapter text?

2009-11-11T09:04:24Z

Hi,
If you want to position the title at a constant distance from the left
margin, regardless of the width of the chapter number, then you can use an
fo:list-block. I called it 'side-by-side' formatting, and an example for
section titles is described here:

http://www.sagehill.net/docbookxsl/SideBySide.html

The trick is to use mode="label.markup" to generate just the chapter number
and mode="title.markup" to generate just the title, putting each in a
separate part of the fo:list-item.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----
From: "Johannes Katelaan" <jk@...>
To: <docbook-apps@...>
Sent: Wednesday, November 11, 2009 6:23 AM
Subject: Re: [docbook-apps] space between chapter number and chapter text?

OK - I found a solution myself. I don't know if this is the best way to do
it, but it works fine for me.
In case somebody is interested in my solution, here it is:

Change the customization layer for the chapter and section titles as
follows:

<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
<l:l10n language="de">
<l:context name="title-numbered">
<l:template name="chapter" text="%n|%t"/>
<l:template name="sect1" text="%n|%t"/>
<l:template name="sect2" text="%n|%t"/>
</l:context>
</l:l10n>
</l:i18n>

This adds a pipe character as a separator between the chapter or section
number and the text.

Copy the template "component.title" to the customization layer stylesheet
and modify the end of this template as follows:

<xsl:otherwise>




<fo:inline>
<xsl:copy-of select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="15mm">
<xsl:copy-of select="substring-after($title,'|')"/>
</fo:inline>
</xsl:otherwise>

Copy the template "section.heading" to the customization layer stylesheet
and modify as follows:

<xsl:choose>
<xsl:when test="$level=1">
<fo:block
xsl:use-attribute-sets="section.title.level1.properties">



<fo:inline>
<xsl:copy-of
select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="11.5mm">
<xsl:copy-of
select="substring-after($title,'|')"/>
</fo:inline>
</fo:block>
</xsl:when>
<xsl:when test="$level=2">
<fo:block
xsl:use-attribute-sets="section.title.level2.properties">



<fo:inline>
<xsl:copy-of
select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="10mm">
<xsl:copy-of
select="substring-after($title,'|')"/>
</fo:inline>
</fo:block>
</xsl:when>

Yes, the space between the number and the text is hard-coded and this will
break, if the font sizes for chapter and section titles are changed.
A better solution would be to position the title text relative to the left
border of the page. But I don't know how to do this.

Johannes

Am 11.11.2009 um 10:16 schrieb Johannes Katelaan:

> Hi!
>
> In my customization layer I changed the chapter titles as follows:
>
> <xsl:param name="local.l10n.xml" select="document('')"/>
> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
> <l:l10n language="de">
> <l:context name="title-numbered">
> <l:template name="chapter" text="%n %t"/>
> </l:context>
> </l:l10n>
> </l:i18n>
>
> I did this to get rid of the word "Kapitel" in the German chapter title.
> This work fine. So I get chapter titles in the form "number and text" now.
>
> My question: Is it possible to change the amount of space between the
> number and the text? I tried to insert additional space characters between
> the %n and the %t, but this had no effect at all.
>
> In my final layout I intend to have something like this:
>
> 1 title chapter one
> 1.1 title section level one
> 1.1.1 title section level two
>
> with all the texts starting at the same distance from the left border of
> the paper.
>
> Is this possible?
>
> Johannes
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@...
> For additional commands, e-mail: docbook-apps-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

compiling a book without the chapter level

2009-11-11T09:03:24Z

Hi all,

I need to compile a book-like document without using the <chapter> levels. I use <bridgehead> tags only to avoid creating a TOC. However, the compiler fails to produce a PDF complaining on the missing fo:child elements (as expected).]

Is it possible to compile a <book> without using <chapters>?

Thanks in advance!
Nancy

Customizing xref to a listitem

2009-11-11T07:33:23Z

Hi folks,

I am trying to customize references to listitems as follows:

<xsl:template match="jlistref">
<phrase status="print">
<xref>
<xsl:copy-of select="@*"/>
<xsl:attribute name="linkend">
<xsl:copy-of select="@*"/>
<xsl:value-of select="@ref"/>
</xsl:attribute>

<xsl:attribute name="xrefstyle">
<xsl:value-of select="'template:Step %n on page %p'"/>
</xsl:attribute>
</xref>
</phrase>

<phrase status="html">
<xref>
<xsl:copy-of select="@*"/>
<xsl:attribute name="linkend">
<xsl:copy-of select="@*"/>
<xsl:value-of select="@ref"/>
</xsl:attribute>

<xsl:attribute name="xrefstyle">
<xsl:value-of select="'template:Step %n'"/>
</xsl:attribute>
</xref>
</phrase>
</xsl:template>

So that when I compile a PDF, an xref will look like as follows:

refer to Step <number> on page <number>.

In HTML, though, it must be just: Step <number>

However, the template above does not affect anything. The reference appears as default.

Please, advise!

Thanks a lot in advance!

Nancy

Re: space between chapter number and chapter text?

2009-11-11T06:23:34Z

OK - I found a solution myself. I don't know if this is the best way to do it, but it works fine for me.
In case somebody is interested in my solution, here it is:

Change the customization layer for the chapter and section titles as follows:

<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
<l:l10n language="de">
<l:context name="title-numbered">
<l:template name="chapter" text="%n|%t"/>
<l:template name="sect1" text="%n|%t"/>
<l:template name="sect2" text="%n|%t"/>
</l:context>
</l:l10n>
</l:i18n>

This adds a pipe character as a separator between the chapter or section number and the text.

Copy the template "component.title" to the customization layer stylesheet and modify the end of this template as follows:

<xsl:otherwise>




<fo:inline>
<xsl:copy-of select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="15mm">
<xsl:copy-of select="substring-after($title,'|')"/>
</fo:inline>
</xsl:otherwise>

Copy the template "section.heading" to the customization layer stylesheet and modify as follows:

<xsl:choose>
<xsl:when test="$level=1">
<fo:block xsl:use-attribute-sets="section.title.level1.properties">



<fo:inline>
<xsl:copy-of select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="11.5mm">
<xsl:copy-of select="substring-after($title,'|')"/>
</fo:inline>
</fo:block>
</xsl:when>
<xsl:when test="$level=2">
<fo:block xsl:use-attribute-sets="section.title.level2.properties">



<fo:inline>
<xsl:copy-of select="substring-before($title,'|')"/>
</fo:inline>
<fo:inline space-start="10mm">
<xsl:copy-of select="substring-after($title,'|')"/>
</fo:inline>
</fo:block>
</xsl:when>

Yes, the space between the number and the text is hard-coded and this will break, if the font sizes for chapter and section titles are changed.
A better solution would be to position the title text relative to the left border of the page. But I don't know how to do this.

Johannes

Am 11.11.2009 um 10:16 schrieb Johannes Katelaan:

> Hi!
>
> In my customization layer I changed the chapter titles as follows:
>
> <xsl:param name="local.l10n.xml" select="document('')"/>
> <l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
> <l:l10n language="de">
> <l:context name="title-numbered">
> <l:template name="chapter" text="%n %t"/>
> </l:context>
> </l:l10n>
> </l:i18n>
>
> I did this to get rid of the word "Kapitel" in the German chapter title. This work fine. So I get chapter titles in the form "number and text" now.
>
> My question: Is it possible to change the amount of space between the number and the text? I tried to insert additional space characters between the %n and the %t, but this had no effect at all.
>
> In my final layout I intend to have something like this:
>
> 1 title chapter one
> 1.1 title section level one
> 1.1.1 title section level two
>
> with all the texts starting at the same distance from the left border of the paper.
>
> Is this possible?
>
> Johannes
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@...
> For additional commands, e-mail: docbook-apps-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

space between chapter number and chapter text?

2009-11-11T01:16:25Z

Hi!

In my customization layer I changed the chapter titles as follows:

<xsl:param name="local.l10n.xml" select="document('')"/>
<l:i18n xmlns:l="http://docbook.sourceforge.net/xmlns/l10n/1.0">
<l:l10n language="de">
<l:context name="title-numbered">
<l:template name="chapter" text="%n %t"/>
</l:context>
</l:l10n>
</l:i18n>

I did this to get rid of the word "Kapitel" in the German chapter title. This work fine. So I get chapter titles in the form "number and text" now.

My question: Is it possible to change the amount of space between the number and the text? I tried to insert additional space characters between the %n and the %t, but this had no effect at all.

In my final layout I intend to have something like this:

1 title chapter one
1.1 title section level one
1.1.1 title section level two

with all the texts starting at the same distance from the left border of the paper.

Is this possible?

Johannes

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Re: About imageobjectco, callout and title placement

2009-11-06T13:21:25Z

Hi Jacques,

Friday 06 November 2009

> On 6 nov. 2009, at 17:16, Jacques Foucry wrote:
>
> I'm sorry !
>
> > How can I change the title placement in this case ?
>
> After re-re-reading the source, I've misplaced the </figure>, after
> the </calloulist>.

Just to note: Norm wrote a very interesting article about image callouts. Find
it here:

http://norman.walsh.name/2006/06/10/imageobjectco

Maybe it's useful for your adventure with callouts. :-)

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: About imageobjectco, callout and title placement

2009-11-06T12:39:26Z

On 6 nov. 2009, at 17:16, Jacques Foucry wrote:

I'm sorry !

> How can I change the title placement in this case ?

After re-re-reading the source, I've misplaced the </figure>, after
the </calloulist>.

Sorry !

Jacques

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

About imageobjectco, callout and title placement

2009-11-06T08:16:55Z

Hello every body,

Today I tried to use figure and imageobjectco in a different way as I
did before.

<figure>
<info><title>This is a title</title><info>
<mediaobject>
<imageobjectco>
<areaspec>
<area coords="" xml:id="first"/>
<area coords="" xml:id="second"/>
</areaspec>
<imageobject>
<imagedata fileref="path/to/the/image"/>
</imageobject>
</imageobject>
</mediaobject>
</figure>
<calloutlist>
<callout arearefs="first">
<para>The first callout bug</para>
</callout>
<callout arearefs="seconde">
<para>The second callout bug</para>
</callout>
</calloutlist>

In my custom stylesheet I've put :
<xsl:param name="formal.title.placement">figure after</xsl:param>

As result of this little sample, the title of the figure is below the
callout list, and I prefer have it juste after the image it self.

I use Docbook 5.0 with 1.75.2 ns stylesheet.

How can I change the title placement in this case ?

Thanks in advance,
Jacques

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

RE: Re: Table cell text overlapes with table border ...docbook 1.74.3

2009-11-05T10:25:14Z

Hi Bela,

This is a pretty common problem when adding technical data to tables, since hyphenation tables/algorithims don't apply to non-standard things like long field names.

The way to handle it is to treat the contents of your table entries like they were URLs (which also bugger up hyphenation). The following template introduces soft hyphens between every letter of every table entry:

<xsl:template name="hyphenate-tableentries">
<xsl:param name="entry" select="''"/>
<xsl:choose>
<xsl:when test="$tableentry.hyphenate = ''">
<xsl:value-of select="$entry"/>
</xsl:when>
<xsl:when test="string-length($entry) > 1">
<xsl:variable name="char" select="substring($entry, 1, 1)"/>
<xsl:value-of select="$char"/>
<xsl:if test="contains($tableentry.hyphenate.chars, $char)">

<xsl:if test="not($char = '/' and substring($entry,2,1) = '/')">
<xsl:copy-of select="$tableentry.hyphenate"/>
</xsl:if>
</xsl:if>

<xsl:call-template name="hyphenate-tableentries">
<xsl:with-param name="entry" select="substring($entry, 2)"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$entry"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>

<xsl:param name="tableentry.hyphenate.chars">_.-/&</xsl:param>
<xsl:param name="tableentry.hyphenate"></xsl:param>

<xsl:template match="entry//text()">
<xsl:call-template name="hyphenate-tableentries">
<xsl:with-param name="entry" select="."/>
</xsl:call-template>
</xsl:template>

I forget who showed me this (someone on this list, I'm sure; think it might have actually been Bob Stayton), but I know I can't take credit for it.

Cheers,
Jeff.

-----Original Message-----
From: Vincent Hennebert [mailto:vhennebert@...]
Sent: Tuesday, October 27, 2009 8:54 AM
To: docbook-apps@...
Subject: Re: [docbook-apps] Re: Table cell text overlapes with table
border ...docbook 1.74.3

Hi,

Bela Patel wrote:

> On Tue, Oct 27, 2009 at 10:36 AM, Bela Patel <belaramani@...> wrote:
>
>> Vincent,
>>
>> I dont quite understand what you are suggesting.
>>
>> I just want the text to automatically break in next line within the cell
>> depending on the cell size so that it does not overlap with Table border.
>>
>> Can you please explain this?

You have to insert those characters wherever you are happy for the text
to break, possibly between every letter. The XSL-FO processor will then
choose one of those places to break the text into two lines. For
example:
ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789ABCDEFGHIJKLMNO

Basically by inserting that character (or the soft hyphen), you’re
giving the XSL-FO processor opportunities to break the text. The more of
those there are, the less risk there is that the text is going to
overlap the cell. Ideally you would somehow automate that process,
inserting those characters by hand is obviously tedious.

HTH,
Vincent

>> Thanks,
>> BRAMANI.
>>
>> On Tue, Oct 27, 2009 at 5:55 AM, Vincent Hennebert <vhennebert@...
>>> wrote:
>>> Hi,
>>>
>>> Since it’s not a regular word it can’t be hyphenated; you must specify
>>> yourself the places where it is allowed to break. If you want a hyphen
>>> to be visible when the text is broken you can use the soft hyphen
>>> character (U+00AD). Otherwise you can use a zero-width space (U+200B).
>>>
>>> HTH,
>>> Vincent
>>>
>>>
>>> Bela Patel wrote:
>>>> Does anybody know how to resolve the following issue? How to make the
>>> text
>>>> string stay within the table cell so that it does not overlap with table
>>>> border?
>>>>
>>>> Any help will be greatly appreciated.
>>>>
>>>> Thanks,
>>>> BRAMANI.
>>>>
>>>> On Mon, Oct 12, 2009 at 3:36 PM, Bela Patel <belaramani@...>
>>> wrote:
>>>>> Hi,
>>>>>
>>>>> I am using docbook version 1.74.3 for PDF report generation.
>>>>>
>>>>> I have 50 chnaracter long text in a table cell but it overlapes with
>>> the
>>>>> table border.
>>>>>
>>>>> for example :
>>>>>
>>>>> 1. I have text "*ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789ABCDEFGHIJKLMNO*"
>>> in
>>>>> one table cell but it overlapes with the table border and goes outside
>>> of
>>>>> the table.
>>>>>
>>>>> 2. But if I modify it as "*
>>>>> ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNO123456789*" then it does not
>>>>> overlap with the border but after 26 character it breaks and goes to
>>> second
>>>>> line within the same cell as shown below.
>>>>>
>>>>> ABCDEFGHIJKLMNOPQRSTUVWXYZ-
>>>>> ABCDEFGHIJKLMNO123456789
>>>>>
>>>>> how can I make the text string shown in first option to stay within the
>>>>> same cell so that it does not overlap with the table border.
>>>>>
>>>>> Thanks,
>>>>> BRAMANI.

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

RE: The LATEX \renewcommand function counterpart in Docbook XSL

2009-11-03T09:54:53Z

| -----Original Message-----
| From: Nancy Brandt
|
| Has anybody seen/created something similar to the LATEX
| \renewcommand function? This function redefines an element's
| default look&feel within the source file.

What would you expect a "\renewcommand function counterpart" to accomplish?

XML has processing instructions (PIs). DocBook XSL recognizes a set of
predefined PIs, and you can also create your own as part of your
customization. See
http://www.sagehill.net/docbookxsl/ProcessingInstructions.html.

You could also use the role attribute as a "hook" for customizations. See
http://www.sagehill.net/docbookxsl/AddNewTemplate.html#AttValueFormatting

Mauritz

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Indenting an inline media object within a table cell

2009-10-29T13:52:07Z

Hi folks,

I need to create a table in which there are two rows in the following form:

First cell Second cell

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

| <bullet-like image> Text | Other Content |

|_____________________________________|___________________|

| <indent 0.1in> <bullet-like image> Text | Other Content |

|_____________________________________|___________________|

The question is how do I create this 0.1in indent in the 1st entry of the second row using XSL (and not XSL-FO)

I tried:

<inlinemediaobject margin-left="0.1in">,

....

....

Nothing happened...

The reason I want it in XSL is that I wish this indentation to appear both in PDF and HTML outputs.

Please, advise!!!

Thanks a lot in advance!!!

Best regards,

Nancy

The LATEX \renewcommand function counterpart in Docbook XSL

2009-10-29T05:48:59Z

Hi All,

Has anybody seen/created something similar to the LATEX \renewcommand function? This function redefines an element's default look&feel within the source file.

Thanks a lot in advance!!!

Best wishes,

Nancy

Using DocBook to prepare memorandum

2009-10-27T11:11:37Z

Is anyone familiar with a technique to prepare a memorandum using
DocBook?

Thanks,

Gary Hoffman

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Re: Table cell text overlapes with table border ...docbook 1.74.3

2009-10-27T08:53:58Z

Hi,

Bela Patel wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Re: Table cell text overlapes with table border ...docbook 1.74.3

2009-10-27T07:37:48Z

On Tue, Oct 27, 2009 at 10:36 AM, Bela Patel <belaramani@...> wrote:

Vincent,

I dont quite understand what you are suggesting.

I just want the text to automatically break in next line within the cell depending on the cell size so that it does not overlap with Table border.

Can you please explain this?

Thanks,

BRAMANI.

On Tue, Oct 27, 2009 at 5:55 AM, Vincent Hennebert <vhennebert@...> wrote:

Hi,

Since it’s not a regular word it can’t be hyphenated; you must specify
yourself the places where it is allowed to break. If you want a hyphen
to be visible when the text is broken you can use the soft hyphen
character (U+00AD). Otherwise you can use a zero-width space (U+200B).

HTH,
Vincent

Bela Patel wrote:
> Does anybody know how to resolve the following issue? How to make the text
> string stay within the table cell so that it does not overlap with table
> border?
>
> Any help will be greatly appreciated.
>
> Thanks,
> BRAMANI.
>
> On Mon, Oct 12, 2009 at 3:36 PM, Bela Patel <belaramani@...> wrote:
>
>> Hi,
>>
>> I am using docbook version 1.74.3 for PDF report generation.
>>
>> I have 50 chnaracter long text in a table cell but it overlapes with the
>> table border.
>>
>> for example :
>>
>> 1. I have text "*ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789ABCDEFGHIJKLMNO*" in
>> one table cell but it overlapes with the table border and goes outside of
>> the table.
>>
>> 2. But if I modify it as "*
>> ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNO123456789*" then it does not
>> overlap with the border but after 26 character it breaks and goes to second
>> line within the same cell as shown below.
>>
>> ABCDEFGHIJKLMNOPQRSTUVWXYZ-
>> ABCDEFGHIJKLMNO123456789
>>
>> how can I make the text string shown in first option to stay within the
>> same cell so that it does not overlap with the table border.
>>
>> Thanks,
>> BRAMANI.
>>
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Re: Table cell text overlapes with table border ...docbook 1.74.3

2009-10-27T02:55:41Z

Hi,

Since it’s not a regular word it can’t be hyphenated; you must specify
yourself the places where it is allowed to break. If you want a hyphen
to be visible when the text is broken you can use the soft hyphen
character (U+00AD). Otherwise you can use a zero-width space (U+200B).

HTH,
Vincent

Bela Patel wrote:

> Does anybody know how to resolve the following issue? How to make the text
> string stay within the table cell so that it does not overlap with table
> border?
>
> Any help will be greatly appreciated.
>
> Thanks,
> BRAMANI.
>
> On Mon, Oct 12, 2009 at 3:36 PM, Bela Patel <belaramani@...> wrote:
>
>> Hi,
>>
>> I am using docbook version 1.74.3 for PDF report generation.
>>
>> I have 50 chnaracter long text in a table cell but it overlapes with the
>> table border.
>>
>> for example :
>>
>> 1. I have text "*ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789ABCDEFGHIJKLMNO*" in
>> one table cell but it overlapes with the table border and goes outside of
>> the table.
>>
>> 2. But if I modify it as "*
>> ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNO123456789*" then it does not
>> overlap with the border but after 26 character it breaks and goes to second
>> line within the same cell as shown below.
>>
>> ABCDEFGHIJKLMNOPQRSTUVWXYZ-
>> ABCDEFGHIJKLMNO123456789
>>
>> how can I make the text string shown in first option to stay within the
>> same cell so that it does not overlap with the table border.
>>
>> Thanks,
>> BRAMANI.
>>
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Table cell text overlapes with table border ...docbook 1.74.3

2009-10-26T18:25:02Z

Does anybody know how to resolve the following issue? How to make the text string stay within the table cell so that it does not overlap with table border?

Any help will be greatly appreciated.

Thanks,

BRAMANI.

On Mon, Oct 12, 2009 at 3:36 PM, Bela Patel <belaramani@...> wrote:

Hi,

I am using docbook version 1.74.3 for PDF report generation.

I have 50 chnaracter long text in a table cell but it overlapes with the table border.

for example :

1. I have text "ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789ABCDEFGHIJKLMNO" in one table cell but it overlapes with the table border and goes outside of the table.

2. But if I modify it as "ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNO123456789" then it does not overlap with the border but after 26 character it breaks and goes to second line within the same cell as shown below.

ABCDEFGHIJKLMNOPQRSTUVWXYZ-

ABCDEFGHIJKLMNO123456789

how can I make the text string shown in first option to stay within the same cell so that it does not overlap with the table border.

Thanks,

BRAMANI.

Re: jre issue with jEdit, DocBook and DocBook xsl stylesheets

2009-10-23T15:45:33Z

Did you check the jEdit website for an updated version of the plugin, one
that works with JRE 1.6? If the plugin is old, it may never have been
tested with 1.6. This seems to be more of an issue with jEdit and its
plugins rather than DocBook (which is known to work in jre 1.6).

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----
From: "Ney, Gordon B CTR USA AMC" <gordon.ney@...>
To: <docbook-apps@...>
Sent: Tuesday, October 20, 2009 7:56 AM
Subject: [docbook-apps] jre issue with jEdit, DocBook and DocBook xsl
stylesheets

Hi,

I am transforming a large 4.4 DocBook file into an XSL-Fo file. I use
an extensive customization layer and DocBook xsl stylesheets 1.69.1,
which also turns on the RenderX extensions. To perform the
transformation, I am using jEdit 4.2 with the xml and xslt processor
plugins. I start jEdit in a jre with parameters -Xms512M -Xmx1024M.

My problem stems from the following: when I perform the transformation
using jre1.5.0_20, it works well; however when using jre6, it fails and
the jEdit activity log has the following set of error messages that are
repeated many times.

[error] AWT-EventQueue-0: at
org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(Ele
mApplyTemplates.java:425)
[error] AWT-EventQueue-0: at
org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates
.java:215)
[error] AWT-EventQueue-0: at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Trans
formerImpl.java:2318)
[error] AWT-EventQueue-0: at
org.apache.xalan.templates.ElemIf.execute(ElemIf.java:203)

I experience the same behavior at home with my own personal computer. I
also experience the same behavior when I upgraded jEdit and its plugins
to the latest version.

My problem is that my work computer's operating system must be changed
from XP to Vista and only the jre6 java environment will be supported,
thus taking away my ability to perform this transformation. Is there a
way to make this transformation work?

Gordon

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Page shrinking or scaling

2009-10-23T11:58:29Z

Thanks! The gs command line worked.

In a message dated 10/23/2009 3:42:06 A.M. Pacific Daylight Time, vhennebert@... writes:

Hi,

Dean Nelson wrote:

> Hi y'all,
>
> Is there a way to shrink the page size in Docbook without having to
> reformat the doc going to PDF (FOP).
>
> My users would like to have a "half size" manual to travel with instead of
> a regular US Letter size page. I guess I could to this at the printers, but
> it would be nice if I could do it at the office.
>
> I tried adjusting the page.height and .width but that just messed things up
> because the fonts were still the same size as were the images.
>
> Any ideas?

I think your best bet is to use some PDF post-processing tool to scale
down the PDF produced by FOP. That way you are sure that both versions
will look absolutely the same, so it will be easier to, e.g., refer back
to the normal version after a first reading with the small one.

Your PDF viewer should allow you to ‘print’ the file into another PDF
file with a different scale. You can also use Ghostscript (taken from
the ps2pdf command and adapted):
gs -q -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite \
-sPAPERSIZE=halfletter -dPDFFitPage -sOutputFile=small.pdf normal.pdf

HTH,
Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: processing a sitemap out of targets.xml data

2009-10-23T09:50:35Z

Hi,

I don't know of a current XML parser that will ignore entity references. Xerces used to have such an option, but that seems to have been dropped. You could supply entity declarations to the file being parsed by adding a DOCTYPE declaration, with or without a reference to a DTD, and add entity declarations.

Bob Stayton
Sagehill Enterprises
bobs@...

----- Original Message -----

From: benno.wolf@...

To: docbook-apps@...

Sent: Thursday, October 22, 2009 3:33 AM

Subject: [docbook-apps] processing a sitemap out of targets.xml data

Hi,
I try to generate a sitemap for a complex document structure, so I decided to use the given output structure in my targets.xml to get to the document and foldernames in the right order.
I simply let run a little sitemap.xsl over it to make another docbook - xml, which all works fine in my editor (oXygen).
But when I start a batch job for it (or even use saxon with a command line, or eclipse), everything breaks, because the parser can't handle the pulled in non-xml data from the referenced .dbs.
With oXygen, I get a few warnings, that's it.
My question now: Is there a way to tell the processor to ignore the entity-references (of course it does not work with xinclude either) for this processing?

Error reported by XML parser: reference to undeclared entity (found "nbsp")
Transformation failed: Run-time errors were reported

I think this is more a general question and I'm sure there is a workaround for this.
Thanks in advance for anyl repy.

Best Regards,
Benno

Re: ePub: rudimentary support for authorgroup in opf.metadata

2009-10-23T09:11:56Z

On Fri, Oct 23, 2009 at 1:14 AM, Michael Wiedmann <mw@...> wrote:

> I'd like to see at least rudimentary support for
>
> <bookinfo|articleinfo>
> <authorgroup>
> <author>
> ...
> </author>
> </authorgroup>
>
> in OPF metadata of epub output.
> This could be accomplished e.g. like

Done.

Thanks,
Keith

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Page shrinking or scaling

2009-10-23T03:41:39Z

Hi,

Dean Nelson wrote:

> Hi y'all,
>
> Is there a way to shrink the page size in Docbook without having to
> reformat the doc going to PDF (FOP).
>
> My users would like to have a "half size" manual to travel with instead of
> a regular US Letter size page. I guess I could to this at the printers, but
> it would be nice if I could do it at the office.
>
> I tried adjusting the page.height and .width but that just messed things up
> because the fonts were still the same size as were the images.
>
> Any ideas?

I think your best bet is to use some PDF post-processing tool to scale
down the PDF produced by FOP. That way you are sure that both versions
will look absolutely the same, so it will be easier to, e.g., refer back
to the normal version after a first reading with the small one.

Your PDF viewer should allow you to ‘print’ the file into another PDF
file with a different scale. You can also use Ghostscript (taken from
the ps2pdf command and adapted):
gs -q -dSAFER -dBATCH -dNOPAUSE -sDEVICE=pdfwrite \
-sPAPERSIZE=halfletter -dPDFFitPage -sOutputFile=small.pdf normal.pdf

HTH,
Vincent

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Re: Page shrinking or scaling

2009-10-23T01:33:10Z

Hi,

font size is static by default. But you could actually make the value
dynamic by assigning its value depending on the paper.type parameter for
example.

<xsl:param name="body.font.master">
<xsl:choose>
<xsl:when test="$paper.type="A5">10pt</xsl:when>
<xsl:when test="$paper.type="A3">14pt</xsl:when>
<xsl:otherwise>12pt</xsl:otherwise>
</xsl:choose>
</xsl:param>

(untested)

Concerning images, you can either:
- make the size relative (e.g. width="80%")
- recalculate the size at transformation time by extracting it in the
image handling template and making it a fraction of the static size
depending on the paper size change... (might be more difficult).

Good luck,

Camille.

DeanNelson@... wrote:

> Hi y'all,
>
> Is there a way to shrink the page size in Docbook without having to
> reformat the doc going to PDF (FOP).
>
> My users would like to have a "half size" manual to travel with
> instead of a regular US Letter size page. I guess I could to this at
> the printers, but it would be nice if I could do it at the office.
>
> I tried adjusting the page.height and .width but that just messed
> things up because the fonts were still the same size as were the images.
>
> Any ideas?
>
> Regards,
> Dean Nelson

[camille.vcf]

begin:vcard fn:Camille Begnis n:Begnis;Camille org:NeoDoc adr:;;5 rue de la Touloubre;Venelles;;13770;France email;internet:camille@... tel;work:+33.9.54.96.99.55 tel;fax:+33.9.59.96.99.55 tel;cell:+33.6.33.15.10.23 url:http://www.neodoc.biz version:2.1 end:vcard

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

ePub: rudimentary support for authorgroup in opf.metadata

2009-10-23T01:14:13Z

I'd like to see at least rudimentary support for

<bookinfo|articleinfo>
<authorgroup>
<author>
...
</author>
</authorgroup>

in OPF metadata of epub output.
This could be accomplished e.g. like

--- docbook.xsl.1.75.2 2009-06-16 04:59:35.000000000 +0200
+++ docbook.xsl 2009-10-23 09:48:11.000000000 +0200
@@ -605,6 +605,10 @@

</xsl:template>

+ <xsl:template match="authorgroup" mode="opf.metadata">
+ <xsl:apply-templates select="author" mode="opf.metadata"/>
+ </xsl:template>
+
<xsl:template match="author|corpauthor" mode="opf.metadata">
<xsl:variable name="n">
<xsl:call-template name="person.name">

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@...
For additional commands, e-mail: docbook-apps-help@...

Page shrinking or scaling

2009-10-22T15:39:50Z

Hi y'all,

Is there a way to shrink the page size in Docbook without having to reformat the doc going to PDF (FOP).

My users would like to have a "half size" manual to travel with instead of a regular US Letter size page. I guess I could to this at the printers, but it would be nice if I could do it at the office.

I tried adjusting the page.height and .width but that just messed things up because the fonts were still the same size as were the images.

Any ideas?

Regards,

Dean Nelson

processing a sitemap out of targets.xml data

2009-10-22T03:33:35Z

Hi,
I try to generate a sitemap for a complex document structure, so I decided to use the given output structure in my targets.xml to get to the document and foldernames in the right order.
I simply let run a little sitemap.xsl over it to make another docbook - xml, which all works fine in my editor (oXygen).
But when I start a batch job for it (or even use saxon with a command line, or eclipse), everything breaks, because the parser can't handle the pulled in non-xml data from the referenced .dbs.
With oXygen, I get a few warnings, that's it.
My question now: Is there a way to tell the processor to ignore the entity-references (of course it does not work with xinclude either) for this processing?

Error reported by XML parser: reference to undeclared entity (found "nbsp")
Transformation failed: Run-time errors were reported

I think this is more a general question and I'm sure there is a workaround for this.
Thanks in advance for anyl repy.

Best Regards,
Benno