Bob Stayton | 1 Mar 06:21 2010
Picon

Re: Forcing a chapter to start on new page (FO)

Hi,
You could set the stylesheet parameter named double.sided to 1.  That will force new 
chapters to start on an odd page.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Jeffrey Trimble" <jtrimble <at> cc.ysu.edu>
To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Sunday, February 28, 2010 3:54 PM
Subject: [docbook-apps] Forcing a chapter to start on new page (FO)

> Is there a quick (and maybe dirty) way to force each chapter to start  on a new page 
> (odd number page) via the print.xsl
> stylesheet for PDF generation?
>
> For example, my Chapter 1 is only one page.  Chapter 2 begins on page  two, instead 
> of page 3.
>
> Thanks in advance,
>
>
> Jeffrey Trimble
> System LIbrarian
> William F.  Maag Library
> Youngstown State University
> 330.941.2483 (Office)
> jtrimble <at> cc.ysu.edu
(Continue reading)

Ivan Ristic | 1 Mar 12:56 2010
Picon

Re: Footer odd/even page problem when chapters do not begin on an odd page

On Sat, Feb 27, 2010 at 12:29 AM, Bob Stayton <bobs <at> sagehill.net> wrote:
> Hi,

Hi Bob,

Many thanks for your help.

> Did you customize the page-sequence-masters as well?

No, I did not -- my knowledge of the stylesheets is limited and I
didn't know what to try next.

With the customisation, per your advice, I managed to have chapters on
auto and the footers rendered correctly.

When I attempted to do the same for all book parts, however, I
encountered another problem:

- My book has parts and my first part falls on an odd page (left).

- The first part is just a single page, and the second page in the
book is the first page of the first chapter. It falls on an even page
(right).

- The initial.page.number template will return 1 for the first page of
the first part because it's the first page of the book (the front
matter uses roman numerals)

- The footer of the second page (even) will be rendered using the odd
layout. (And, from then on, all the pages will have the footer layouts
(Continue reading)

Sherwood Hu | 1 Mar 17:34 2010

RE: RE: Test condition to check if the current node is the first child

Larry,

Thanks for the suggestion. But it does not work if white spaces exist
between <note> and <para> such 
As

<note>       

   <para>
...
</para></note>

Sherwood

-----Original Message-----
From: Rowland, Larry [mailto:larry.rowland <at> hp.com] 
Sent: Wednesday, February 24, 2010 6:04 PM
To: Sherwood Hu; docbook-apps <at> lists.oasis-open.org
Subject: [docbook-apps] RE: Test condition to check if the current node
is the first child

You might try testing for there being no preceding sibling:

   preceding-sibling::node() = ''

Regards,
Larry Rowland

________________________________

(Continue reading)

Rowland, Larry | 1 Mar 19:29 2010
Picon

RE: RE: Test condition to check if the current node is the first child

Sherwood,

Sorry, my mistake.

Try preceding-sibling::element (or preceding-sibling::*) to avoid the white space issue.

LRR 

-----Original Message-----
From: Sherwood Hu [mailto:sherwood <at> morovia.com] 
Sent: Monday, March 01, 2010 9:35 AM
To: docbook-apps <at> lists.oasis-open.org
Subject: RE: [docbook-apps] RE: Test condition to check if the current node is the first child

Larry,

Thanks for the suggestion. But it does not work if white spaces exist
between <note> and <para> such 
As

<note>       

   <para>
...
</para></note>

Sherwood

-----Original Message-----
From: Rowland, Larry [mailto:larry.rowland <at> hp.com] 
(Continue reading)

Dick Hamilton | 1 Mar 20:21 2010

RE: Re: [docbook] DocBook and Google Summer of Code ?

Stefan and the DocBook community,

Stefan, thanks for bringing the deadline to everyone's attention.

I would be glad to act as administrator for the DocBook project.

To that end, there are a few things that need to happen that I cannot do
on my own:

1) We need some mentors; so far, Stefan is the only person who has
signed on as a mentor. Seems to me that we need at least two or three
projects with mentors to make a credible application.

2) We need backup mentor for each project. It's not essential, but it
would help the application and would also make sure that students have
more than one person to work with in case someone is out of town, etc.

I suggest the following schedule:

1) Until March 8 (next Monday) I'll leave the wiki open
(http://docbook.xmlpress.net) for anyone to edit (for those just looking
into this, you need to sign up, but it's automatic and easy). Please
look at the projects, add any you are willing to be mentor for, and sign
up as mentor or backup mentor for any project. Also, if you sign up as a
mentor, please fill out the description if it needs some extra
information, and send me your contact information.

2) On March 8, I'll remove any projects that don't have mentors, and if
we have at least two projects with mentors, I'll begin preparing the
application.
(Continue reading)

Stefan Seefeld | 1 Mar 21:36 2010
Picon

Re: [docbook-apps] Re: [docbook] DocBook and Google Summer of Code ?

Dick,

thanks a lot for your initiative, again !

