From: John H. <jdh...@ac...> - 2005-06-01 18:27:27
|
>>>>> "Chris" == Chris Barker <Chr...@no...> writes: Chris> Wonderful! this is great news. How have you done it? Have Chris> you written a DVI driver? or do you use TeX and associated Chris> tools to create a bitmap and put that on the image? Or Chris> something else? For *Agg, we use tex + dvipng and load the output as a transparent, anti-aliased raster, caching the dvipng output in ~/.tex.cache for efficiency. For PS, we use tex + dvips + psfrag + latex + a patched ps2epsi. The latter is cumbersome, but it works. In an ideal world, we would simply use tex + dvips but embedding the postscript fragments generated by dvips in arbitrary locations on the figure, but this has proved challenging. Having our own dvi parser would be a nice solution. As you noted, the format isn't too complicated, except for the font handling and the fact that you need your own bytecode processing engine to extract the information. We're waiting until Robert Kern has another boring experiment to site through for this one. JDH |