Jose and all,
I feel I should note here that in the xpdf 3.03 release, Derek has
changed the licensing to GPLv2 | GPLv3.
However, since that is still not GPLv2+ (or GPLv3+), I see no way for
GNU PDF to use any code from there, still, because of the possibility of
a GPLv4 someday. Unless you want
/www.mail-archive.com/blank.png";
google_ad_width = 160;
google_ad_height = 600;
google_ad_format = "160x600_as";
google_ad_channel = "8427791634";
google_color_border = "FF";
google_color_bg = "FF";
google_color_link = "006792";
google_colo
I am using texi2pdf and texi2dvi in some software I am developing
and was wondering what the plans were, if any, to integrate the
Texinfo tool chain with the GNU PDF work.
Sorry, I have no clue what that means! Texinfo uses, of course, pdftex
to generate PDF, and I find it hard to fat
P.S. Another approach to the gl*.h problem would be to copy them from
gnulib into the source tree in the standard way, but then have the
gnupdf build process copy them to (say) pdf_list.h. Then that could be
installed and you wouldn't have to deal with physical inclusion, which
granted is pretty w
OTOH, I'm not totally sure about the inclusions of "stddef.h" and
"stdbool.h" which are needed by gl_list and whose include directives
are in "pdf-types.h". They may not be portable across platforms and
they're small enough that we could create our own versions.
Gnulib goes to a l
If you think it's not a good idea to modify those headers we should
copy them to another location and modify them there. I guess it's
the same.
What? This makes no sense to me.
As we already discussed, Gnulib headers should not be modified in your
source tree (then you can't update t
What I meant is to _phisically_ include gl_list.h and its
dependencies in pdf.h.
That would be ok.
If with "distribute" you mean installing gl_list.h in /usr/local/include/
Indeed, gl_anything.h should not be installed, for a couple reasons --
1) the whole purpose of gnulib is to be
BTW, distributing gnulib headers along with
pdf.h is also a bad idea, isn't it?
I don't see anything very problematic with distributing them.
So the public API shouldn't depend
on any data type coming from those headers.
That indeed may be troublesome -- you wouldn't want a PD
Uff sorry :-) The file gl_list.h is downloaded from the Gnulib
repository using `gnulib-tool import', and I am not sure if it's a good
You definitely don't want to modify anything that comes from gnulib.
That would defeat the whole purpose of gnulib.
