From: Matt N. <new...@ca...> - 2006-01-23 23:36:03
|
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 |
From: Christopher B. <Chr...@no...> - 2006-04-24 17:55:49
|
Darren Dale wrote: > The basic approach is to extract the font layout information from the > dvi files. LaTeX could be the only dependency. Wonderful idea! I've been hoping someone would write this for ages. This could lead to using TeX as a layout engine for creating Reports, etc. in all kinds of other apps as well. I'm looking forward to seeing how it works out. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Alan G I. <ai...@am...> - 2006-04-24 18:33:11
|
> Darren Dale wrote: >> The basic approach is to extract the font layout information from the >> dvi files. LaTeX could be the only dependency. On Mon, 24 Apr 2006, Christopher Barker apparently wrote: > Wonderful idea! I've been hoping someone would write this for ages. This > could lead to using TeX as a layout engine for creating Reports, etc. in > all kinds of other apps as well. Is this the PyX approach? I ask that in hopes there may synergies that save some developer time. Cheers, Alan Isaac |
From: John H. <jdh...@ac...> - 2006-04-24 18:36:23
|
>>>>> "Alan" == Alan G Isaac <ai...@am...> writes: Alan> Is this the PyX approach? I ask that in hopes there may Alan> synergies that save some developer time. pyx is GPL -- we've contacted them about relicensing their code but got nowhere. JDH |
From: Christopher B. <Chr...@no...> - 2006-04-24 20:08:26
|
John Hunter wrote: >>>>>> "Alan" == Alan G Isaac <ai...@am...> writes: > Alan> Is this the PyX approach? I ask that in hopes there may > Alan> synergies that save some developer time. > > pyx is GPL -- we've contacted them about relicensing their code but > got nowhere. I didn't think it was the PyX approach anyway, but I just took another look. Does anyone know for sure? In PyX's case, it is going from TeX to PS, so I think it might use dvips or something to do that. rather than reading and rendering the DVI itself. Speaking of which, perhaps pdfTeX is an option. I think pdfTeX generates pdf directly, which we could either just use, or maybe parse. I don't know if that would be harder or easier than DVI though. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Alan G I. <ai...@am...> - 2006-04-24 20:23:36
|
On Mon, 24 Apr 2006, Christopher Barker apparently wrote: > I think it might use dvips or something to do that. rather than > reading and rendering the DVI itself. That is not my understanding, which however is limited. Cheers, Alan Isaac PS I have tried to reopen the discussion with the PyX developers. I'll post any useful outcomes. |