public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Wookey <wookey@aleph1.co.uk>
To: Timothy Reaves <treaves@silverfields.com>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: problems generating PDF
Date: Tue, 31 Jul 2001 11:07:00 -0000	[thread overview]
Message-ID: <Marcel-1.50-0731175243-b49h+Ty@chewy.aleph1.co.uk> (raw)
In-Reply-To: <20010731113853.0843dd17.treaves@silverfields.com>

On Tue 31 Jul, Timothy Reaves wrote:
> 	Hello all.
> 
> 	I have a (currently) very simple docbook document I'm working on to
> evaluate docbook.
>   I have jEdit setup very nicely to help me with this.  Writing the
> document in docboo k isn't really a problem.  The problem is producing
> output.  Specifically PDF.
> 
> 	When I generate a PDF document, the basic structure is fine. 
> However, a portion of the text is in red.  I've no idea why. 

hmm, red in HTML output means 'this text is wrong in some way but I'm putting
it in anyway'. Not sure if the same thing can occur in PDF (it hasn't for me
yet), so this may be a red herring.

> There is no tag at that location. 

Check the output of warnings from the SGML processor - it probably complains
about something at this point.

> Other portions are itialicised when the
> should (based on other portions of the document that are t agged
> similerly).  

Don't know about that

> And finally, another portion has no margin.

I've had this when something was wrong with the SGML structure. All the pages
after the point where it goes wrong have their margins completely wrong.
I forget what actually caused it, but it was something like having unbalanced
<sect></sect> tags or starting a chapter inside a chapter.

> 	Are these types of problems common with actually generating documents
> from docbook so urce?  I can't see how docbook could be useful unless there
> were a reliable way to act ually generate documents from it.

It can work fine. I suspect you actually have errors in your SGML and it is
doing its best to do what you said as opposed to what ou meant :-)

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/     play: http://www.chaos.org.uk/~wookey/

      reply	other threads:[~2001-07-31 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  8:39 Timothy Reaves
2001-07-31 11:07 ` Wookey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Marcel-1.50-0731175243-b49h+Ty@chewy.aleph1.co.uk \
    --to=wookey@aleph1.co.uk \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=treaves@silverfields.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).