Differences

This shows you the differences between two versions of the page.

--- kicad:pdf_output_from_kicad_in_linux [2013/06/26 02:29] – [Using SVG] mithat
+++ kicad:pdf_output_from_kicad_in_linux [2016/02/06 18:21] (current) – [Using SVG] mithat
@@ Line 3: / Line 3: @@
 ===== Using SVG =====
-The most reliable way I've found to get good PDFs from KiCad under Linux is to first plot to SVG and then convert the SVGs to PDF. Plotting to SVG isn't difficult:
+The most reliable way I've found to get good PDFs from KiCad under Linux is to first plot to SVG and then use an external tool to convert the SVGs to PDF. Plotting to SVG in KiCad isn't difficult:
-  * Eeschema: //File > Plot > Plot SVG//
+  * In Eeschema: //File > Plot > Plot SVG//
-  * Pcbnew: //File > Print SVG//
+  * In Pcbnew: //File > Print SVG//
-However, converting these files to PDF isn't nearly as straight-forward. I use **[[svg2pdf-d|this script]]** to automate the conversion process. I just drop a copy of the script into my project directory and run it whenever I want to convert files. There are a few things you should note:
+However, converting these files to PDF isn't quite as straight-forward. I wrote the script **[[svg2pdf-d]]** to automate the conversion process. Just drop a copy of the script into a KiCad project directory and then run it whenever you want to convert files.
-  * Running this script will destroy any *.svg files in the working directory! That’s by design. I want to minimize the number of files that might be out of sync with the source, and keeping both SVGs and PDFs is just asking for trouble!
-  * The script relies on [[http://inkscape.org/|Inkscape]]---which it runs in batch/shell mode. Inkscape isn't really that light, but it’s arguably something that should be in your FOSS toolkit anyway.
+<WRAP center round important 90%>
+**Running this script will delete all *.svg files in the working directory!**
+This is by design. I want to minimize the number of files that might be out of sync with the source, and keeping both SVGs and PDFs is just asking for trouble!
+Put any SVG artwork you need to keep in a subdirectory or edit the script so it doesn't delete *.svg files.
+</WRAP>
+There are a few things more you should note:
+  * The script relies on [[http://inkscape.org/|Inkscape]], which it runs in batch/shell mode. Inkscape isn't really that light, but it’s arguably something that should be in your FOSS toolkit anyway.
   * The script relies on [[https://help.gnome.org/users/zenity/stable/|Zentiy]]. If this offends your KDE or other sensibilities, I have a [[svg2pdf-dgxmessage|version]] that uses [[http://homepages.ihug.co.nz/~trmusson/programs.html#gxmessage|gxmessage]] or [[http://linux.die.net/man/1/xmessage|xmessage]] as well as a pure [[svg2pdf-dbash|command-line version]]. I won't promise to keep these updated though.
 ===== Using PostScript =====
-Another alternative is to use PostScript as an intermediate format. [[ps2pdf-d|Here]] is a script that uses Ghostscript's [[http://ghostscript.com/doc/current/Ps2pdf.htm|ps2pdf]] for conversion. I prefer the SVG approach above because:
+Another alternative is to use PostScript as an intermediate format. [[ps2pdf-d|Here]] is a (much shorter) script that uses Ghostscript's [[http://ghostscript.com/doc/current/Ps2pdf.htm|ps2pdf]] for conversion. I prefer the SVG approach above because:
-  * The color mapping (at least from Eeschema) is truer.
+  * The color mapping from SVGs (at least from Eeschema) is truer.
   * Pcbnew gives you much more control over what you can plot to SVG compared to PostScript. In particular, you can't plot composite layers to PostScript.
-  * Page-sizing is automatic (I think).
+  * Correct page-sizing with SVG conversion is automatic (I think).
 I include the PostScript version here because there might be some limitations with SVGs that I've yet to discover.