That is practically impossible. When conceived by John Warnock in the late 198s and defined in the now-famous Camelot whitepaper in 199 the future PDF format was intended to serve a genuine business need that had no immediate answer at the time. That of having a self-contained cross-platform digital printout that wouldbine visual information from arbitrary sources and render onscreen and print identically anywhere on any system without relying on external resources s The concept the format and the apanying Acrobat app sparked a lot of interest but once Adobe made Acrobat Reader a free download and enabled viewing in browser (defining the concept of a browser extension jointly with Netscape along the way) it really took to the sky. Since then PDF as a format grew to support a multitude of featuresments and annotations; accessibility features; content protection encryption and access security; forms and data collection; professional printing features; interactivity multimedia 3D support file attachments robust metadata etc. When Adobe donated PDF do ISO s in 28 it opened new horizons for the format adoption. I remember estimates from circa 213 that there were over 2 bln PDF in freely indexable resources around Internet with up to twice that amount in various corporate repositories. Since then PDF even had to branch out into a family of several related standards for document archival ( PDF s ) engineering ( PDF s ) professional printing ( PDF s ) variable data printing ( PDF s ) and accessibility ( PDF s ) all of them feature-based subsets of functionality from the parent PDF specification. Which in itself is under active development s having just released a major new version 2.. PDF is even listed by Wikipedia as an example of a de-facto standard s ) As a technical product PDF is on masterpiece level. Tasked from the outset to be future-proof it is AFAIC the only document format to boast forwardpatibility. Just think about it you create a PDF document today then find a way to transfer it on a 25yoputer with a copy of Acrobat Reader and it opens and shows! No wonder PDF was chosen as a substrate for the ISO document archival standard to make sure a digital document archived today opens in 1 years. So back to your question. What is it that you feel can be improved enough for tasks and features above to throw PDF off its throne? Is that original business need not yet sufficiently addressed? You serously want to beat all of that listed? I really don see thating. There were several attempts of which Microsoft most recent XPS challenge s es to mind. Does XPS even ring a bell now? However at the time it seemed threatening considering Microsoft resource then apany roughly 1 times the size of Adobe. In reality the market just doesn need another format for the task PDF is coping just fine. There are areas of improvement to address of course PDF very nature of keeping the layout intact is less of an advantage in the mobile era. There are screen reflow technologies but they need to be more mature and widespread. While PDF can support anypression method there are more efficient alternatives for raster-only (scanned) content using the various flavours of MRC (think DjVu). Yet this ispletely at software vendors discretion and some implementations s are very solid already (not so great in Adobe own Acrobat product unfortunately). Anyway there may be new imagepression algorithms on the horizon and PDF is well set to support any of them without even any changes to the specification.
How was the PDF format created?
I was there for the whole thing. It was the 9's and Adobe was doing well. In addition to the Systems department which handled the Postscript business there was an Applications group which had Photoshop and Illustrator. John Warnock had the idea that every document that was ever printed or ever would be printed could be represented in a document. This was not an unreasonable idea since Postscript was designed for this purpose and Adobe also had some code from Illustrator that would handle the fonts and graphics and code from Photoshop to display s - this would be the second file format for the project. However there were requirements that were not being met. Requirements like forward and backwardspatibility streaming large documents through a printer driver where the printer driver has no idea how many pages there will be and opening a 1 page document and being able to jump directly to the 5th page without reading the whole file. Peter Hibberd had written a demo of an 'object oriented file format' so Richard Cohn and Alan Wootton went to work trying to adapt his work for use on the Carousel project. After many weeks of struggle it was decided that adapting his work was going to be more work than writing new code and that some of the 'object oriented' concepts were not applicable since it was finally bing obvious that a key-value format was going to be part of the solution. This was the third file format. Bob Wulff the manager of the project told Richard and Alan to 'go away' and to note back until there was a file format! The next Monday Richard and Alan started meeting at Richard's house in Menlo Park instead of going to work in Mountain View (where Google is now). By the end of Thursday Richard and Alan had described data structures and concepts for a file format on many pieces of paper. Alan went home pulled 4 overnights in a row and came back to Adobe on Monday with the fourth file format written and working in the current code. This file format became known as PDF.
What are some tips for an aspiring game developer?