PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
Leonard,
It seems like PDF/A has a serious problem. PDF/A files won't be usable in any workflow requiring XRX or KDK commands. This eliminates PDF/A from most commercial B/W and color PDF workflows - specifically printing using drawer-pull commands on most any commercial printing device.
Ironically, Adobe controls the PDF specification - while its own OEMs are creating illegal BROKEN workflows around Adobe's RIPs - while at the same time Adobe's apologists criticize the workflow the OEMs customers are forced to employ to make the OEMs device generate revenue.
Someone on this list besides myself should be concerned that vendors using the equipment I reference are the ones who pay to buy the tools developers and standards makers create.
I am forced to conclude that the PDF/A standards committee is choosing a position that will ultimately be a disservice to PDF developers who sell to this market. Further, I think it's irresponsible to use this list, which should be open to all developer issues, as a bully pulpit to claim that only certain workflows are good, i.e., not BROKEN.
As I said before, I represent the interests of our customers here - folks who have spent $100K's to $1,000K's to buy and use this type of equipment. These folks want to use PDF because of the value and flexibility it brings to their workflows.
I am sad to see that they cannot be accommodated. Does anyone else share my opinion?
Todd
On Wednesday, June 25, 2003, at 03:44 PM, Leonard Rosenthol wrote:
PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
At 01:57 PM 6/25/2003 -0400, Todd Kueny wrote:Its seems by your definition that a PDF which prints correctly on one of these devices is BROKEN and a PDF which does not print but is acceptable within the context of the PDF Standard is not BROKEN.
ANY PDF that does not conform to the PDF Reference (for WHATEVER REASON), is by definition "broken". I don't care if it work in Acrobat, Xpdf, Ghostscript or Billy-Bob's RIP - it's still broken.
This is something that we are VERY concerned about on the PDF/A committee and are working hard to make sure that all the ambiguities of the PDF Ref are tightened down...
I suggest the more constructive approach of complaining to Adobe that the PDF standard is BROKEN because it doesn't support what is "standard practice" in the industry
Nope, standard practice is NOT the way to do standards! Standards need to stand on their own and then be implemented correctly by vendors. The mess that is HTML is a perfect example of this...
Leonard
----------------------------------------------------------------------- ----
Leonard Rosenthol <mailto:[EMAIL PROTECTED]>
Chief Technical Officer <http://www.pdfsages.com>
PDF Sages, Inc. 215-629-3700 (voice)
To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
