Ubuntu

openjade 1.4devel1-13 rejects dbttlpg.dsl flow object not accepted by port; only display flow objects accepted

Reported by John Steele Scott (t-tec) on 2005-02-01
8
Affects Status Importance Assigned to Milestone
openjade
Unknown
Unknown
openjade (Ubuntu)
Medium
Unassigned

Bug Description

I have a simple docbook file which looks like this:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

<book>
<bookinfo>
  <title>Title</title>
  <subtitle>Subtitle</subtitle>
</bookinfo>
</book>

I wish to make a PDF using docbook2pdf.

With openjade-1.4devel1-13, it fails as follows:

john@john-ubuntu:/tmp $ docbook2pdf -p /usr/bin/openjade-1.4devel test.docbook
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /tmp/test.docbook
/usr/bin/openjade-1.4devel:/usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbttlpg.dsl:2649:6:E:
flow object not accepted by port; only display flow objects accepted
Done.

Openjade-1.3 is okay:

john@john-ubuntu:/tmp $ docbook2pdf -p /usr/bin/openjade1.3 test.docbook
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /tmp/test.docbook
Done.

Jade 1.2.1-42 is also okay:

john@john-ubuntu:/tmp $ docbook2pdf -p /usr/bin/jade test.docbook
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /tmp/test.docbook
/usr/bin/jade:/usr/share/sgml/declaration/xml.dcl:31:27:W: characters in the
document character set with numbers exceeding 65535 not supported
Done.

The file it complains about is:
john@john-ubuntu:/tmp $ dpkg -S
/usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbttlpg.dsl
docbook-dsssl: /usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbttlpg.dsl
john@john-ubuntu:/tmp $ dpkg -s docbook-dsssl | grep Version
Version: 1.78-4

And the specific part which seems to cause the error is:

  (element subtitle
    (make sequence
      font-family-name: %title-font-family%
      font-weight: 'bold
      (literal (if (first-sibling?) ": " "; ")) <----- this line is where the
error comes
      (process-children)))

If I remove the subtitle from my original test file, there is no error.

Matt Zimmerman (mdz) wrote :

It's not clear to me whether dbttlpg.dsl is incorrect (and openjade 1.4 is being
more stringent), or openjade 1.4 is incorrect.

Any XML experts in the house?

Matt Zimmerman (mdz) wrote :

Is this bug still present and relevant in current Breezy?

I don't have breezy at work yet, but will run this test-case on a PC at home,
and get back to you.

John Steele Scott (toojays) wrote :

This bug is still there in the latest breezy packages (docbook-dsssl-1.79-3,
openjade-1.4devel1-14ubuntu1). The line number is different, but the code at
that line is the same as it was when I first reported this.

toojays@hiro:/tmp$ docbook2pdf -p /usr/bin/openjade-1.4devel test.xml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /tmp/test.xml
/usr/bin/openjade-1.4devel:/usr/share/sgml/docbook/stylesheet/dsssl/modular/print/dbttlpg.dsl:2722:6:E:
flow object not accepted by port; only display flow objects accepted
Done.

Matt Zimmerman (mdz) on 2006-03-31
Changed in openjade:
assignee: nobody → dsilvers
Daniel Silverstone (dsilvers) wrote :

As far as I can tell, there has been no development on this software in several years.

The openjade project appear to be concentrating on OpenSP instead of openjade.

I have thus filed an upstream bug here: http://sourceforge.net/tracker/index.php?func=detail&aid=1463717&group_id=2115&atid=102115

But I don't believe we can track sourceforge bugs generically in malone.

Daniel Silverstone (dsilvers) wrote :

I can confirm that this remains the case in dapper. Let's see what upstream make of it

Changed in openjade:
status: Unconfirmed → Confirmed

On Mon, Apr 03, 2006 at 05:38:20PM -0000, Daniel Silverstone wrote:
> As far as I can tell, there has been no development on this software in several years.
>
> The openjade project appear to be concentrating on OpenSP instead of openjade.
>
> I have thus filed an upstream bug here: http://sourceforge.net/tracker/index.php?func=detail&aid=1463717&group_id=2115&atid=102115
>
> But I don't believe we can track sourceforge bugs generically in malone.

Not generically, but it's sensible to add bug trackers for each SF upstream
that we have.

--
 - mdz

Daniel Silverstone (dsilvers) wrote :

I have added support for, and attached a remote bug watch for, this bug.

Changed in openjade:
assignee: dsilvers → nobody

Thank you for posting this bug.

Does this occur in Lucid?

Changed in openjade (Ubuntu):
status: Confirmed → Incomplete
John Steele Scott (toojays) wrote :

I don't know if it still occurs in Lucid, this bug report was from a past life. I don't need to care about this anymore.

The bug description includes a trivially simple method to reproduce. If you wanted to actually help Ubuntu improve (rather than just karma whore) you could attempt to reproduce it yourself.

John Steele Scott, thank you for responding so quickly. However, I do not appreciate your remarks about me trying to be a "karma whore". To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers (including myself), so please bear this in mind.

I still experience the very same problem in Lucid, openjade 1.4devel1-19build1 (the default openjade).

If you want more details, please ask.

Thomas Hotz (thotz) wrote :

I mark the bug as confirmed. Please run "apport-collect 12431". This gives us all the information about your current system you are using. Thank you very much for your help!

Thomas Hotz (thotz) wrote :

I close this bug, because I don't get a reply. If you still encounter this bug, feel free to reopen this bug, or better, report a new bug. Thank you!

Changed in openjade (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.