![]() ![]() So far I have only had success with exporting to PDF from VectorWorks and importing that in Inkscape. VectorWorks is a CAD program much like AutoCAD, used more in the Architecture and Entertainment Production industries. I’d report the problem (again, again, and yet again) to AutoCAD.I am trying to figure out the best way to get vector based drawings from VectorWorks into Inkscape with as little mangling as possible. My fix was to manually increase the width of all those offending lines to 0.5pt instead of 0pt. And for the last 29 years I have been at Adobe, this problem has continually come up with AutoCAD files although we have continually advised them not to use these constructs. Everything goes through a driver and there may be some enhancements there for zero width lines.įor the record, Adobe has always strongly discouraged use of 0 setlinewidth in PostScript and the equivalent 0 w in PDF exactly due to the problems you are seeing in this file. ![]() In addition, they don’t passthrough PostScript. Why would other PDF applications be able to print those lines in your original file? What I believe is happening is that they are artificially “bulking up” the lines to something they believe is more visible. ![]() What happens for non-PostScript printers? I honestly don’t know, but there is a good chance that other PDL drivers would either simply ignore zero width lines or possibly “bulk them up” to something more visible. My Xerox Phaser 7500 printer, showed the lines but exceptionally faintly. For PostScript printing, Acrobat actually passes through the 0 w width descriptions in PDF to 0 setlinewidth in PostScript (I validated it manually!) and passes that through to the printer. What happens when printing is printer driver and printer-dependent. ![]() Acrobat and Reader do their best to render the output. That is interpreted by both PostScript and PDF as a single pixel in width for the renderer. They are defined by AutoCAD as zero width lines. There is a reason for the disappearing lines. I received the problematic file privately from mike podlabeniouk and examined it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |