Re: pslatex code contaminating the gnuplot core

[Harald H. <h.h...@tu...>]

On Tue, 1 Mar 2005, Daniel J Sebald wrote:

> Ethan Merritt wrote:
> > By the way, in trying to build gnuplot without the postscript
> > terminal driver I discovered that the recent commingling of
> > postscript/pslatex/epslatex has made this impossible.
> >
> > In particular I object to the following contamination of core
> > routines with terminal-specific code.  If we need a new terminal
> > entry for this, then so be it. But having the core code writing
> > this garbage is just really really ugly.
>
> Oo, yes.  Don't start this sort of thing.  There must be a good solution to this inside the terminal
> driver, e.g., static variables for remembering when to put this string in the LaTeX file.  Harald?
>
> > -    /* Print \includegraphics here when using back option for text */
> > -    if (term->name=="epslatex" && gpoutfile)
> > -       fprintf(gpoutfile, "    \\put(0,0){\\includegraphics{%s}}%%\n",
> > -               pslatex_auxname);

This was the only possibility to enable the user to use the keywords
'front' and 'back' for 'labels'. With "terminal entry", do you mean a new
member in the TERMENTRY struct? It could be something like
    void (*place_plot) __PROTO((void));
that does nothing by default and writes the above line to the output file
if defined:

graphics.c, graph3d.c, and term.c:

    if (term->place_plot)
        (*term->place_plot)();

post.trm:

TERM_PUBLIC void
PS_place_plot()
{
    if (term->name=="epslatex" && gpoutfile)
        fprintf(gpoutfile, "    \\put(0,0){\\includegraphics{%s}}%%\n",
                pslatex_auxname);
}

Shall I write a patch and upload it to sourceforge?

-- 
Harald Harders
h.h...@tu...
http://www.harald-harders.de