Closed GoogleCodeExporter closed 9 years ago
Editing R18 (sparkfun trimpot 3296) tells me that this part has "separate
copper0 and copper1 layers" which I think is a bug.
I have not yet understood where the official parts are saved, but one should
try to edit 3296_*_pcb.svg.
Original comment by david.pe...@gmail.com
on 1 Feb 2014 at 1:08
if i open the svg-from 3296 there is really much inkscape crap. i edited the
file in AI and clean all the crap. the copper fill now works correct.
(but it destroys the size of the part because of 96dpi-inkscape and
72dpi-illustrator)
i give it another try, and the failure not comes up because of the "separate
copper0 and copper1". my guess: there are really much gorn, matrix and
translate properties in many groups, and this is what confuses when it makes
the copper fill. attached my illustrator file, ... svg code is more clean and
the copper-fill gets the right keepout. but the footprint is now too big
because of the conversion AI every time does.
try to cleanup the svg-code. sorry i never used inkscape...
Original comment by bluearc....@gmail.com
on 5 Feb 2014 at 4:39
Attachments:
Original comment by bluearc....@gmail.com
on 5 Feb 2014 at 4:53
"is really much inkscape crap"
There probably does need to be some work done sometime to make Fritzing more
tolerant of Inkscape svg, the main problems are in font-sizing (inkscape uses
style attributes, rather than individual attributes, it's a simple matter of
translating the styles), and obviously something here to do with translations.
Inkscape is the software that most people who make parts are going to be using,
AI is not open source, nor freely available, which is sort of opposed to
Frtizing's ideals a bit really I think :-)
Original comment by bitsybof...@gmail.com
on 5 Feb 2014 at 11:43
... +1 for you ;)
Original comment by bluearc....@gmail.com
on 6 Feb 2014 at 8:22
Issue has moved to new issue tracker at github. Please continue the discussion
at https://github.com/fritzing/fritzing-app/issues
Original comment by andre.knoerig@gmail.com
on 23 Sep 2014 at 3:44
Original issue reported on code.google.com by
bitsybof...@gmail.com
on 1 Feb 2014 at 10:44Attachments: