Intro to PDF - Leonard Rosenthol

From PDF file structure to the Carousel Object System to common data structures and more, Adobe’s PDF Architect introduces the technical infrastructure of the world’s chosen final-form electronic document format.

[@sent4dc]

33:56 this is where PDF internals start. The rest of the fluff is not very important.

[@pythongabi]

thanks, saved me a meaningful amount of time hahah

[@valerijgrayfield1313]

Thank you

[@elvinsamuel3932]

👑

[@Rozenkrantzz]

You rock. Thank you

[@wisama11]

Hey, I created the pdf file from notepad using structure and code from the presentation. The Dimensions and the Font was available in the properties(those came out right) But the Hello World string was not seen. I have double checked the spaces too. Thanks

[@gabrielcarrillo5681]

I know this is **way** too late, but I did it just like it shows and it worked perfectly. There's some things that are really easy to miss, though, like the lack of spaces between /Basefont and /Helvetica in object 4 and the double spaces near the end. Here's the code for anyone interested: %PDF-1.4 6 0 obj > endobj 1 0 obj > endobj 4 0 obj > endobj 2 0 obj > stream BT /F1 24 Tf 1 0 0 1 260 600 Tm (Hello World)Tj ET endstream endobj 5 0 obj > endobj 3 0 obj > endobj xref 0 7 0000000000 65535 f 0000000060 00000 n 0000000228 00000 n 0000000424 00000 n 0000000145 00000 n 0000000333 00000 n 0000000009 00000 n trailer > startxref 488 %%EOF

[@tobiasthrien1]

@@gabrielcarrillo5681 I know this is *way* *way* too late but I got exactly the same. However the byte offsets are actually wrong. Somewhere in obj 1 there is one byte missing (or can't be seen; maybe an extra space). If you count the bytes you'll see that obj 4 (following obj 1) starts at byte 144 not 145. Of course all other byte positions shift by one as well. Then somewhere in obj 2 again one byte is missing which then makes obj 5 start at 331 not 333. My PDF reader still managed to display the document but also warned me. That's how I know. I corrected the xref to: 0000000000 65535 f 0000000060 00000 n 0000000227 00000 n 0000000422 00000 n 0000000144 00000 n 0000000331 00000 n 0000000009 00000 n and the xref itself then starts at 486. Therefore: startxref 486

[@SailasRick-mj5yr]

Too impressive

[@thomai5287]

"Artificial intelligence cannot read legal documents, yet. Probably never". That aged not so well :) But great talk. Thank you!

[@greencoder1594]

[21:11] «Launch a URI, ...play movies, ...There's a full programming language embedded into PDF» From a security perspective, PDF now reminds me of Adobe Flashplayer.

[@valerijgrayfield1313]

I think for the world as a whole, it would be better if PDF would be replaced with HTML. It would be easier for the Web to implement features that PDF is used for than for PDF to reach the security level of the Web, even if PDF already relies on some of those security features that the Web enabled for it. Clearly, choosing JS as the PDF's internal language is motivated by the fact that the Web uses it and thus it is much more tested. Well, the same goes for every other feature.

[@MorisonMs]

Just me or he sounds like Joaquin Phoenix