Hi Taco, hi all, I was just playing around to get 0.51.0 compiled with libpopper, without success unfortunately. I have already one patch in my patch queue to help (for the pdf version, see attached patch), but there is a new problem which I tried to find a way around without success. Maybe someone here has an idea: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc: In function ‘void write_epdf1(pdf_output_file*, image_dict*)’: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:663: error: ‘class Page’ has no member named ‘getResourcesNF’ ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:669: error: ‘class Page’ has no member named ‘getMetadataNF’ I checked the header files from poppler and there is nothing like *NF :-( Thanks for any suggestions, and all the best Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TU Wien, Austria Debian TeX Task Force DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ He expanded his chest to make it totally clear that here was the sort of man you only dared to cross if you had a team of Sherpas with you. --- Douglas Adams, The Hitchhikers Guide to the Galaxy
On Sun, 14 Mar 2010, Norbert Preining wrote:
I was just playing around to get 0.51.0 compiled with libpopper, without success unfortunately.
I have already one patch in my patch queue to help (for the pdf version, see attached patch), but there is a new problem which I tried to find a way around without success. Maybe someone here has an idea: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc: In function ?void write_epdf1(pdf_output_file*, image_dict*)?: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:663: error: ?class Page? has no member named ?getResourcesNF? ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:669: error: ?class Page? has no member named ?getMetadataNF?
I checked the header files from poppler and there is nothing like *NF :-(
Thanks for any suggestions, and all the best
well, i had patched xpdf-3.02 in the luatex distro, see SVN 3304, source/libs/xpdf/xpdf-3.02/xpdf/Page.h no real idea yet how to make this consistent with poppler. Regards, Hartmut
2010/3/14 Norbert Preining
I have already one patch in my patch queue to help (for the pdf version, see attached patch), but there is a new problem which I tried to find a way around without success. Maybe someone here has an idea: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc: In function ‘void write_epdf1(pdf_output_file*, image_dict*)’: ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:663: error: ‘class Page’ has no member named ‘getResourcesNF’ ../../../source/texk/web2c/luatexdir/image/pdftoepdf.cc:669: error: ‘class Page’ has no member named ‘getMetadataNF’
Hartmut forked our version of xpdf in r3304.
I checked the header files from poppler and there is nothing like *NF :-(
That's because it's a local addition to xpdf. I see two options: 1. create a layer between xpdf/poppler and luatex like in pdftex 1.50 2. push changes like these upstream (i.e. to poppler) so that they get integrated there Hartmut? Best Martin
2010/3/14 Martin Schröder
Hartmut forked our version of xpdf in r3304.
And our current file in source/libs/xpdf/xpdf-3.02/xpdf/Page.h since then violates the GPL, section 2a. See also https://bugs.freedesktop.org/show_bug.cgi?id=16518 Best Martin
On So, 14 Mär 2010, Hartmut Henkel wrote:
well, i had patched xpdf-3.02 in the luatex distro, see SVN 3304, source/libs/xpdf/xpdf-3.02/xpdf/Page.h
On So, 14 Mär 2010, Martin Schröder wrote:
Hartmut forked our version of xpdf in r3304.
Ouch. That will make at least the distributors unhappy.
1. create a layer between xpdf/poppler and luatex like in pdftex 1.50
Probably hard according to Hartmuts remarks on "no idea how to make that consistent with poppler".
2. push changes like these upstream (i.e. to poppler) so that they get integrated there
Hahaha, Martin, wasn't it you complaining about them at one of the BachoTeXs? Well, I am not sure how to proceed. And I am not sure how happy Debian (and probably other) security guys will be about the reintroduction of code duplication etc. But if it is the only way to go, although I am unhappy, so it be. I mean, we could have saved us all the work last year to convert TeX Live to a way that it compiles both wiht poppler and xpdf, only to see that it will soon break again ... :-( Best wishes Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TU Wien, Austria Debian TeX Task Force DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ TIDPIT (n.) The corner of a toenail from which satisfying little black deposits may be sprung. --- Douglas Adams, The Meaning of Liff
2010/3/14 Norbert Preining
On So, 14 Mär 2010, Martin Schröder wrote:
Hartmut forked our version of xpdf in r3304.
Ouch. That will make at least the distributors unhappy.
1. create a layer between xpdf/poppler and luatex like in pdftex 1.50
Probably hard according to Hartmuts remarks on "no idea how to make that consistent with poppler".
I doubt it. At the end you have to adapt only two files for poppler. http://preview.tinyurl.com/yk9uqm7 http://preview.tinyurl.com/yghn92f
2. push changes like these upstream (i.e. to poppler) so that they get integrated there
Hahaha, Martin, wasn't it you complaining about them at one of the BachoTeXs?
It's unlikely, but remains possible. :-) Taco? Best Martin
On So, 14 Mär 2010, Martin Schröder wrote:
1. create a layer between xpdf/poppler and luatex like in pdftex 1.50
Probably hard according to Hartmuts remarks on "no idea how to make that consistent with poppler".
I doubt it. At the end you have to adapt only two files for poppler. http://preview.tinyurl.com/yk9uqm7 http://preview.tinyurl.com/yghn92f
Hmm, that sounds interesting, esp. also for xetex, so if all would use that it would be easier ...
Hahaha, Martin, wasn't it you complaining about them at one of the BachoTeXs?
It's unlikely, but remains possible. :-)
Hmm, that talk about alternatives of pdf libraries ... Best wishes Norbert ------------------------------------------------------------------------ Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TU Wien, Austria Debian TeX Task Force DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 ------------------------------------------------------------------------ BROUGH SOWERBY One who has been working at that same desk in the same office for fifteen years and has very much his own ideas about why he is continually passed over for promotion. --- Douglas Adams, The Meaning of Liff
On Sun, 14 Mar 2010, Martin Schröder wrote:
2010/3/14 Norbert Preining
: On So, 14 Mär 2010, Martin Schröder wrote:
Hartmut forked our version of xpdf in r3304.
Ouch. That will make at least the distributors unhappy.
1. create a layer between xpdf/poppler and luatex like in pdftex 1.50
Probably hard according to Hartmuts remarks on "no idea how to make that consistent with poppler".
I doubt it. At the end you have to adapt only two files for poppler. http://preview.tinyurl.com/yk9uqm7 http://preview.tinyurl.com/yghn92f
2. push changes like these upstream (i.e. to poppler) so that they get integrated there
Hahaha, Martin, wasn't it you complaining about them at one of the BachoTeXs?
It's unlikely, but remains possible. :-)
Taco?
fwiw, i have sent diffs to Derek, in the hope that he integrates them upstream. Let's see... Regards, Hartmut
participants (3)
-
Hartmut Henkel
-
Martin Schröder
-
Norbert Preining