On 03/01/2010 02:21 PM, Dick Hamilton wrote:
> Stefan and the DocBook community,
>
> Stefan, thanks for bringing the deadline to everyone's attention.
>
> I would be glad to act as administrator for the DocBook project.
>
> To that end, there are a few things that need to happen that I cannot do
> on my own:
>
> 1) We need some mentors; so far, Stefan is the only person who has
> signed on as a mentor. Seems to me that we need at least two or three
> projects with mentors to make a credible application.
>    

I'm not quite convinced of this. In this stage the goal is for the 
DocBook project to be accepted as mentoring organization. I don't think 
that DB requires much work to be considered by Google as credible, given 
its long and successful history.

It is once that potential applicants are looking for things to work on 
that we need to show mentor availability. Similarly with tasks: they are 
merely suggestions for students who want to work on DB, but don't have 
made up their mind on what specifically to work on.

It may also happen that a student shows up with a fully thought-out 
(Continue reading)

David Cramer | 1 Mar 23:43 2010

RE: [docbook-apps] Re: [docbook] DocBook and Google Summer of Code ?

Hi Dick,
Thanks from me as well for keeping this idea going. 

Perhaps we should think in terms of co-mentoring (rather than mentor and
backup). I would be willing to co-mentor the Webhelp proposal. 

Thanks,
David

> -----Original Message-----
> From: Dick Hamilton [mailto:rlhamilton <at> frii.com] 
> Sent: Monday, March 01, 2010 1:21 PM
> To: 'docbook'; 'DocBook Apps Mailing List'
> Subject: RE: [docbook-apps] Re: [docbook] DocBook and Google 
> Summer of Code ?
> 
> Stefan and the DocBook community,
> 
> Stefan, thanks for bringing the deadline to everyone's attention.
> 
> I would be glad to act as administrator for the DocBook project.
> 
> To that end, there are a few things that need to happen that 
> I cannot do on my own:
> 
> 1) We need some mentors; so far, Stefan is the only person 
> who has signed on as a mentor. Seems to me that we need at 
> least two or three projects with mentors to make a credible 
> application.
> 
(Continue reading)

Dick Hamilton | 2 Mar 00:49 2010

RE: [docbook-apps] Re: [docbook] DocBook and Google Summer of Code ?

David,

I think co-mentoring makes great sense. I see that you signed up on the
Wiki and did exactly what I was going to suggest, which was to leave a
line with "Your name here" for another volunteer.

Generally, let's go with co-mentors, though if in some situation a
mentor with a backup makes better sense, just mark it up that way.

Best,
Dick
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624 

> -----Original Message-----
> From: David Cramer [mailto:dcramer <at> motive.com] 
> Sent: Monday, March 01, 2010 3:43 PM
> To: Dick Hamilton; docbook; DocBook Apps Mailing List
> Subject: RE: [docbook-apps] Re: [docbook] DocBook and Google 
> Summer of Code ?
> 
> 
> Hi Dick,
> Thanks from me as well for keeping this idea going. 
> 
> Perhaps we should think in terms of co-mentoring (rather than 
> mentor and
(Continue reading)

Michael Fuchs | 2 Mar 14:16 2010

Missing toc levels in Javahelp

Hello,

I tried to generate some javahelp from the file
docsrc/reference.xml.included from the DocBook XSL packages for usage
with the dbdoclet gui.

I run into a problem, because the generated navigation tree always ended
at the part level. It never showed the reference level or anything
deeper nested.

The structure of the file is:

set
  book
    part
      reference
        refentry
        ...

The problem seems to be the following template from javahelp.xsl

If it matches a part element, it doesn't look for reference child nodes,
but only for direct refentry tags. If I add the reference element to the
apply-templates call, everything seems to function correctly.

<xsl:template match="part|reference|preface|chapter|appendix|article"
              mode="jhtoc">
  <xsl:variable name="id">
    <xsl:call-template name="object.id"/>
  </xsl:variable>
(Continue reading)

Jeffrey Trimble | 2 Mar 14:38 2010

Re: Forcing a chapter to start on new page (FO)

Bob, 

Thanks.  I tried it, but I got numerous FO errors.  Here's some specifics that
may be why I got the errors:

Docbook.xml 4.5
FOP .94

In my pint.xsl style sheet I have the following reference:

It seems to have been the culprit, but I'm not much help since this isn't my area of expertise.

Any thoughts?

TIA,

Jeff

On Mar 1, 2010, at 12:21 AM, Bob Stayton wrote:

Hi,
You could set the stylesheet parameter named double.sided to 1.  That will force new chapters to start on an odd page.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net


----- Original Message ----- From: "Jeffrey Trimble" <jtrimble <at> cc.ysu.edu>
To: "DocBook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Sunday, February 28, 2010 3:54 PM
Subject: [docbook-apps] Forcing a chapter to start on new page (FO)


Is there a quick (and maybe dirty) way to force each chapter to start  on a new page (odd number page) via the print.xsl
stylesheet for PDF generation?

For example, my Chapter 1 is only one page.  Chapter 2 begins on page  two, instead of page 3.

Thanks in advance,


Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
jtrimble <at> cc.ysu.edu
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
"The spice must flow..."


---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org




---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe <at> lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help <at> lists.oasis-open.org


Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
"The spice must flow..."


Gmane