Right here’s an intelligent concern. Taking it by the book, it is probably you’ll possibly possibly possibly launch off with this:

%PDF-1.0
1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj
xref
0 4
0000000000 65535 f
0000000010 00000 n
0000000053 00000 n
0000000102 00000 n
trailer<>
startxref
149
%EOF

which is 291 bytes of PDF joy. Acrobat opens it, but it complains barely. There is one online page in it and it is 3/72″ sq., the minimum allowed by the spec.

On the unreal hand, Acrobat X would not even bother with the murky reference table anymore, so we are able to have interaction that out:

%PDF-1.0
1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj
trailer<>

Acrobat complains, but opens it. Now we’re at 178 bytes.
Turns out that you just do not desire that /Size in the trailer. Now we’re at 172:

%PDF-1.0
1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj
trailer<>

Turns out you do not desire all those pesky /Form aspects on your dictionaries:

%PDF-1.0
1 0 obj<>endobj 2 0 obj<>endobj 3 0 obj<>endobj
trailer<>

Now we’re at 138 bytes.

It additionally appears to be like that when the spec says „shall be an indirect reference“ and /Depend is required, and the header „must“ be %PDF-1.0, they’re making free suggestions. Right here’s the smallest I’m able to also accumulate it and have it openable in Acrobat X:

%PDF-1.
trailer<>]>>>>>>

70 bytes.

Now, my editor makes exhaust of Dwelling windows newline discipline, but Acrobat accepts Dwelling windows, Mac, or Unix conventions, so by the exhaust of a hex editor, I replaced the rn with r and removed the closing newline altogether, which leaves me with 67 bytes

25 50 44 46 2D 31 2E 0D 74 72 61 69 6C 65 72 3C 
3C 2F 52 6F 6F 74 3C 3C 2F 50 61 67 65 73 3C 3C 
2F 4B 69 64 73 5B 3C 3C 2F 4D 65 64 69 61 42 6F 
78 5B 30 20 30 20 33 20 33 5D 3E 3E 5D 3E 3E 3E 
3E 3E 3E 

I tried taking off the closing stay dictionary (>>), but Acrobat achieve not have that. The PDF finding out built-in to Google Chrome (FoxIt) might possibly well possibly also not open it.

As a PostScript (HA! Ogle what I did there?), when you happen to consent to Acrobat „repairing“ the file, it bumps up to 3550 bytes, most of it not mandatory metadata, but it leaves in the merit of loads of lag spec violations.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.