Douglas W Philips wrote:
> On Fri, Mar 26, 2010 at 6:49 AM, Hussein Shafie <hussein at xmlmind.com
> <mailto:hussein at xmlmind.com>> wrote:
> 
>     --> The bug below is almost certainly unrelated to the above issues:
>     ---
>     ditac: ERROR: fatal error reported by the XSLT engine: A sequence of
>     more than one item is not allow ed as the first operand of 'ge' (2, 6)
>     ; SystemID: file:/C:/ditac-1_2_0/xsl/fo/pagination.xsl; Line#: 627;
>     Column#: -1
>     ---
>     In order to fix it, we need to be able to reproduce it.
> 
> 
> That should be easy. AllI did was put a weebles="expert" attribute on
> the topic element of sample2.dita. It didn't matter if I put it before
> or after the "id" attribute. :(
> 
> That was just a shot-in-the-dark guess based on your description of how
> ditac "transfers" conditional attributes from the map's topicref to the
> dita file's topic element. I had hoped it would work so that we could
> use that as a work-around.
> 
> I'll reply to the other parts of your email separately, but this part
> seemed pretty self-contained and concise. :)
> 

I'm really sorry to annoy you again with our bugs, but I cannot
reproduce  the above bug even after adding a weebles="expert" attribute
on the topic element of sample2.dita.

I used the files you sent us and just replaced sample2.dita by:
---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN"
"http://docs.oasis-open.org/dita/dtd/topic.dtd";>
<topic id="sample_topic2" weebles="expert">
  <title>Sample topic</title>

  <body>
    <p>The intended audience of this topic are experts.</p>
  </body>
</topic>
---

I used ditac 1.2 to do this:
---
~/tmp/sample2$ ~/src/ditac/bin/ditac -version
ditac: INFO: ditac version is 1.2.0

~/tmp/sample2$ java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)

~/tmp/sample2$ ~/src/ditac/bin/ditac -filter sample2.ditaval
sample.docx sample.ditamap
---

Which XSL-FO processor is invoked by ditac, RenderX XEP or XMLmind
XSL-FO Converter, does not matter. It always works as expected.

This location:
---
file:/C:/ditac-1_2_0/xsl/fo/pagination.xsl; Line#: 627
---
indicates that the bug seems to be triggered by hand-written frontmatter
and/or backmatter (???)




Reply via email to