View Single Post
Old 01-22-2008, 06:24 PM   #83
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by kovidgoyal View Post
No my post stated that tagging a PDF document essentially creates two versions of the document

1) The untagged version. This is a "rendered" layout and will not reflow
2) The tagged version. This is a reflowable layout, but as a reflowable layout, it is inferior to dedicated reflowable layouts like HTML+CSS

You might as well think of a tagged PDF as a container for two versions of the document.
I do not think about it like that at all. I think of it as one document, which is what it is, with added metadata that is ignored when it is rendered on a page by page data but used when it is reflowed. The metadata includes enough information to provide the CSS data but better. It is tagged with the paragraph style and overrides for each paragraph in the document. This metadata allows a smart program to determine the best way to render that paragraph to communicate the information on the target output device.

There are certainly not two copies of the document in a container or it would be much bigger.

Dale
DaleDe is offline   Reply With Quote