Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

Docbook support in Gentoo is broken [solved]

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
36 posts
  • 1
  • 2
  • Next
Author
Message
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

Docbook support in Gentoo is broken [solved]

  • Quote

Post by tempest » Fri Jun 18, 2004 8:23 pm

I have several papers of mine written in docbook XML, all of which I was able to convert and handle with the docbook2* utils when using Redhat.

A year ago I switched to Gentoo; I never tried to handle these documents again until today, and discovered that I probably have something messed up in my docbook config.

This is a simple sample document:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<articleinfo>
<title>dummy title</title>
</articleinfo>
 
<para>dummy text</para>
 
</article>
When I try to use docbook2pdf on it:

Code: Select all

$ docbook2pdf dummy.xml
Using catalogs: /usr/share/sgml/opensp-1.5/OpenSP/catalog, /usr/share/sgml/docbook/sgml-dtd-4.1/catalog, /usr/share/sgml/docbook/sgml-dtd-3.0/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.77/catalog, /usr/share/sgml/docbook/sgml-dtd-4.0/catalog, /usr/share/sgml/docbook/sgml-dtd-3.1/catalog, /usr/share/sgml/sgml-iso-entities-8879.1986/catalog, /usr/share/sgml/openjade-1.3.2/catalog, /usr/share/sgml/openjade-1.3.2/dsssl/catalog, /usr/share/sgml/xml-iso-entities-8879.1986/catalog
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /home/tempest/articles/dummy.xml
jade:/home/tempest/articles/dummy.xml:2:118:E: URL not supported by this version
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl:53:130:Q: number of ID references in start-tag must not exceed GRPCNT (32)
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl:52:0:Q: number of ID references in start-tag must not exceed GRPCNT (32)
Maybe the problem has something to do with the catalogs (only the SGML ones are listed, and I'm using XML) or jade; does anybody have a clue about how to fix this problem?

Edit: Changed title of topic to "Docbook support in Gentoo is broken"
Edit: Changed title of topic to "Docbook support in Gentoo is broken - on fresh install too!"
Edit: Added "[solved]" to topic subject.
Last edited by tempest on Wed Jan 05, 2005 9:04 pm, edited 3 times in total.
For every problem there is a solution that is simple, neat, and wrong.
Top
nemo_
Apprentice
Apprentice
User avatar
Posts: 167
Joined: Thu Sep 19, 2002 12:38 am
Location: Brussels, Belgium
Contact:
Contact nemo_
Website

  • Quote

Post by nemo_ » Sat Jun 19, 2004 3:21 pm

i'm really not sure if this would help but did you check http://dev.gentoo.org/~satai/sgmlfix.html ?
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Sun Jun 20, 2004 5:03 pm

I had a look at it and realized that the problem is much harder than I thought... It seems to be an issue caused by improper handling of XML catalogs.

satai wrote:it's probably XML -- which hasn't been dealt with properly by Gentoo yet, but will be some day
Anyway I unmerged and reemerged the suggested apps, and noticed that when emerging docbook-xml-dtd-4.2, the ebuild would complain about the missing docbookx.dtd file. After a forum search:

http://forums.gentoo.org/viewtopic.php?t=35539

It turns out that that ebuild is buggy. This has already been filed:

http://bugs.gentoo.org/show_bug.cgi?id=52725

a corrected build-docbook-catalog script is included in the bug filing. I tried to run that and now my file /etc/xml/docbook has been created correctly... But the docbook2pdf problem still persists. Here follows the execution output on the same file:

Code: Select all

$ docbook2pdf dummy.xml
Using catalogs: /usr/share/sgml/docbook/sgml-dtd-4.1/catalog, /usr/share/sgml/docbook/sgml-dtd-3.0/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.77/catalog, /usr/share/sgml/docbook/sgml-dtd-4.0/catalog, /usr/share/sgml/docbook/sgml-dtd-3.1/catalog, /usr/share/sgml/sgml-iso-entities-8879.1986/catalog, /usr/share/sgml/openjade-1.3.2/catalog, /usr/share/sgml/openjade-1.3.2/dsssl/catalog, /usr/share/sgml/xml-iso-entities-8879.1986/catalog
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /home/tempest/articles/dummy.xml
jade:/home/tempest/articles/dummy.xml:2:118:E: URL not supported by this version
Ideas?
For every problem there is a solution that is simple, neat, and wrong.
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Mon Jun 28, 2004 7:40 pm

I've just tried the docbook-utils/docbook-utils-pdf suite on a freshly installed Mandrake 10.0 . The execution of the utilities (on the already introduced dummy.xml) gives me this output:

Code: Select all

tempest@vmware tempest $ docbook2pdf dummy.xml
Using catalogs: /etc/sgml/xml-docbook.cat
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print
Working on: /home/tempest/dummy.xml
And the PDF comes out correctly. I'm posting this hoping it to be useful for the developers.

BTW, in the previous post I forgot to specify that on the Gentoo host the result file is not produced.
For every problem there is a solution that is simple, neat, and wrong.
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Wed Jul 07, 2004 12:01 pm

I feel that this topic should really be moved to Portage and Programming, because the ebuilds related to the involved software are probably messed up; at least this is how I see the situation, I'd be glad to be corrected.

Readers of this topic, it would be nice if you tried to execute

Code: Select all

docbook2pdf dummy.xml
(dummy.xml follows)

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article>
<articleinfo>
<title>dummy title</title>
</articleinfo>
 
<para>dummy text</para>
 
</article>
on your own gentoo box, and report your output.
For every problem there is a solution that is simple, neat, and wrong.
Top
bsolar
Bodhisattva
Bodhisattva
User avatar
Posts: 2764
Joined: Sun Jan 12, 2003 5:14 pm

  • Quote

Post by bsolar » Wed Jul 07, 2004 7:29 pm

Moved from Other Things Gentoo.
I may not agree with what you say, but I'll defend to the death your right to say it.
Top
robmoss
Retired Dev
Retired Dev
Posts: 2634
Joined: Tue May 27, 2003 4:42 pm
Location: Jesus College, Oxford
Contact:
Contact robmoss
Website

  • Quote

Post by robmoss » Wed Jul 07, 2004 7:45 pm

Hmmm, well it's a pretty bad thing for this to be broken. When I get my x86 box up again later I'll have a go and see whether I can fix the ebuild.
Reality is for those who can't face Science Fiction.

emerge -U will kill your Gentoo
ecatmur, Lord of Portage Bash Scripts
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Tue Jul 13, 2004 12:18 pm

I gave another shot at this issue: you can use the option -n and -c catalog_file to select manually a catalog to use. This didn't solve anything but could be useful for developers reading this thread:

Code: Select all

$ docbook2pdf -n -c /usr/share/sgml/docbook/xml-dtd-4.2/docbook.cat dummy.xml
Using catalogs: /usr/share/sgml/docbook/xml-dtd-4.2/docbook.cat
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /home/tempest/dummy.xml
jade:/home/tempest/dummy.xml:2:118:E: URL not supported by this version
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:5:73:W: cannot generate system identifier for public text "-//James Clark//DTD DSSSL Style Sheet//EN"
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:13:97:W: cannot generate system identifier for public text "-//Norman Walsh//DOCUMENT DocBook Print Stylesheet//EN"
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:15:0:E: reference to entity "STYLE-SHEET" for which no system identifier could be generated
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:5:0: entity was defined here
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:13:1:E: notation "DSSSL" for entity "docbook.dsl" undefined
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:19:26:E: there is no attribute "ID"
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:19:38:E: there is no attribute "USE"
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:113:29:E: there is no attribute "ID"
jade:/usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl:113:48:E: there is no attribute "DOCUMENT"
jade:E: specification document does not have the DSSSL architecture as a base architecture
jade:E: no style-specification or external-specification with ID "PRINT"
BTW, dummy.xml is still the same file reported in the last posts.

Once again I'd like to hear from people reading this topic if I'm the only one suffering of this problem.
For every problem there is a solution that is simple, neat, and wrong.
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Wed Aug 18, 2004 10:20 pm

Today I have updated docbook-xml-dtd to version 4.3 and the related build-docbook-catalog 1.2.

This didn't fix any of the problems reported in the previous posts. Again, am I the only one suffering of this trouble?
For every problem there is a solution that is simple, neat, and wrong.
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Fri Sep 10, 2004 5:03 pm

Someone suggested that things might start to work using SGML instead of XML, so i promptly prepared dummy2.sgml:

Code: Select all

<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN">
<book>
        <bookinfo>
                <title>Dummy title</title>
        </bookinfo>
        <chapter>
                <title>Dummy chapter</title>
                <para>Dummy para</para>
        </chapter>
</book>
I can't imagine a simpler sgml docbook document, so I used this one.

Tried to produce PDF with docbook2pdf:

Code: Select all

$ docbook2pdf dummy2.sgml
Using catalogs: /etc/sgml/sgml-docbook-4.2.cat
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /home/tempest/dummy2.sgml
This is pdfTeX, Version 3.14159-1.10b (Web2C 7.4.5)
(Fatal format file error; I'm stymied)
Tried to handle it manually, using openjade:

Code: Select all

$ openjade -t sgml -d /usr/share/sgml/docbook/dsssl-stylesheets-1.77/html/docbook.dsl dummy2.sgml
openjade:dummy2.sgml:1:54:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V4.2//EN"
openjade:dummy2.sgml:1:54:E: reference to entity "BOOK" for which no system identifier could be generated
openjade:dummy2.sgml:1:0: entity was defined here
openjade:dummy2.sgml:1:54:E: DTD did not contain element declaration for document type name
openjade:dummy2.sgml:2:5:E: element "BOOK" undefined
openjade:dummy2.sgml:3:10:E: element "BOOKINFO" undefined
openjade:dummy2.sgml:4:8:E: element "TITLE" undefined
openjade:dummy2.sgml:6:9:E: element "CHAPTER" undefined
openjade:dummy2.sgml:7:8:E: element "TITLE" undefined
openjade:dummy2.sgml:8:7:E: element "PARA" undefined
I'm changing the title of this topic to "Docbook support in Gentoo is broken", since all the dummy files I tried can be converted flawlessly using the docbook utils shipped with other distros.
For every problem there is a solution that is simple, neat, and wrong.
Top
AerisG222
n00b
n00b
User avatar
Posts: 39
Joined: Mon Aug 25, 2003 5:41 pm
Location: Quincy, MA

you aren't alone

  • Quote

Post by AerisG222 » Mon Nov 29, 2004 9:34 pm

I am just starting to try and create documentation using docbook, and ran into difficulties generating PDF output using xmlto. After finding your post, I tried your first XML sample, and I got similar results. I was able to generate XHTML output using xmlto, however the PDF output did not work at all.

Looking a bit further into this, I think the problem is in one of the xmltex tools xmlto invokes, not xmlto itself. Anyways, here is the output that I get when I try to generate the PDF file.

Code: Select all

Format script: /usr/share/xmlto/format/docbook/pdf
Convert to XSL-FO
Real stylesheet: http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl
xmllint >/dev/null --xinclude --postvalid /home/mmorano/code/docbook/test/test.docbook
Stylesheet: /tmp/xmlto-xsl.FVH1iE
xsltproc --nonet --xinclude \
 -o /tmp/xmlto.t5L81G/test.proc \
 /tmp/xmlto-xsl.FVH1iE \
 /home/mmorano/code/docbook/test/test.docbook
Making portrait pages on A4 paper (210mmx297mm)
Post-process XSL-FO to PDF
This is pdfTeX, Version 3.14159-1.10b (Web2C 7.4.5)
(./tmp.fo{/usr/share/texmf/pdftex/config/pdftex.cfg}
xmltex version: 2002/06/25 v1.9 (Exp):
(/usr/share/texmf/tex/xmltex/xmltex.cfg)
! I can't find file `tmp.cfg'.
\@filef@und ->\jobname .cfg 
                            
...
l.1 
    <?xml version="1.0"?>
Please type another input file name: 
! Emergency stop.
\@filef@und ->\jobname .cfg 
                            
...
l.1 
    <?xml version="1.0"?>
No pages of output.
Transcript written on tmp.log.

I have tried re-emerging a number of the docbook related packages, without success. The following are the packages I currently have installed (in case it matters, I am running AMD64):

Code: Select all

     dev-libs/libxslt-1.1.9-r1 
     net-libs/libwww-5.4.0-r2 
     app-text/tetex-2.0.2-r4 
     app-text/jadetex-3.12 
     dev-tex/xmltex-1.9-r1 
     app-text/passivetex-1.4-r1 
     app-text/xmlto-0.0.18 
     app-text/docbook-dsssl-stylesheets-1.77-r2 
     app-text/docbook-sgml-dtd-4.2-r1 
     app-text/docbook-sgml-utils-0.6.12 
     app-text/docbook-xml-dtd-4.3 
     app-text/docbook-xml-simple-dtd-4.1.2.4 
     app-text/docbook-xsl-stylesheets-1.65.1 
     app-text/openjade-1.3.2-r1 
     app-text/opensp-1.5-r1 
     app-text/sgml-common-0.6.3-r4 
Has anyone been able to successfully generate PDFs from their docbooks?

Also, in anticipation of getting this working, I think I will have another question. It looks like the PDF will be created with a paper size of A4, however, I would rather US-Letter for my needs. How would I specify that I would prefer US-Letter? Looking through the xmlto script, it automatically tries to determine the paper size by using output from locale LC_PAPER, however, it is not clear to me how I would change this to be a different size.

TIA!
Mike
Top
AerisG222
n00b
n00b
User avatar
Posts: 39
Joined: Mon Aug 25, 2003 5:41 pm
Location: Quincy, MA

quick followup

  • Quote

Post by AerisG222 » Tue Nov 30, 2004 11:28 am

I tried downgrading some packages, and now am getting PDF output, although it is not as I expected.

I am now using:

Code: Select all

xmlto-0.0.17
xmltex-1.9
libxslt-1.1.8
passivetex-1.25
I'll have to look more into why seemingly random "4ch" is appearing near the article title now, but this is much better than before :)

Does anyone have any thoughts on papersize?

TIA,
Mike
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Thu Dec 23, 2004 10:27 pm

I know I'm going to bore people out there, but the situation is much worse than it seemed to be.

Today I performed a new, fresh install of Gentoo 2004.3-r1, using stage3 and GRP, for a friend of mine; at the end of the day I launched

# emerge docbook-sgml-utils

on the fresh system, and tried to convert to pdf dummy.xml and dummy2.sgml, with docbook2pdf.

Guess what?

Code: Select all

# docbook2pdf dummy.xml
Using catalogs: /usr/share/sgml/opensp-1.5/OpenSP/catalog, /usr/share/sgml/sgml-iso-entities-8879.1986/catalog, /usr/share/sgml/xml-iso-entities-8879.1986/catalog, /usr/share/sgml/openjade-1.3.2/catalog, /usr/share/sgml/openjade-1.3.2/dsssl/catalog, /usr/share/sgml/docbook/sgml-dtd-4.1/catalog, /usr/share/sgml/docbook/sgml-dtd-4.0/catalog, /usr/share/sgml/docbook/dsssl-stylesheets-1.77/catalog, /usr/share/sgml/docbook/sgml-dtd-3.0/catalog, /usr/share/sgml/docbook/sgml-dtd-3.1/catalog
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /root/dummy.xml
jade:/root/dummy.xml:2:118:E: URL not supported by this version
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl:53:130:Q: number of ID references in start-tag must not exceed GRPCNT (32)
jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.77/print/docbook.dsl:52:0:Q: number of ID references in start-tag must not exceed GRPCNT (32)

Code: Select all

# docbook2pdf dummy2.sgml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/sgml/docbook/utils-0.6.12/docbook-utils.dsl#print
Working on: /root/dummy2.sgml
jade:/root/dummy2.sgml:1:54:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook V4.2//EN"
jade:/root/dummy2.sgml:1:54:E: reference to entity "BOOK" for which no system identifier could be generated
jade:/root/dummy2.sgml:1:0: entity was defined here
jade:/root/dummy2.sgml:1:54:E: DTD did not contain element declaration for document type name
jade:/root/dummy2.sgml:2:5:E: element "BOOK" undefined
jade:/root/dummy2.sgml:3:17:E: element "BOOKINFO" undefined
jade:/root/dummy2.sgml:4:22:E: element "TITLE" undefined
jade:/root/dummy2.sgml:6:16:E: element "CHAPTER" undefined
jade:/root/dummy2.sgml:7:22:E: element "TITLE" undefined
jade:/root/dummy2.sgml:8:21:E: element "PARA" undefined
Something is definitely wrong inside Gentoo. Note that I can flawlessy parse the same files with docbook2pdf on many other random distro: tried with latest Fedora, Mandrake and Debian.
For every problem there is a solution that is simple, neat, and wrong.
Top
AerisG222
n00b
n00b
User avatar
Posts: 39
Joined: Mon Aug 25, 2003 5:41 pm
Location: Quincy, MA

more success, different tool

  • Quote

Post by AerisG222 » Thu Dec 23, 2004 10:59 pm

I have stuck with the XML side of docbook. I was not able to get decent pdf output using xmlto to generate directly to pdf (via passivetex and the rest of these tools). However, I did the following:

Code: Select all

emerge fop
And then executed

Code: Select all

xmlto fo mybook.dbx
fop mybook.fo -pdf mybook.pdf
and this generated a much nicer looking pdf file than using xmlto directly. Using fop requires you to install a bunch of java related utilities, but it worked for me first try. Note there were some warnings, and there are things I will want to do to tweak the output, but it seems to be more mature than the alternative.
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Thu Dec 23, 2004 11:11 pm

AerisG222, thanks for the tip... I will experiment with it in the following days when I'm back to work.

Anyway the issue remains: docbook2* utils do not work in Gentoo, neither for XML nor for SGML. I'm hoping that some developers read this...
For every problem there is a solution that is simple, neat, and wrong.
Top
cerealito
n00b
n00b
User avatar
Posts: 20
Joined: Sat Apr 10, 2004 5:09 pm
Location: Toulouse, Fr
Contact:
Contact cerealito
Website

Oh boy!

  • Quote

Post by cerealito » Fri Dec 24, 2004 6:53 am

I was searching a tool to handle all the text of my thesis report, and then i read about docbook... I started to read some tutorials and to experimet with it. After some time I gave up... I just couldnt get a decent pdf... Now i see why!!!

I hope this can be fixed soon. Mean while, i'll stick to OO and styles... :P
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Fri Dec 31, 2004 6:04 pm

cerealito wrote:I just couldnt get a decent pdf
As far as I tried, you can't get any pdf, be it decent or not, with the docbook2* utils shipped with Gentoo. And we're talking about the very same utils that work flawlessly in other distros.

I just don't get it, and I'm surprised that very few people have shown up on this thread to talk about it, maybe no one cares about Docbook support? I hope that the upcoming year will bring a solution to this problem...
For every problem there is a solution that is simple, neat, and wrong.
Top
g1ul10
n00b
n00b
User avatar
Posts: 11
Joined: Wed Dec 01, 2004 8:17 am

  • Quote

Post by g1ul10 » Sun Jan 02, 2005 2:09 pm

Hi All,

I've been able to obtain a pdf file from the sample xml file posted by tempest using xmlto. The command line is

Code: Select all

xmlto -v pdf sample.xml
generating the following oputput

Code: Select all

Format script: /usr/share/xmlto/format/docbook/pdf
Convert to XSL-FO
Real stylesheet: http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl
xmllint >/dev/null --xinclude --postvalid /home/giulio/work/software/gbutils/sample.xml
Stylesheet: /tmp/xmlto-xsl.5aqwT5
xsltproc --nonet --xinclude \
 -o /tmp/xmlto.O1l6W8/sample.proc \
 /tmp/xmlto-xsl.5aqwT5 \
 /home/giulio/work/software/gbutils/sample.xml
Making portrait pages on A4 paper (210mmx297mm)
Post-process XSL-FO to PDF
xmlto -v pdf sample.xml  10.21s user 0.33s system 88% cpu 11.918 total
and the file 'sample.pdf' which seems OK.

I've the following installed
  • app-text/xmlto-0.0.15
    dev-tex/xmltex-1.9
    app-text/passivetex-1.25
    dev-libs/libxslt-1.1.9-r1
I've obtained pdf files with strange characters from a document I had pre-processed with AsciiiDoc, like the ones mentioned by AerisG222. The sample file by Tempest, however, does not generate these characters.
Maybe the problem is in AsciiDoc and not in xmlto. More investigations needed.
Top
tigrezno
Apprentice
Apprentice
User avatar
Posts: 251
Joined: Fri Jun 28, 2002 12:14 pm
Location: Spain
Contact:
Contact tigrezno
Website

  • Quote

Post by tigrezno » Sun Jan 02, 2005 2:44 pm

mmmm people can you read???

from the first post:

jade:/home/tempest/articles/dummy.xml:2:118:E: URL not supported by this version


As you can see it's not an error of gentoo, what is happening is that openjade don't support accessing remote URLs within xml documents. In the XML document there is a remote URL for accessing the catalog, just remove it and change to your local catalog, search for it under /usr/share/sgml IIRC.
Ruby => "0100007F".unpack('x6a2X4a2X4a2X4a2').collect{ |byte| byte.hex }.join(".")
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Sun Jan 02, 2005 6:13 pm

Hi tigrezno, yes my friend I can read. A more appropriate question is...
tempest wrote:Note that I can flawlessy parse the same files with docbook2pdf on many other random distro
...can you?

Those xml files are parsed correctly using all the distros I tried, so I think the problem is somewhere in Gentoo's DocBook integration, and that's why I mentioned the problem here.

I'm not going to modify the xml source files; that's not because I'm lazy, it's just because they are correct XML DocBook documents as they are; that's enough for me and should be so for the parser as well.
For every problem there is a solution that is simple, neat, and wrong.
Top
tigrezno
Apprentice
Apprentice
User avatar
Posts: 251
Joined: Fri Jun 28, 2002 12:14 pm
Location: Spain
Contact:
Contact tigrezno
Website

  • Quote

Post by tigrezno » Sun Jan 02, 2005 6:15 pm

tempest wrote:Hi tigrezno, yes my friend I can read. A more appropriate question is...
tempest wrote:Note that I can flawlessy parse the same files with docbook2pdf on many other random distro
...can you?

Those xml files are parsed correctly using all the distros I tried, so I think the problem is somewhere in Gentoo's DocBook integration, and that's why I mentioned the problem here.

I'm not going to modify the xml source files; that's not because I'm lazy, it's just because they are correct XML DocBook documents as they are; that's enough for me and should be so for the parser as well.
Well, then try generating the pdf without internet conection.
Ruby => "0100007F".unpack('x6a2X4a2X4a2X4a2').collect{ |byte| byte.hex }.join(".")
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Sun Jan 02, 2005 6:51 pm

I guess that the last one was a bit of sarcasm from you :wink: I didn't want to sound offensive so forgive me if it seemed so.

Of course my documents might be correctly parsed with the URL removed, there's no reason why they shouldn't. My point is: why should I modify the same files that work flawlessly with the very same version of jadetex, openjade, docbook2*, on other distros?

That's the reason I'm suggesting that the bug is somewhere in Gentoo's DocBook integration.
For every problem there is a solution that is simple, neat, and wrong.
Top
tigrezno
Apprentice
Apprentice
User avatar
Posts: 251
Joined: Fri Jun 28, 2002 12:14 pm
Location: Spain
Contact:
Contact tigrezno
Website

  • Quote

Post by tigrezno » Mon Jan 03, 2005 12:47 am

please, emerge opensp 1.5.1, it uses --enable-http that 1.5-r1 (Stable) don't use, or add --enable-http to 1.5-r1 ebuild.
Ruby => "0100007F".unpack('x6a2X4a2X4a2X4a2').collect{ |byte| byte.hex }.join(".")
Top
tigrezno
Apprentice
Apprentice
User avatar
Posts: 251
Joined: Fri Jun 28, 2002 12:14 pm
Location: Spain
Contact:
Contact tigrezno
Website

  • Quote

Post by tigrezno » Mon Jan 03, 2005 10:36 am

tempest wrote:I guess that the last one was a bit of sarcasm from you :wink: I didn't want to sound offensive so forgive me if it seemed so.

Of course my documents might be correctly parsed with the URL removed, there's no reason why they shouldn't. My point is: why should I modify the same files that work flawlessly with the very same version of jadetex, openjade, docbook2*, on other distros?

That's the reason I'm suggesting that the bug is somewhere in Gentoo's DocBook integration.
The reason is just simple, you should not depend on internet conection to generate your content when you have the same catalog in your hard disk. If your conection goes down, then you can't generate content, is this good? i don't think so, but it's only my opinion.
Ruby => "0100007F".unpack('x6a2X4a2X4a2X4a2').collect{ |byte| byte.hex }.join(".")
Top
tempest
n00b
n00b
User avatar
Posts: 44
Joined: Fri Jun 18, 2004 7:56 pm

  • Quote

Post by tempest » Wed Jan 05, 2005 9:02 pm

tigrezno wrote:please, emerge opensp 1.5.1, it uses --enable-http that 1.5-r1 (Stable) don't use, or add --enable-http to 1.5-r1 ebuild.
You're the man! That was the ticket, I had already noticed the --enable-http option but only in openjade's ebuild, and it didn't come to my mind that opensp could have such an option too.

To summarize it all up, here's the patch for opensp-1.5-r1.ebuild:

Code: Select all

@@ -37,6 +37,7 @@
        # Detect mips systems properly
        gnuconfig_update

+       myconf="${myconf} --enable-http"
        myconf="${myconf} --enable-default-catalog=/etc/sgml/catalog"
        myconf="${myconf} --enable-default-search-path=/usr/share/sgml"
        myconf="${myconf} --datadir=/usr/share/sgml/${P}"
If someone of the devs is looking: could this one be officially added to the portage tree? I don't feel like reporting in bugzilla since it's not a real bug of the ebuild...
tigrezno wrote:The reason is just simple, you should not depend on internet conection to generate your content when you have the same catalog in your hard disk. If your conection goes down, then you can't generate content, is this good? i don't think so, but it's only my opinion.
In my situation this is not a real problem since the content is autogenerated nightly with a script on a machine that is (should be?) up 24/7. The real reason for the link to a remote catalog is that I don't own the machine, so I have limited freedom on the software installed on it. I have thought up possible solutions but this is not the right topic to talk about them :wink:

For those not willing to read the whole topic: there's no docbook integration trouble in Gentoo, the problem was an unspecified option to opensp configure in the relative x86 ebuild, and that option is already present in the opensp ebuild currently in ~x86.

I'm marking this one as [solved].
For every problem there is a solution that is simple, neat, and wrong.
Top
Post Reply

36 posts
  • 1
  • 2
  • Next

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy