On 07/01/12 12:06, Per Nielsen wrote: > I recently discovered Veusz and was quite happy as it seemed to solve > many of my plotting frustrations. However, then I realized the lack of > latex support, which for me is essential.
Do you need complete latex support or is it just particular features? > Then I tried using Veusz in conjunction with psfrag to enable latex > support, which did not work. After trying psfrag with matplotlib for > Python, which to my surprise did not work either, and some googling I > found the following post: > > http://www.mail-archive.com/[email protected]/msg19767.html > > Apparently psfrag searches for some specific string format for its latex > replacement, which a recent version of matplotlib has changed, breaking > psfrag support in matplotlib. > > Might this issue be the same for Veusz? If so, are there plans to fix it > or is there perhaps some workaround? Unfortunately it's Qt which produces the postscript output from drawing commands sent by Veusz. It doesn't seem to put the text strings directly into the postscript output but encodes them. I can't think of an obvious easy fix. What could be done is: 1. Write our own EPS output driver, like I've done for SVG. This would work, but I don't know how to get fonts to embed as postscript fonts. It might be some work too! 2. Write SVG output using the current development version and convert to EPS using inkscape. The development version has an option to export text as text in the SVG file (not curves). I think inkscape might be able to write psfrag compatible postscript. 3. Maybe translate what Qt is writing into the EPS file back into text. Jeremy _______________________________________________ Veusz-discuss mailing list [email protected] https://mail.gna.org/listinfo/veusz-discuss
