I wrote a report with LaTeX, and afterwards discovered it must be PDF/A-compliant - which wasn't. I found the pdfx LaTeX package and followed its
instructions, thus obtaining a file that should be PDF/A and pdfinfo identifies
as such, but my employer's upload form thinks isn't [...]
Thanks for any help.
On Wed, Jul 03, 2024 at 01:06:56PM +0000, Ceppo wrote:
I wrote a report with LaTeX, and afterwards discovered it must be PDF/A-compliant - which wasn't. I found the pdfx LaTeX package and followed its
instructions, thus obtaining a file that should be PDF/A and pdfinfo identifies
as such, but my employer's upload form thinks isn't [...]
Uh-oh. We set the standards, but won't tell you what they are.
Thanks for any help.
Not concrete help, but the Wikipedia [1] makes for an interesting
read (including refs to bunches of test suites you can throw at your publisher's site to find out where their validator is failing).
And there seems to be a kind of semi-official validaror, according
to the above ref.
Cheers
[1] https://en.wikipedia.org/wiki/PDF/A
--
t
I wrote a report with LaTeX, and afterwards discovered it must be PDF/A-compliant - which wasn't. I found the pdfx LaTeX package and followed its
instructions, thus obtaining a file that should be PDF/A and pdfinfo identifies
as such, but my employer's upload form thinks isn't. Is pdfinfo reliable enough
that I can tell my employer his form is broken? If not, how can I make sure that pdflatex's output is actually PDF/A-compliant?
I will also probably have to upload under the same requirement some third-party
PDF, which is not PDF/A, without access to an editable version. Is there a way
to convert them to PDF/A? I know that converting from an editable version would
be the correct way for this, but I have no real way to get it.
A requirement of any solution is that it doesn't rely on non-DFSG-compliant software, including online conversion tools.
Thanks for any help.
On Wed, Jul 03, 2024 at 03:36:17PM +0200, tomas@tuxteam.de wrote:
Uh-oh. We set the standards, but won't tell you what they are.
But they did! They say PDF/A. But you have a point that this maybe is
not enough. Which version of PDF/A are we talking about?
On Wed, 2024-07-03 at 18:38 +0200, Richard wrote:
For anything further, you'll have to research yourself as ghostscript
is very complex but used by many people.
Please stop using such a dinky font.
For anything further, you'll have to research yourself as ghostscript
is very complex but used by many people.
Please stop using such a dinky font. There are plenty of old farts trying to read this list.
Tell that to your mail program. If it chooses to show you the mail that
way, don't blame me. Everything needed to display it any way you want is there, it just needs to be used. Thunderbird can define a minimum text size and refuse messages to use their own font. If your archaic software doesn't do basics, blame the dev - or better yet yourself, as the choice is yours.
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">
pdfinfo probably only reads metadata, but does not do any PDF/A compliance validation.
VeraPDF seems to work for validation (https://verapdf.org/software/).
Well, that is my way:
latex .../Nix.tex .../Nix.dvi^^^^^^^
dvips -o Nix.ps Nix.pdf
ps2pdf ... Nix.ps ... Nix.pdf
chmod 755 script
All works since many many years absolutly perfect, nothing else ever was is needed
From LaTeX, this is quite simple, there's a package for that - as for pretty much everything in the LaTeX world. Googling for just like 10 sec could have given you this great guide: https://webpages.tuni.fi/latex/pdfa-guide.pdf
gs -dQUIET -dUseCIEColor -sProcessColorModel=DeviceCMYK -sDEVICE=pdfwrite -dPDFACompatibilityPolicy=1 -dCompressFonts=true -dSubsetFonts=true -sFONTPATH=/usr/share/fonts/ -o <file name of output> <file name of input>
On Wed, Jul 03, 2024 at 01:06:56PM +0000, Ceppo wrote:
I wrote a report with LaTeX, and afterwards discovered it must be PDF/A-compliant - which wasn't. I found the pdfx LaTeX package and followed its instructions, thus obtaining a file that should be PDF/A and pdfinfo identifies as such, but my employer's upload form thinks isn't [...]
Uh-oh. We set the standards, but won't tell you what they are.
Not concrete help, but the Wikipedia [1] makes for an interesting
read (including refs to bunches of test suites you can throw at your publisher's site to find out where their validator is failing).
And there seems to be a kind of semi-official validaror, according
to the above ref.
On Wed, Jul 03, 2024 at 01:06:56PM +0000, Ceppo wrote:
A requirement of any solution is that it doesn't rely on non-DFSG-compliant software, including online conversion tools.
Please looks at this thread at StackExchange. I found that to be very helpful. https://tex.stackexchange.com/questions/130201/pdf-a-with-hyperref-on-tex-live-2013/136653#136653
Please let me know how it works out for you.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 151:07:24 |
| Calls: | 10,383 |
| Files: | 14,054 |
| Messages: | 6,417,797 |