At 15:16 30/05/2008 -0700, Alan C. Baird wrote:
I created a screenplay template for MSWord 2002 and wrote a short
10-page script - the .doc file was 56Kb.
Then I created a screenplay template for OpenOffice.org Writer 2.4
and pasted the same text into it - the resulting .odt file was 17Kb. Great!
Afterwards, I created a PDF of the .doc file at
http://createpdf.adobe.com - using Adobe's default settings, the
.doc-PDF file was 17Kb. Finally, I created a PDF of the .odt file
with OOo Writer 2.4 - using the default Export settings, that
.odt-PDF file was 48Kb. Oof.
I'm not an expert in these matters, but here is an idea.
Word processor files generally do not include a definition of the
fonts they use. PDF files do. Unless you asked Microsoft Word to
embed the fonts, your .doc file would simply have named the fonts it
needed at different points; likewise, Writer's .odt file would not
contain any font definitions. When these document files are opened
on remote systems, the fonts used for displaying or printing them are
similarly named fonts present on that system, or appropriate fonts
determined by its font substitution table.
When you made PDF versions of these documents, (subsets of)
appropriate fonts would have been included in them. But the fonts
included in your first example would presumably have been provided by
the Adobe web site, whereas the fonts included in the second example
would have been imported by Writer from your own system. These would
in general be different fonts (albeit with the same names) and could
even be different types of font - perhaps of very different
sizes. Are the .doc and .odt documents otherwise identical, in
fact? Is it possible that you have a rogue character in another font
in your Writer version, requiring the PDF to contain another
font? (Remember that character attributes such as bold and italic
are actually indicators of alternative fonts.)
If you open your PDFs in Adobe Reader and go to File | Properties...
| Fonts, you can see what is embedded in each.
But others may well know better ...
I trust this helps.
Brian Barker
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
