|
From: | Faheem Mitha |
Subject: | Re: [AUCTeX] dvipng is not called by auctex |
Date: | Thu, 4 Jul 2013 13:25:28 +0530 (IST) |
User-agent: | Alpine 2.00 (DEB 1167 2008-08-23) |
On Thu, 4 Jul 2013, David Kastrup wrote:
Faheem Mitha <address@hidden> writes:
Looking at the compilation output, I see that the creation of the preview png snippets seems to be done by ghostscript. It looks like a pdf file is first created by TeX and then pdf2dsc is used to create a dsc file from that pdf.
The dsc file is not doing much: basically it fakes a PostScript page directory for the PDF file that then can be processed as if it had been PostScript to start with.
I see.
I'm not clear what gs uses to create the final png.
Its png16m backend.
Ok.
In any case, in terms of speed, is this the best possible option?
Nowadays, it's conceivable that pdftocairo might be faster, but it would not seem possible to do the kind of demand-based rendering that the Ghostscript interactive interface does, not with a single process. If you are daring, you might want to try writing a backend for that. At the time preview-latex was actively developed, there was no reasonable PDF->png converter available apart from Ghostscript.
I see. The current preview setup is fine. Thanks very much for the explanation, and for preview-latex.
Regards, Faheem
[Prev in Thread] | Current Thread | [Next in Thread] |