kicad:pdf_output_from_kicad_in_linux
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
kicad:pdf_output_from_kicad_in_linux [2013/06/29 03:50] – [Using SVG] mithat | kicad:pdf_output_from_kicad_in_linux [2013/06/30 05:33] – mithat | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Using SVG ===== | ===== 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 use an external tool to 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: |
* In Eeschema: //File > Plot > Plot SVG// | * In Eeschema: //File > Plot > Plot SVG// | ||
* In Pcbnew: //File > Print SVG// | * In Pcbnew: //File > Print SVG// | ||
- | However, converting these files to PDF isn' | + | However, converting these files to PDF isn' |
- | There are a few things you should note: | + | <WRAP center round important 60%> |
- | * //Running this script will destroy | + | **Running this script will destroy |
- | * The script relies on [[http:// | + | |
+ | 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' | ||
+ | </ | ||
+ | |||
+ | |||
+ | There are a few things more you should note: | ||
+ | * The script relies on [[http:// | ||
* The script relies on [[https:// | * The script relies on [[https:// | ||
kicad/pdf_output_from_kicad_in_linux.txt · Last modified: 2016/02/06 18:21 by mithat