Mansour | 1 Dec 03:33 2007
Picon

Re: Line spacing

Thank you, Bob. That's exactly what I wanted.

Bob Stayton wrote:
> Then you can output a processing instruction like <?break?> using XSLT 
> as follows:
>
> <xsl:processing-instruction name="break"/>
>
> Then your docbook stylesheet customization can process that into an 
> empty fo:block to create the line break.
>
> Bob Stayton
> Sagehill Enterprises
> DocBook Consulting
> bobs <at> sagehill.net
>
>
> ----- Original Message ----- From: "Mansour" <mansour77 <at> yahoo.com>
> To: "Bob Stayton" <bobs <at> sagehill.net>
> Cc: <docbook <at> lists.oasis-open.org>
> Sent: Friday, November 30, 2007 11:52 AM
> Subject: Re: [docbook] Line spacing
>
>
>> I am aware of the literallayout tag. However, it preserves every 
>> thing inside the tag like extra spaces. That's why I am trying avoid 
>> using it. On the other hand, using a processing instruction like 
>> <?break-line?> is not going to work, because I am not writing a 
>> docbook document directly. I am writing a template (xslt) that will 
>> generate a docbook. And I couldn't find a way to output <?break?> 
(Continue reading)

Norman Walsh | 1 Dec 16:15 2007

DocBookers dinner (3 Dec 2007)

Coming to Boston for XML 2007? Interested in DocBook? Eat? Let's have
dinner!

Anyone interested in dinner? See
http://norman.walsh.name/2007/11/30/DocBookDinner

Concrete plans always work better than vague ones, so I propose that
we meet in the Marriott Copley Place hotel lobby at 7:30p on Monday,
3 December 2007, departing for dinner promptly at 8:00p. There must be
restaurants close by.

If you look at the XML 2007 schedule, you'll see that there are events
every evening. There's nothing to be done about that. If you're not
free for dinner, I'll be wandering around every day.

(And sorry for the late notice; I blame my cold and too much work.
Thanks to Keith Fahlgren for the just-in-time reminder!)

                                        Be seeing you,
                                          norm

--

-- 
Norman Walsh <ndw <at> nwalsh.com>      | Oh well, no matter what happens,
http://www.oasis-open.org/docbook/ | there's always death.-- Napoleon
Chair, DocBook Technical Committee |
Jean Jordaan | 2 Dec 06:56 2007
Picon

Re: Re: [docbook-apps] A sequence of tables ..

Hi David

> Ah, then maybe this:

Slightly edited:

>      <section><title>Use cases</title>
>        <simplesect><title>Use Case 1: Blah</title>
>          <informaltable>...</informaltable>
>        </simplesect>
>        <simplesect><title>Use Case 2: Wooga</title>
>          <para>...</para>
>          <para>...</para>
>          <table>...</table>
>        </simplesect>
>        ....
>        <simplesect><title>Use Case 5: Create Zone</title>
>          <informaltable>...</informaltable>
>        </simplesect>
>      </section>

Hmm, that's pretty close. Thanks.

Now I have another issue. Some use cases are grouped; i.e. 5.1, 5.2,
so I want something like this::

  <section><title>Use cases</title>
     <simplesect><title>Use Case 1: Blah</title>
        <informaltable>...</informaltable>
     </simplesect>
(Continue reading)

David Cramer | 2 Dec 17:26 2007

RE: Re: [docbook-apps] A sequence of tables ..

Since you're happy with simplesects, which look like sections except
they don't chunk, I'm guessing that the main thing you want is that each
use case not be on a separate chunk. So if there existed a processing
instruction, <?dbhtml stop-chunking?>, that caused the xsls to stop
chunking from that point on, you could do this:

  <section>
     <?dbhtml stop-chunking?>
     <title>Use cases</title>
     <section><title>Use Case 1: Blah</title>
        <informaltable>...</informaltable>
     </section>
     ....
     <section><title>Create Zone</title>
       <section><title>Use Case 5.1: Create Small Zone</title>
       ...
       </section>
       <section><title>Use Case 5.2: Create Big Zone</title>
       ...
       </section>
     </section>
     <section><title>Use Case 6: Another simple one</title>
        <informaltable>...</informaltable>
     </section>
     ...
  </section>

This would be better because simplesects not chunking might actually be
a bug and could be fixed later. I've wanted this very feature and have
looked into implementing it. It's doable (only tricky because of the
(Continue reading)

Mansour | 2 Dec 22:25 2007
Picon

keep-together and keep-with-next

I have a section that I need it all in one page. This section consists 
only of a list. The last item in the list is rendered on the top of the 
next page. I have tried every possible combination of keep-together and 
keep-with-next. Nothing worked.

<section>
    <title> title of the section</title>
    <?dbfo keep-together.within-coloumn="always"?>
    <para> this is the explanation of the section. Two more lines to 
go.</para>
    <itemizedlist>
    <listitem> item1</listitem>
    <listitem> item2</listitem>
    <listitem> item3 </listitem>
    </itemizedlist>
