|
From: Petr M. <mi...@ph...> - 2004-10-04 06:25:27
|
> > I think that the epslatex driver should use postscript_gpoutfile for its > > aux output, not its new gpauxfile. That's because there are tests within the > > gnuplot core for this output, and then a postscript-optimized code is > > shipped out (e.g. pm3d routines). Have you tested your epslatex with pm3d > > output? I guess it would fail. > > I have never understood the sence of postscript_gpoutfile. What it is ment > for? Added for the (e)ps(la)tex family: ChangeLog.0-2000-11-20 Petr Mikulik <mi...@ph...> ChangeLog.0- ChangeLog.0- * src/: color.c pm3d.c term.c term_api.h ChangeLog.0- term/: epslatex.trm pslatex.trm post.trm ChangeLog.0: pm3d: added 'FILE *postscript_gpoutfile' which is set to ChangeLog.0- 'PSLATEX_auxfile' or 'gpoutfile' or '0' according to 'set term', ChangeLog.0- i.e. to the file where the postscript code goes to (if outputted). ChangeLog.0: Condition 'if (!postscript_gpoutfile)' can be used to distinguish ChangeLog.0- postscript terminals family (used in postscript optimized output ChangeLog.0- in pm3d). That's why I think your epslatex should use it as well. Now I see that the surrounding #ifdef PM3D ... #endif should be removed, and that postscript_gpoutfile should be always useable. See also here: term_api.h-#ifdef PM3D term_api.h-/* Output file where the PostScript output goes to. term_api.h- In particular: term_api.h: postscript_gpoutfile == gpoutfile term_api.h- for 'set term': postscript, pstex term_api.h: postscript_gpoutfile == PSLATEX_auxfile term_api.h- for 'set term': pslatex term_api.h: postscript_gpoutfile == 0 term_api.h- for all other terminals term_api.h- It is non-zero for for the family of postscript terminals, thus making term_api.h- this a unique check for postscript output (pm3d has some code optimized term_api.h- for PS, for instance). term_api.h-*/ term_api.h:extern FILE *postscript_gpoutfile; term_api.h-#endif -- PM |