Menu
▾
▴
Re: [Matplotlib-users] Re: [matplotlib-devel] doing tex support the right way
|
From: Darren D. <dd...@co...> - 2006-01-24 00:19:14
|
On Monday 23 January 2006 19:06, Ryan Krauss wrote: > While the gnuplot approach of outputing an eps file plus a tex file > that does all the axis labeling is probably lots easier to implement, > I am nervous that if the tex file ever gets seperated from the eps > file, I am left with a plot with no axis or tick mark labels - or > labels that were accidentally editted. That may not be a big enough > concern to justify the extra work to parse the dvi, but it is a > concern of mine. > > It may be irrational on my part, but something about a single eps file > feels cleaner to me than the seperate eps and tex file approach. Actually, this was what the first incarnation of usetex looked like: a ps file and a separate latex file. In fact, it still does that, but I put a lot of work into hiding that from the user and making mpl do the extra work behind the scenes to deliver a single eps file. I didnt like the idea of having to insert an eps file and some latex code on top of it. What if the file is not destined for a latex document? I might want to use the image with all the fancy markup in a poster created with inkscape or adobe illustrator. > On 1/23/06, Matt Newville <new...@ca...> wrote: > > Hi Darren, > > > > It may be very different than what you're doing, but the hybrid > > approach of gnuplot's 'pslatex' terminal device might be worth > > considering and looking into. This writes postscript for the graphics > > part and leaves simple lines (for the axes) and the text as plain > > latex that overlays the postscript. I think for mpl, you might want > > to have all the non-text go into the postscript and all the text go > > into an accompanying latex file, but the idea is the same. > > > > One advantage there is portability, as the output is latex+embedded > > postscript (using \special). It also allows pretty fine-grained > > control on the output, including changing fonts or doing latex things > > that mpl can't do (and this can all be done after the fact, so that > > you can create the figure, and then change the fonts). It does > > require latex to create the figure, but this step could be automated, > > at least to stage of the dvi-with-eps-figure stage. Getting to ps, > > pdf, or png would be less easy to automate but may be doable in a > > portable way. > > > > That sounds easier than parsing a dvi file to me. And postscript > > backend already exists. > > > > > > --Matt > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files for problems? Stop! Download the new AJAX search engine that > > makes searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > > _______________________________________________ > > Matplotlib-users mailing list > > Mat...@li... > > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Darren S. Dale, Ph.D. Cornell High Energy Synchrotron Source Cornell University 200L Wilson Lab Rt. 366 & Pine Tree Road Ithaca, NY 14853 dd...@co... office: (607) 255-9894 fax: (607) 255-9001 |