</section>

I have tried  keep-with-next, keep-together.within-page. Can someone 
help getting this to work?
thank you.
David Cramer | 3 Dec 04:49 2007

RE: keep-together and keep-with-next

It sounds like <?dbfo keep-together="auto" ?> is only supported in
tables: http://www.sagehill.net/docbookxsl/PageBreaking.html

You could add something like this to your customization layer:

  <xsl:template match="*[processing-instruction('mansour-fo') =
'keep-together']">
	<fo:block keep-together.within-column="always">
	  <xsl:apply-imports/>
	</fo:block>
  </xsl:template>

This template wraps any element containing <?mansour-fo keep-together?>
in a <fo:block keep-together.within-column="always">. So put
<?mansour-fo keep-together?> as a child of your section. It should also
work in other places, but you could also put is in places where the
results would be not what you want or even result in invalid fo. 

David 

> -----Original Message-----
> From: Mansour [mailto:mansour77 <at> yahoo.com] 
> Sent: Sunday, December 02, 2007 3:26 PM
> To: docbook <at> lists.oasis-open.org
> Subject: [docbook] keep-together and keep-with-next
> 
> I have a section that I need it all in one page. This section 
> consists only of a list. The last item in the list is 
> rendered on the top of the next page. I have tried every 
> possible combination of keep-together and keep-with-next. 
(Continue reading)

David Cramer | 3 Dec 04:55 2007

RE: keep-together and keep-with-next

Oh, btw., if you're not using fop, you might first try the technique
describe in "Soft page breaks" in Bob's book:
http://www.sagehill.net/docbookxsl/PageBreaking.html 

David

> -----Original Message-----
> From: David Cramer 
> Sent: Sunday, December 02, 2007 9:50 PM
> To: Mansour; docbook <at> lists.oasis-open.org
> Subject: RE: [docbook] keep-together and keep-with-next
> 
> It sounds like <?dbfo keep-together="auto" ?> is only supported in
> tables: http://www.sagehill.net/docbookxsl/PageBreaking.html
> 
> You could add something like this to your customization layer:
> 
>   <xsl:template match="*[processing-instruction('mansour-fo') 
> = 'keep-together']">
> 	<fo:block keep-together.within-column="always">
> 	  <xsl:apply-imports/>
> 	</fo:block>
>   </xsl:template>
> 
> This template wraps any element containing <?mansour-fo 
> keep-together?> in a <fo:block 
> keep-together.within-column="always">. So put <?mansour-fo 
> keep-together?> as a child of your section. It should also 
> work in other places, but you could also put is in places 
> where the results would be not what you want or even result 
(Continue reading)

Olivier Ishacian | 3 Dec 13:55 2007

[ANN] XMLmind XML Editor 3.7.0

XMLmind XMLmind is pleased to announce a new version of XMLmind XML Editor.
   _____________________________________________

XMLmind XML Editor Personal Edition 3.7.0 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/xmleditor/upgrade.html.)
   _____________________________________________

v3.7.0 (November 15, 2007):

   * The DITA add-on for XMLmind XML Editor now
     fully supports the DITA DTD 1.1. It includes
     its own minimal copy of DITA Open Toolkit
     version 1.4. If you need this add-on, please
     install it using Options|Install Add-ons.

   * New Tools|Helper Application sub-menu. This
     menu contains entries allowing to use
     third-party applications to view or edit part
     or all of the document being edited.

   * New date/time picker dialog box. This dialog
     box is used by the Attribute Tool, the
     putAttribute and addAttribute commands, new
     form controls called date-time-picker,
(Continue reading)

Mansour | 3 Dec 19:59 2007
Picon

Re: keep-together and keep-with-next

David, both suggestions worked but not in the same way.
Using the soft break method generated exactly what I was expecting and 
pushed the section to the next page. However, using the processing 
instruction you gave, did a better job. It kept the section on the same 
page but it made the spaces between lines smaller in order to fit the 
whole section. I do not understand what happened exactly, or the low 
level work of all this, but using the PI generated the result I need.

Thank you.
Jean Jordaan | 4 Dec 03:58 2007
Picon

Re: Re: [docbook-apps] A sequence of tables ..

Hi David

> Since you're happy with simplesects, which look like sections except
> they don't chunk, I'm guessing that the main thing you want is that
> each use case not be on a separate chunk.

That's pretty much spot-on :-)

This is one of those specification documents that go into deeply nested
short numbered sections. Often the sections are just a paragraph (or
two), but they may contain tables and sometimes a bunch of subsections.
Marking it up as one enormous list isn't ideal, as the items need to be
in a ToC. And having sections that chunk into myriads of tiny pages
isn't nice either.

The one tricky bit I think is chunking this::

    simplesect
    simplesect
    section
    simplesect

How would that look? Maybe like this::

    SECTION TITLE

        Section ToC

        simplesect1 title
        simplesect2 title
(Continue reading)


Gmane