On 02 Jul 2014, at 16:46, luigi scarso wrote:

On Wed, Jul 2, 2014 at 4:37 PM, Otared Kavian wrote: Dear List members,

Does anyone know how to create a PDF/A file (where A stands for Archive) in mkii? In a thesis project which has to be uploaded on an archiving site it is required that the fonts should be imbedded into the PDF file and be compatible with the PDF/A standard.

How can this be done without having access to a professional software from Adobe or other companies?

Many thanks in advance: OK ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

hm mkii ? with mkiv you can have pdf/a-1a http://www.ntg.nl/maps/41/08.pdf

Thanks Luigi for the hint to that paper. Unfortuantely the project has been done with mkii… that’s why I would like to know if it’s possible to produce a PDF/A compliant file with ConTeXt mkii. By the way, is there an easy way to check whether a PDF file is PDF/A compliant? Best regards: OK

Thanks Luigi! It turns out that with some slight modifications I could typeset the mentioned project with mkiv. Then after having added the following from your article: %% For PDF/A \setupbackend[ format={pdf/a-1a:2005}, profile={default_cmyk.icc, default_rgb.icc,default_gray.icc}, intent={% ISO coated v2 300\letterpercent\space (ECI)} ] %% Tagged PDF %% method=auto ==> default tags by Adobe \setupstructure[state=start,method=auto] I could get a PDF which looks fine: but now I have to make sure that it is PDF/A compliant. Right now I don’t hav etime to check this, but in any case you gave me good hope… Thanks! Best regards: OK On 02 Jul 2014, at 17:05, luigi scarso wrote:

On Wed, Jul 2, 2014 at 4:52 PM, Otared Kavian wrote:

Thanks Luigi for the hint to that paper. Unfortuantely the project has been done with mkii… that’s why I would like to know if it’s possible to produce a PDF/A compliant file with ConTeXt mkii. By the way, is there an easy way to check whether a PDF file is PDF/A compliant?

Best regards: OK afaik there is only and experimental extension of pdftex that used with latex can make pdf/a-1a (tagged pdf) -- but i'm not sure.

But pdf/a-1b are different (not tagged) so you can use ghostscript, even if it's not easy. Here an article by C: Beccari for xelatex http://www.guitex.org/home/images/ArsTeXnica/AT012/xelatex-pdfa.pdf

See also this for gs http://stackoverflow.com/questions/1659147/how-to-use-ghostscript-to-convert...

-- luigi ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Hi Luigi, I did a test with mkiv (see the tex file attached), and then tested the resulting pdf file on the site you mentioned, http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx Unfortunately it says that the PDF produced by mkiv is not conform: test-PDF-A-1b.pdf does not conform to PDF/A. Validating file "test-PDF-A-1b.pdf" for conformance level pdfa-1a Invalid content of XMP packet header attribute 'id': 'dtlnfbrryjnvabnrajbkrpyw'. dc:description :: Wrong value type. Expected type 'lang alt'. The XMP property 'pdfaid:conformance' has the invalid value 'B'. Required is 'A'. The key MarkInfo is required but missing. A device-specific color space (DeviceGray) without an appropriate output intent is used. The document does not conform to the requested standard. The document contains device-specific color spaces. The document's meta data is either missing or inconsistent or corrupt. The document doesn't provide appropriate logical structure information. Done. So, I don’t know how to solve the issue of creating a PDF/A. Thanks for any hint. Best regards: OK On 02 Jul 2014, at 17:35, luigi scarso wrote:

On Wed, Jul 2, 2014 at 5:18 PM, Otared Kavian wrote: Thanks Luigi!

It turns out that with some slight modifications I could typeset the mentioned project with mkiv. Then after having added the following from your article:

%% For PDF/A \setupbackend[ format={pdf/a-1a:2005}, profile={default_cmyk.icc, default_rgb.icc,default_gray.icc}, intent={% ISO coated v2 300\letterpercent\space (ECI)} ] %% Tagged PDF %% method=auto ==> default tags by Adobe \setupstructure[state=start,method=auto]

I could get a PDF which looks fine: but now I have to make sure that it is PDF/A compliant. Right now I don’t hav etime to check this, but in any case you gave me good hope… Thanks! The problem is the pdf/a validator ... it's better to use that one the counterpart . An important one is the preflight of acrobat professional. If it says that it's ok , then "it's hard to assert that it's not ok" . Also this one maybe can help: http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx but privacy can be an issue.

Imho, a school (or whatever educational structure) that require a pdf/a should also offer a service to validate a pdf, and a report if validation fails.

-- luigi ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

On Wed, Jul 2, 2014 at 10:54 PM, Otared Kavian wrote:

Hi Luigi,

I did a test with mkiv (see the tex file attached), and then tested the resulting pdf file on the site you mentioned,

http://www.pdf-tools.com/pdf/validate-pdfa-online.aspx

Unfortunately it says that the PDF produced by mkiv is not conform:

test-PDF-A-1b.pdf does not conform to PDF/A.

Validating file "test-PDF-A-1b.pdf" for conformance level pdfa-1a Invalid content of XMP packet header attribute 'id': 'dtlnfbrryjnvabnrajbkrpyw'. dc:description :: Wrong value type. Expected type 'lang alt'. The XMP property 'pdfaid:conformance' has the invalid value 'B'. Required is 'A'. The key MarkInfo is required but missing. A device-specific color space (DeviceGray) without an appropriate output intent is used. The document does not conform to the requested standard. The document contains device-specific color spaces. The document's meta data is either missing or inconsistent or corrupt. The document doesn't provide appropriate logical structure information. Done.

So, I don’t know how to solve the issue of creating a PDF/A.

Thanks for any hint. Best regards: OK

This pass acrobat xi preflight for pdf/a-1b Note that the icc files default_cmyk.icc default_gray.icc default_rgb.icc ISOcoated_v2_300_eci.icc must be in tex/texmf-context/colors/icc/profiles and must match with the colorprofiles.xml in tex/texmf-context/colors/icc/context

\setupinteraction [title=TITLE, subtitle=SUBTITLE, author=AUTHOR, keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}] %% For PDF/A \setupbackend[ format={pdf/a-1b:2005}, profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}, intent=ISO coated v2 300\letterpercent\space (ECI)] \starttext \chapter[chap:testing]{Testing} \input knuth \input tufte \input knuth \input tufte \input knuth \input tufte \stoptext This pass pdf/a-1a \setupinteraction [title=TITLE, subtitle=SUBTITLE, author=AUTHOR, keyword={{KEYWORD1, KEYWORD2}, KEYWORD3}] %% For PDF/A \setupbackend[ format={pdf/a-1a:2005}, profile={default_cmyk.icc,default_rgb.icc,default_gray.icc}, intent=ISO coated v2 300\letterpercent\space (ECI)] %% Tagged PDF %% method=auto ==> default tags by Adobe %% \setupbackend[export=yes] it's necessary now to activate the tags %% probably it could be optional \setupbackend[export=yes] \setupstructure[state=start,method=auto] \starttext \startchapter[title=Testing chapter] \input knuth \startsection[title=Testing section] \bTABLE \bTR\bTD 1 \eTD \bTD 2 \eTD \eTR \bTR \bTD[nx=2] 3 \eTD\eTR \eTABLE \stopsection \stopchapter \stoptext

-- luigi