On Mon, 2003-12-01 at 02:45, Glen Mazza wrote:
--- John Austin [EMAIL PROTECTED] wrote:
The property strings are given to the Property
object
constructor by some path beginning with a SAX
parser.
It is reasonable to assume that the SAX parser loses
refs to most of these strings and
Input: The XSL-FO file produced from:
DocBook: The Definitive Guide
Document size: 648 Pages // for the O'Reilly edition
FO file size: 21,659,370 bytes
Properties: 526,648
Tags: 285,223
Height of tree: 17 // max height of the parse tree
Unique
--- John Austin [EMAIL PROTECTED] wrote:
The property strings are given to the Property
object
constructor by some path beginning with a SAX
parser.
It is reasonable to assume that the SAX parser loses
refs to most of these strings and that the Property
implementation retains the only
In the interest of contributing (instead of just
trashing) to the proposed implementation, I wrote
a simple Perl script to get some counts out of a
real-world XSL-FO file.
Input: The XSL-FO file produced from a DocBook file
I have left from a dormant project. The perl program
counts the number
John Austin wrote:
In the interest of contributing (instead of just
trashing) to the proposed implementation, I wrote
a simple Perl script to get some counts out of a
real-world XSL-FO file.
Input: The XSL-FO file produced from a DocBook file
I have left from a dormant project. The perl program
Darn, racall the last post.
John Austin wrote:
Note that storing the property name and value refs supplied
to the Property constructor will use 45,620 strings. If the
Property implementation employs canonical mapping to ensure
that only one copy of each unique string is stored, then just
over
On Sat, 2003-11-29 at 16:35, J.Pietschmann wrote:
Darn, racall the last post.
John Austin wrote:
Note that storing the property name and value refs supplied
to the Property constructor will use 45,620 strings. If the
Property implementation employs canonical mapping to ensure
that only
