Re: DOCBOOK-APPS: Problem converting DB to PDF...
Nik Clayton <nik@nothing-going-on.demon.co.uk> writes:
> I don't want to do that. If I did, any one that wanted to build the
> documentation for a specific output format is going to need to have the
> same tools to hand as the original author -- I think this is too heavy a
> burden to force on people,
I'm not forcing any burden on people -- I am simply providing the
capability to convert between formats.
Some projects such as yours has a wide base of users building the
documentation, and they need to be careful. Some have very small,
controlled, bases of users, and they rightfully want all derived files
out of CVS.
So -- it's just a system feature that I can allow conversion right
from xfig format. No one has to use it -- they can keep their images
sources in .eps format, even if they were origianlly .fig files or
whatever. The application doesn't care :)
We should move off this one point -- it's getting tiresome.
> As far as I know, the pdftex defaults aren't overrides, they're just a
> default list of extensions to search. So if you tell pdftex "Include
> the image file with the name "figure1", it'll search for "figure1"
> first, then "figure1.png", then "figure1.pdf", and so on.
>
> All I do is change the search order, so that it'll include "figure1.pdf"
> in preference to "figure1.png".
>
> > > No. As the first step *after* (Open)Jade has generated the .tex file we
> > > prepend a line of TeX that makes sure the defaults are set to what we
> > > expect them to be.
> >
> > Oh, can I say "ew" to that?
>
> Yep. But I've learnt that expecting application defaults to change
> stable between releases is a bad idea.
Eh?
> Better to hardcode the defaults you want somewhere that you control,
> and enforce it rigorously.
Yeah.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: