# pdf/a: Width information for rendered glyphs is inconsistent

Have there been any advances to create a valid pdf/a-1b from LaTeX including math fonts? I get the following error from preflight in Adobe Acrobat Pro: Width information for rendered glyphs is inconsistent for the document (TeXLive 2011 and pdflatex):

\documentclass{article}

\usepackage{MnSymbol}
%\usepackage{mdsymbol}
\usepackage[a-1b]{pdfx}

\begin{document}

$$\sum$$

\end{document}


For this to run, a sRGB profile is needed which can be downloaded here. Rename it to sRGBIEC1966-2.1.icm.

Next to fixable errors (eg no metadata supplied), I get the error for either MnSymbol or mdsymbol. Is there something to be done in the mf source code? Any other advice? Unfortunately, Acrobat cannot fix this issue.

-
I get the same error with \documentclass{standalone}\usepackage[a-1b]{pdfx}\begin{document}x\end{document‌​}. The PDF has a width entry of 527.8, fontforge (and the afm file) give a width of 527 - but I know almost nothing about fonts. –  topskip May 25 '12 at 20:54
XeTeX also inserts 527.8 but that gives no error. To reproduce the problem one can leave out the \usepackage command. –  topskip May 25 '12 at 21:25
@sebschub Maybe you should update your question, since Acrobat can fix this issue. –  maetra Dec 3 '12 at 8:19

I cannot provide an LaTeX-based answer, but I tried the new Acrobat Reader XI in order to get a fully valid pdf/a-1b document from your MWE. Et voilà, it worked well, the pdfwidth information for rendered glyphs was also fixed. One drawback though, in comparison with Acrobat Reader 9 the generated files seem to get larger.

-
Did you use the preflight tool or did you "print" into a new pdf? –  sebschub Nov 22 '12 at 12:42
@sebschub. I used the preflight tool directly as well which seems to do same as the save as option but not as the print option. The print option was unable to fully comply with pdf/a-1b standard do to some xmp-problem but fixed the width information as well. –  maetra Nov 22 '12 at 13:21

I'm sure you're no longer interested in the answer, but for future readers who happen upon this thread:

Can you avoid using the MnSymbol or mdsymbol packages? When I use the amsmath package instead, I have no problems. The appearance of the characters is slightly different, but I suspect that's not a problem for most applications. My code is:

\documentclass{article}

%\usepackage{MnSymbol}
%\usepackage{mdsymbol}
\usepackage{amsmath}
\usepackage[a-1b]{pdfx}

\begin{document}

$$\sum$$

\end{document}


It seems like the basic issue is that some of the characters in the two symbol packages you are trying to call (including \sum) have zero character width, which violates the ISO standards for PDF/A documents. The characters called by the amsmath package evidently don't have this property.

This problem is poorly documented, but I found these two sources which are obliquely related:

tug.org/pracjourn/2010-1/beccari/pdfatricks.tex

and the last section of

http://support.river-valley.com/wiki/index.php?title=Generating_PDF/A_compliant_PDFs_from_pdftex

-