To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=63199





------- Additional comments from [EMAIL PROTECTED] Sun Mar 19 11:43:18 -0800 
2006 -------
->pl. Attached is the patch to clean up a little the PDF file.
The PDF 1.4 spec ( ch 3.1.1 ) says that the use of white spaces for indentation
in the examples is not recommended, the eol used there is a recommended
convention (not mandatory !), elsewhere the character '/' is explained to be a
token separator. The only place where a eol is mandatory, is the xref table.
>From al this I made an aggressive cleaning, joining togheter lines, using '/'
instead of spaces to separate tokes except where the separation was meant to be
a 'whitespace character' as they call it (e.g. between string and numbers), I
left eol in place where I wasn't sure of the changing.

Of course I didn't change 'obj', 'stream', 'endstream' 'endobj' tokens, in this
case I only changed the eol to a single LF char.

Let me know is you thing this a too aggressive approach and I will revert back
to a less aggressive one, e.g. leaving the recommended convention for arranging
token into lines (not used by gs though).

The gain figures depend from the file, they range from 1% to 3% for the untagged
version, and from 5% to 12% for the tagged ones.

The '<<' and '>>' tokens can still be optimized, from the specs it's unclear,
but gs optimizes '<<' (e.g. emits: /Resources<</ProcSet[/PDF /ImageC /ImageI
/Text] ), but not '>>'; let me know what you think.

I sent to your e-mail a tagged version to test.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to