Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (hermes.apache.org: domain of mcintyre.a@gmail.com
 designates 64.233.170.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=ZVr5pxnM04owmpBOp14Pr7i+DnEwWijEJbmbF3M2kg7R+niP+dZQjS/KKqIwgv9sBEO1kk/s6UDH8mQ573ZqX+cfcFBmEKQTOYk8FpVoaejk1ItCS2v96tM7nnI5dnyhsfYgOBQztK1Fe8OUq5bkELeKgSvReOxgPiq/rYMC4e8=
Message-ID: <54ac72d705032215176681aadc@mail.gmail.com>
Date: Tue, 22 Mar 2005 15:17:58 -0800
From: Andrew McIntyre <mcintyre.a@gmail.com>
Reply-To: Andrew McIntyre <mcintyre.a@gmail.com>
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: [doc] Simplified DITA instructions
In-Reply-To: <42409C68.4010500@wiu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <20050322010341.49935.qmail@web81606.mail.yahoo.com>
	 <42409C68.4010500@wiu.edu>

On Tue, 22 Mar 2005 16:30:00 -0600, scott hutinger <s-hutinger@wiu.edu> wrote:
>      [xslt] home/srh/src/derby-d/docs/trunk/temp/rrefdmrs.dita:14:32:
> Fatal Error! XML document structures must start and end within the same
> entity.

Hi Scott,

Is that the only error in the output? Please check the preceding
section for other errors. I was seeing something similar on Windows
2000, but in the admin guide. The problem was that during the mappull
transform, the XSL parser would somehow fail to evaluate the title of
a topic/task as equal to the corresponding entry in the mapfile. This
would output an error that reads something like "Cannot find task
title in .dita file, using navtitle instead" but then the parser would
quit without finishing the transform, leaving an incomplete set of
files for the topicpull transform. That transform would then produce
an error like the one you posted.

The problem seems to be a problem with how Xalan handles whitespace on
Windows, as I was unable to reproduce the problem on Linux or Mac OS X
(or even Windows XP!). I was able to work around the problem by
removing all the whitespace (including spaces :(( ) from the title in
the task and the corresponding navtitle in the ditamap, but while that
allows it build the pdf, the readability goes to zero.

Are you working on Windows 2000? If so, try adding the Saxon jars to
your classpath and running the build again, I'm curious if it will
automatically use Saxon (instead of Xalan) if it is in the classpath.

andrew