Thank you. I see what I can do...
Best regards Toël Hartmann On 7 aug 2013, at 22:06, Leleu Eric <[email protected]> wrote: > Hi, > > Currently the only way to check an other format than PDF/A is to replace > ValidationProcess in the PreflightConfiguration. To do this, you have to > extend the PreflightDocument to access the config attribute in order to > call replaceXXX method on the configuration object. > > Each instance of ValidationProcess class is called in the validate method > of the PreflightDocument. > > > > BR, > Eric > > > 2013/8/6 Hartmann Toël <[email protected]> > >> Hi, >> >> I am interested in helping adding support for such a validator, but will >> need guidance on where to start. >> The predefined constants in PreflightConstants does not seem to be used, >> and the enum in Format looks to only be referred to in FilterHelper but the >> code seems to do the same thing anyway. >> >> What would be the preferred strategy for adding such validation support? >> >> >> On 6 aug 2013, at 12:06, Maruan Sahyoun <[email protected]> wrote: >> >>> Hi, >>> >>> it's technically possible to add checks for PDF/X compliance but at that >> point in time I don't think that someone is working on it. For an immediate >> solution you should use the PDF/A validation output. >>> >>> Of course, if you are willing to add support for a validator … >>> >>> BR >>> Maruan Sahyoun >>> >>> Am 06.08.2013 um 10:26 schrieb Hartmann Toël <[email protected] >>> : >>> >>>> Hi, >>>> >>>> I would like to check pdf for PDF/X-1a:2003 compliance. >>>> >>>> Would it be possible to add support for PDF/X specific checks in PDFBOX >> or should I analyze the XML output from PDF/A? >>>> >>>> >>>> >>>> Best regards >>>> Toël Hartmann >>> >> >>
