#11
|
|||
|
|||
Vector PDF gets my vote
|
#12
|
|||
|
|||
I'm a huge proponent of SVG graphics for almost anything related to 3rd order Bezier curves. It's XML and represents the curve data in a readily interpreted open standard. PDF is a proprietary format.
However, SVG is not a publishing format. For greater printing accessibility the superior format is PDF, as that is its primary purpose. SVG on the other hand is a vector data format, not a document exchange format. An abstract example is that a multi-page document cannot be encapsulated by one SVG, rather it requires multiple files. Font embedding and other such publishing issues (in the case of instructions) also raise concerns. My workflow is CAD software for design, Inkscape for simplification of curves and texturing/coloring, Scribus for PDF output. Without some context as to what the printing difficulties were it's difficult to offer another input. However, scaling issues with SVG printing from the browser are hit or miss as well as they'll depend on how your SVG is constructed, and whether or not the print options of the printer/browser behave uniformly. |
#13
|
||||
|
||||
Quote:
You're obviously well into the more arcane aspects of computers which leaves us simple folk way behind. Whilst you need the facility to text read the actual code most others around here don't have that ability. Might I suggest that what is most useful for the majority on this forum is a .pdf file that will open in standard run of the mill windows and mac programs and without the potential problems mentioned above by psf. Printing areas were of course discussed at Hhrrrmph! Margins! and A4 and US Letter PDF Compatibility? but if you also actually draw an enclosing rectangle and label it with it's size in inches and millimeters (lots of us like mms) then physically checking the printed size of that rectangle will let folks know if they are looking at exactly what you intended even when they can't read text code. |
#14
|
|||
|
|||
Quote:
I agree, for the builder, PDF is easier to use (multipage support comes to mind) and probably more widely supported. But SVG would be a big bonus for customizers. You might offer SVG versions as a companion package. |
#15
|
|||
|
|||
Quote:
For example, most of my builds (distributed as a set of JPGs or unlocked PDF/PDO; in the latter case, I use a virtual printer to convert to PDF) have used this overflow:
Of course, I've not used 3D software for customization; in that case, PDO could be a better choice. And yes, if you only want to build, not tweak/tune]repaint, PDF is best. Uh, maybe not - AFAIK, SVG can't harbor viruses |
Google Adsense |
#16
|
|||
|
|||
Friends & Modelers,
I am an avid Linux user so SVG files are opened and display well (as far as I can tell) on my system, but having said that I must say that my open source system plays very well indeed with PDFs. I can create them with a number of free programs and GIMP or Krita allow me to load any page from a PDF to modify or rescale. Since I am currently working on a RR layout with an extensive town scene in N scale this comes in very handy, because most buildings, cars, RR cars, etc available on the 'net are in HO scale or other larger scales. Of course when working with a graphic in GIMP I use the native .xcf format, it is similar to the .psd format in that it supports layers, alpha channels etc. There is even a program called "PDF Chain" that allows me to load any number of smaller PDFs and save them as a single larger PDF. So the long and short of it is, Don't fear the PDF. Just my 2 cents, Formerly Styrene aka David |
#17
|
||||
|
||||
PDF.
That said, you will find LOTS of people who have no idea how to print anything, much less a PDF. Reading is necessary in most cases, reading instructions that is. (Grin)
__________________
--- Ken The advantage of simplifying origami are twofold. |
#18
|
|||
|
|||
Quote:
Please do package SVGs as a PDF. Anyone who wants access to the SVG can open the PDF in Inkscape (or tool of their preference) to get it, but most probably won't know what to do with an SVG file - whereas everyone and their sister has a PDF viewer/printer.
__________________
Current builds: Mirco Firefly Serenity 1:96, Saturn V 1:72 ADD victims: WM Columbia 1:100, AXM Atlas V 1:300, OBP Spruce Goose, Uhu02 X-Wing... and many others |
#19
|
|||
|
|||
Quote:
I concur that most PDO files seem blocky, but I guess that's related to the fact that Pepakura, being so inexpensive, considerably lowered the bar for aspiring publishers, therefore opening the gates for less-than-polished models. Other aspects suggesting that time and money committed are more a issue:
* the cheapest version of Pepakura limits the texture size to 1K x 1K, but I don't know about the poly count Quote:
But yes, certainly PDF caters to a wider audience. Last edited by cfuruti; 11-21-2016 at 05:53 PM. Reason: (attempt to) fix URLs |
#20
|
||||
|
||||
PDF for most people will be better, as others said (most people have some sort of PDF reader). If you want to allow easy edits of patterns, textures, etc. publish the SVG as well.
I don't know what's your pipeline like, but I have several separate svg files with patterns, instructions and such that I combine to one pdf at the end - it's more convenient to distribute. Few notes: * PDF is an open format for a long time as well - you can get the specification. If your PDF file is compressed (most are), you can convert it to text form and look inside as well (SVG is clearer tho IMHO). * I've seen printing issues both with PDF and with SVG, there's just no guarantee that any of them will work perfectly. cfuruti: while you're correct that locked PDF can not be imported by Inkscape, you can still convert them to unlocked if you know the password for viewing, and import afterwards. |
Google Adsense |
|
|