<div dir="auto"><span style="font-family:sans-serif;font-size:13.696px">Here, I have created two repository, </span><a href="https://gist.github.com/harieamjari/d4c634ce2ddb2c6e6c666a3985de2909" style="text-decoration:none;color:rgb(66,133,244);font-family:sans-serif;font-size:13.696px">https://gist.<wbr>github.com/harieamjari/<wbr>d4c634ce2ddb2c6e6c666a3985de29<wbr>09</a><span style="font-family:sans-serif;font-size:13.696px"> and </span><a href="https://gist.github.com/harieamjari/c4aeac23ac0fecd8d938a7a03118b743" style="text-decoration:none;color:rgb(66,133,244);font-family:sans-serif;font-size:13.696px">https://gist.github.com/<wbr>harieamjari/<wbr>c4aeac23ac0fecd8d938a7a03118b7<wbr>43</a><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px">The former contans a pdfa compliant document while the latter contains a nonpdf/a compliant document.</div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px">Each of this repository can be compiled online with latexonline.cc. Here is the them respectively: </div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><a href="https://texlive2020.latexonline.cc/compile?git=https://gist.github.com/harieamjari/d4c634ce2ddb2c6e6c666a3985de2909.git&target=t.tex&command=pdflatex&force=true&download=outpdfa.pdf" style="text-decoration:none;color:rgb(66,133,244)">https://texlive2020.<wbr>latexonline.cc/compile?git=<wbr>https://gist.github.com/<wbr>harieamjari/<wbr>d4c634ce2ddb2c6e6c666a3985de29<wbr>09.git&target=t.tex&command=<wbr>pdflatex&force=true&download=<wbr>outpdfa.pdf</a> output contains pdfa compliant pdf.<br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><a href="https://texlive2020.latexonline.cc/compile?git=https://gist.github.com/harieamjari/c4aeac23ac0fecd8d938a7a03118b743.git&target=t.tex&command=pdflatex&force=true&download=outnonpdfa.pdf" style="text-decoration:none;color:rgb(66,133,244)">https://texlive2020.<wbr>latexonline.cc/compile?git=<wbr>https://gist.github.com/<wbr>harieamjari/<wbr>c4aeac23ac0fecd8d938a7a03118b7<wbr>43.git&target=t.tex&command=<wbr>pdflatex&force=true&download=<wbr>outnonpdfa.pdf</a> output contains non pdfa compliant pdf.<br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px">The result for outpdfa.pdf from <a href="http://verapdf.com/" style="text-decoration:none;color:rgb(66,133,244)">verapdf.com</a> is it passed the verification while the outnonpdfa.pdf has failed.</div><div dir="auto" style="font-family:sans-serif;font-size:13.696px"><br></div><div dir="auto" style="font-family:sans-serif;font-size:13.696px">You can verify yourself the pdfa.pdf and nonpdfa.pdf from each gist repository.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 19 Nov 2021 22:25, "suzuki toshiya" <<a href="mailto:mpsuzuki@hiroshima-u.ac.jp">mpsuzuki@hiroshima-u.ac.jp</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Harie,<br>
<br>
BTW, have you confirmed that if PDF/A document is embedded via includegraphics macro, the whole document becomes PDF/A?<br>
<br>
On 2021/11/19 23:15, suzuki toshiya wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FYI: I found that I received the off-list reply from Harie.<br>
<br>
-------- Forwarded Message --------<br>
Subject: Re: [cairo] Feature request: PDF/A compliant pdf?<br>
Resent-From: <a href="mailto:mpsuzuki@hiroshima-u.ac.jp" target="_blank">mpsuzuki@hiroshima-u.ac.jp</a><br>
Date: Fri, 19 Nov 2021 01:12:16 +0000<br>
From: Harie Amjari <<a href="mailto:healer.harie@gmail.com" target="_blank">healer.harie@gmail.com</a>><br>
To: suzuki toshiya <<a href="mailto:mpsuzuki@hiroshima-u.ac.jp" target="_blank">mpsuzuki@hiroshima-u.ac.jp</a>><br>
<br>
I'm using graphviz to produce pdf files which I incorporate my tex file with `\includegraphics{o.pdf}` along with `\usepackage[a-1b]{pdfx}` at the preamble of the tex file (and since graphviz uses cairo in the writing of the pdf, the whole document becomes non pdf/a compliant even though i've included `\usepackage[a-1b]{pdfx}`)<br>
<br>
On the other hand, if I don't include `\includegraphics{o.pdf}` then the whole document produced by latex becomes pdf/a compliant, but if I tries to include it, then my whole document becomes non pdf/a compliant.<br>
<br>
More <a href="https://gitlab.com/graphviz/graphviz/-/issues/2155" rel="noreferrer" target="_blank">https://gitlab.com/graphviz/gr<wbr>aphviz/-/issues/2155</a><br>
<br>
On 19 Nov 2021 08:50, "suzuki toshiya" <<a href="mailto:mpsuzuki@hiroshima-u.ac.jp" target="_blank">mpsuzuki@hiroshima-u.ac.jp</a><ma<wbr>ilto:<a href="mailto:mpsuzuki@hiroshima-u.ac.jp" target="_blank">mpsuzuki@hiroshima-u.ac.<wbr>jp</a>>> wrote:<br>
Dear Harie,<br>
<br>
I've seen the documentation at <a href="https://www.cairographics.org/manual/cairo-PDF-Surfaces.html" rel="noreferrer" target="_blank">https://www.cairographics.org/<wbr>manual/cairo-PDF-Surfaces.html</a> and so far it does not mention any support for compliant in PDF/A, other than the <a href="https://www.cairographics.org/manual/cairo-PDF-Surfaces.html#cairo-pdf-metadata-t" rel="noreferrer" target="_blank">https://www.cairographics.org/<wbr>manual/cairo-PDF-Surfaces.html<wbr>#cairo-pdf-metadata-t</a> which is required by the specification to be filled up, I believed. Is this feature possible? (to implement?)<br>
<br>
Please could you tell me the background why you (or somebody else) require PDF/A support in cairo?<br>
Are you developing some applications using cairo and want to emit PDF/A from your application?<br>
<br>
There are many applications using cairo, but I guess, if cairo adds a support for PDF/A, most applications would not add new switch to use new APIs...<br>
<br>
Possibly a function like `cairo_pdfa_*`?<br>
<br>
I don't think the introduction of new surface and the huge set of new API is the best way.<br>
If it would happen in future, the extension of the cairo_pdf_version_t enum would be mild solution.<br>
<br>
--<br>
<br>
Taking a glance on <a href="https://en.wikipedia.org/wiki/PDF/A#Description" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/<wbr>PDF/A#Description</a> ,<br>
it would not be so hard to ignore the prohibited contents (like JPEG2000 in PDF/A-1... oh, there's no prohibition for JBIG2 content?), but the problem would be that the metadata is classified as mandatory.<br>
<br>
If future cairo library requests as "please give me XMP metadata to be embedded in PDF/A - if not, I cannot emit PDF/A", the application programmers can pass some appropriate XMP as "ok, here it is"? I'm afraid they would complain "oh, I don't understand what I should do. My interest is only the passing of the validation by the PDF/A validator which I'm asked to use. cairo should create the XMP by itself, even if its content is filled by blahblahblah".<br>
<br>
Similar issues would happen for the requests of "Language specification", "Hierarchical document structure", "Tagged text spans and descriptive text for images and symbols". How do you think about these requirement?<br>
<br>
Regards,<br>
mpsuzuki<br>
<br>
On 2021/11/18 22:53, Harie Amjari wrote:<br>
I've seen the documentation at <a href="https://www.cairographics.org/manual/cairo-PDF-Surfaces.html" rel="noreferrer" target="_blank">https://www.cairographics.org/<wbr>manual/cairo-PDF-Surfaces.html</a> and so far it does not mention any support for compliant in PDF/A, other than the <a href="https://www.cairographics.org/manual/cairo-PDF-Surfaces.html#cairo-pdf-metadata-t" rel="noreferrer" target="_blank">https://www.cairographics.org/<wbr>manual/cairo-PDF-Surfaces.html<wbr>#cairo-pdf-metadata-t</a> which is required by the specification to be filled up, I believed. Is this feature possible? (to implement?)<br>
<br>
Possibly a function like `cairo_pdfa_*`?<br>
<br>
<br>
</blockquote>
</blockquote></div></div>