The program that I use as an editor for vector based images is able to export using the following standards:
- Postscript 2 and 3 ( .ps )
- PSTricks macro written in Latex ( .tex )
- Eps ( .eps )
- SVG ( .svg )
Now after using latex for some time I can't really say which one is better for a latex based workflow, but I have been able to write down some requirements, I need support for :
- static images only ( no need for animations at this point, also my final goal is always a pdf anyway )
- inclusion from external file ( I often use relative paths to organize everything in their own directories )
- usable in styles
.styfiles - lightweight and easy to render in the final pdf ( sometimes
latexcreates some really hard-to-render images ) - easy to avoid aliasing / not prone to poor rendering
- text as path or text as text ( be able to incorporate the text from the image as "normal" text or viceversa )
- a format that copes well with layouts properties like margins, the center of each element, scaling, etc etc .
Since I'm not new to the imaging world and to the graphics world in general, I see Postscript as the old ancestor of pretty much anything that fits in a pipeline for the production of documents and vector images, I don't wanna sound like I have a biased opinion but probably PS works better for pdf production ? I don't know, I'm just thinking out loud. Anyway I'm more interested in the points I gave, especially the quality of the final product is everything to me.
As a special note I would like to know if latex uses an internal representation of a given vector image and what language is used for that.
pdflatexdirectly). – Jake Feb 13 '14 at 13:46pdflatexdirectly too, I noticed that is somehow better to first compile the.texwithlatex. – user2485710 Feb 13 '14 at 13:50pdflatexvslatex)? – Jake Feb 13 '14 at 13:59