Hot answers tagged

56

The preflight tool of PDFBox validates against the PDF/A-1b standard, more than just PDF. The first errors regarding PDF/A-1b should be resolved by a recent pdfTeX, I do not get these errors with pdfTeX 1.40.16 (TeX Live). The last error 7.1 about MetaData comes from the requirement of PDF/A-1b to also embed the meta data in XMP format, see package ...


29

Update: Since the original answer, the PDF api in luatex changed. In order to use this code you have to load luatex85 Put the color profile eciRGB_v2.icc in the working directory. Add the flowing code to your preamble: \usepackage{luatex85} \pdfminorversion 4 \immediate\pdfobj stream attr{/N 3} file{eciRGB_v2.icc} \pdfcatalog{% /OutputIntents [ << /...


20

Experience with the Accessibility Package I downloaded the accessibility.sty style file from Babette Schalitz's website. This file is available under an LPPL license. Using \usepackage[tagged]{accessibility} in my preamble allowed me you to generate a basic tagged PDF file that passes tests in Adobe Acrobat. However, the package didn't work if I needed to ...


17

This question has a lot of votes, but hasn't received an answer. So I am giving a ConTeXt solution. To create a tagged pdf, simply add: \setuptagging[state=start] at the top of your document. For example: \setuptagging[state=start] \starttext \startsection [title={A section title}] \input ward \stopsection \stoptext Then, pdfinfo test.pdf gives: ...


12

Generating PDFA-1b compatible PDFs is rather difficult with LaTeX. The details are described here: http://support.river-valley.com/wiki/index.php?title=Generating_PDF/A_compliant_PDFs_from_pdftex If it is just about the color profile, you may use the following piece of code: \pdfminorversion=4 \documentclass{minimal} \usepackage[rgb]{xcolor} \immediate\...


11

It seems the answer was hiding in a footnote of this paper on making ADA compliant PDFs. See this project! UPDATE: Having spent time attempting to use this tool in conjunction with a complex custom class, I want to temper expectations. While the accessibility.sty package is a useful tool for simple documents, it is incompatible with multiple packages and ...


10

Generating PDFA-1b compliant documents is not possible with the default pdftex. There is a minor bug in pdftex resulting in non-compliant EOL markers. There is a bug report from 2011 about this problem which successfully resolves the issue. You can find it here: http://sarovar.org/tracker/index.php?func=detail&aid=4341&group_id=106&atid=493 ...


9

As of January 2017 pdfx package improved a lot but still has some problemswith producing expected results. That's why i use some handcrafted solution for small list of options (this sample is also a test for differrent problems): % Úτƒ-8 encoded \RequirePackage{filecontents} \begin{filecontents*}{pdfaxcode.tex} \ifnumgreater{\value{pdftype}}{0}{% \...


9

Extract from pdfx documentation: "PDF/A and PDF/E usually need an RGB profile". You may force RGB colors using the rgb option when thexcolor package is loaded: \documentclass[margin=1pt]{standalone} \usepackage[rgb]{xcolor} \usepackage[a-1b]{pdfx} \usepackage{hyperref} \hypersetup{colorlinks=true} \begin{document} \url{http://jill-jenn.net} \end{document}


8

The tikz package loads the xcolor package which is partially responsible for the change in your url colors. This can be easily fixed by placing your \hypersetup{colorlinks=true} before the tikz package and the color will be defined as RGB magenta before the tikz package is loaded, resulting in the original color. Here is a MWE (note: i have the pdfx package ...


8

As to your second question: it is normal, that an RGB and an CMYK color does not look the same. To understand why, I have to tell some details. You have to know, that there are at least two different ways of "getting color" into your life. Lets have a closer look at your computer monitor. If you switch it off, it shows its "natural" color, which is kind ...


7

You need eciRGB_v2.icc in the working directory. \documentclass{article} % =============================== % Embedding the color profile. % Requires eciRGB_v2.icc in the working directory % http://www.eci.org/_media/downloads/icc_profiles_from_eci/ecirgbv20.zip \pdfminorversion 4 \immediate\pdfobj stream attr{/N 3} file{eciRGB_v2.icc} \pdfcatalog{% /...


7

Putting the correctly compiled executables to /usr/bin, everything works as expected. As I struggled quite a bit correctly compiling it, I think it will be useful to have an up-to-date guide to get pdftex from current sources. A big thank you to the helpful people at the tex live and tlbuild mailing lists. Here's the guide: How to build and install pdftex/...


7

You need to set the variable omitcidset to 1 (thanks to Hans Hagen ...): \documentclass{article} \usepackage{fontspec} \setmainfont{Georgia} \usepackage[a-3b]{pdfx} \pdfvariable omitcidset=1 \begin{document} Test \end{document} (probably pdfx should do it, so better inform the maintainer)


6

I had to validate a document through jhove, and I managed to do it using pdftk on the PDF that was produced by pdflatex. I simply used the command pdftk MyDocument.pdf output ValidatedDocument.pdf I hope it can help you!


6

Let pdfx load hyperref: \documentclass{article} \usepackage[a-1b]{pdfx} \begin{document} Foo Bar \end{document} Generally, hyperref should be loaded late - last excepting packages which specifically require it be loaded first.


5

With pdfx.sty (v1.5.8) the following order of packages works also, provided you change the \usepackage[..options..]{hyperref} into \hypersetup{..options..}. \documentclass[twoside,a4paper,DIV15,parskip=off,9pt]{scrbook} \usepackage[a-1b]{pdfx} % Fonts and typesetting settings \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \usepackage[ngerman]{babel} \...


5

I get no error if I load the packages in the correct order: \documentclass[twoside,a4paper,DIV15,parskip=off,9pt]{scrbook} % Fonts and typesetting settings \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \usepackage[ngerman]{babel} \usepackage[sc]{mathpazo} % For Palatino %\usepackage{mycals} % What's this???? \usepackage[ linktocpage=false, % ...


5

This answer presents what seems to me the most efficient way to improve the accessibility of LaTeX documents. Unfortunately, it requires the use of R and Adobe Acrobat. My previous approach involved using only a modified version of Babett Schaltz’s accessibility.sty. (Schaltz created it as part of her 2007 PhD thesis in Germany.) Despite making hundreds of ...


5

Using TeX Live 2014, pdfTeX 3.14159265-2.6-1.40.15, I don't seem to run into these problems. Maybe updating your TeX-system can solve the problems. Here is a modification of your MWE that embeds a color profile and metadata (I don't have access to Adobe's Preflight tool or other software that can do this in a post-processing step). Information on how to ...


4

I'm not sure if an answer is still of interest. Anyway: 1) I would strongly advise to use the pdfx package: \usepackage[a-1b]{pdfx} 2) The error in the pdfx package is caused by the way how the timestamp is put together. Depending on your timezone (e.g. UTC+1, UTC-1, etc) you have a different sign there. This causes the issue. Use of \getTZh doesn't ...


4

With some dirty patchcmd (from etoolbox) of hyperref commands. Seems to work with pdflatex and lualatex. icc file from pdfx package. \documentclass{article} \pdfminorversion 4 \pdfcompresslevel=0 \immediate\pdfobj stream attr{/N 4} file{coated_FOGRA39L_argl.icc} \pdfcatalog{% /OutputIntents [ << /Type /OutputIntent /S/GTS_PDFA1 /DestOutputProfile \the\...


4

The argument to \includexmp should be a file name (without the .xmp extension), modelled on the license.xmp file found in the package distribution: <x:xmpmeta xmlns:x='adobe:ns:meta/'> <rdf:RDF xmlns="http://web.resource.org/cc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> ...


4

This has been fixed in veraPDF V1.11.19, see https://github.com/veraPDF/veraPDF-library/issues/957. I confirm this has been an issue in PostScript font parser in the 1.10.6 release. It has been fixed in dev. Please check the latest dev version: http://software.verapdf.org/develop/1.11/verapdf-greenfield-1.11.19-installer.zip


4

You can force the output intent with : \RequirePackage{filecontents} \begin{filecontents*}{\jobname.xmpdata} \setCMYKcolorprofile{coated_FOGRA39L_argl.icc} {Coated FOGRA39} {FOGRA39 (ISO Coated v2 300\% (ECI))} {http://www.argyllcms.com/} \Title{Title} \Author{Author\sep} ...


4

Your example is using ghostscript with the -dPDFA option to create a pdf/A-1 compliant pdf. Your example is also using opacity. But transparent objects and layers are forbidden in PDF/A-1 and it looks as if ghostscript is doing a lot work to remove them. I couldn't check what exactly happens as even with small examples the uncompressed pdf is huge. This ...


3

You are mixing xmpincl and pdfx expectations about how the XMP file will be found and created. The command \includexmp is from xmpincl, and pdfx wants nothing to do with it. pdfx provides a simplified interface, but it has strict requirements: Your .xmpdata file must have the same name as the main .tex file (if using the filecontents package, then use \...


Only top voted, non community-wiki answers of a minimum length are eligible