:52 AM
Subject: Re: [iText-questions] RTF Parser update
I guess that splitting the RTF parser into another jar is the solution.
Paulo
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Howard Shank
> Sent: Wednesday, December 05, 2007 7
ext here
> Subject: Re: [iText-questions] RTF Parser update
>
> >> There are so many control words in the RTF spec that I tried to
> >> simplify the creation of the classes through automating the
> >> generation of them. This way new control words
> (RtfCtrl
>> There are so many control words in the RTF spec that I tried to
>> simplify the creation of the classes through automating the
>> generation of them. This way new control words (RtfCtrlWordBase_*)
>> can be added through the generation process without disturbing
>> manual coding that may
On 5 Dec 2007, at 18:23, Howard Shank wrote:
> There are so many control words in the RTF spec that I tried to
> simplify the creation of the classes through automating the
> generation of them. This way new control words (RtfCtrlWordBase_*)
> can be added through the generation process with
From: Mark Hall <[EMAIL PROTECTED]>
To: Post all your questions about iText here
Sent: Wednesday, December 5, 2007 1:04:14 PM
Subject: Re: [iText-questions] RTF Parser update
Hi,
I must admit, that I didn't take the size of the resulting jars into
consideration when add
Hi Paulo,
I agree with the source size issue. One side note is the size almost tripled
when I added all the license comment blocks.
>Looks like it does exactly the same as the base class.
Yes. I agree that is what it "looks" like at the moment. This is because the
functionality of each contro
WordBase
> for some specific uses. This would probably allow iText to be
> distributed in a single jar.
>
> Paulo
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On
>> Behalf Of Howard Shank
>> Sent: Wednesday
Sent: Wednesday, December 05, 2007 3:47 PM
> To: Post all your questions about iText here
> Subject: Re: [iText-questions] RTF Parser update
>
> Paulo,
>
> The tests in the previous message were run in debug mode.
>
> Running in release mode (no debug) the timings for
Paulo,
The tests in the previous message were run in debug mode.
Running in release mode (no debug) the timings for creation and population of
the HastMap object are in the 60ms range.
Howard
Be a bett
ednesday, December 5, 2007 5:56:38 AM
Subject: Re: [iText-questions] RTF Parser update
I had a very quick look at the thousands of new classes created and I
have a few remarks:
- it looks like 99% of those classes could be eliminated and a generic
class with some parameters be created when load
f Of Howard Shank
> Sent: Tuesday, December 04, 2007 9:48 PM
> To: Post all your questions about iText here
> Subject: [iText-questions] RTF Parser update
>
> Hello everyone,
>
> Just a quick note to let everyone know there was a pretty big
> update the the RtfParser today. M
Hello everyone,
Just a quick note to let everyone know there was a pretty big update the the
RtfParser today. Mark Hall was gracious enough to review and accept the changes
and added the update to the repository today.
New parser features:
Correctly parses all control words, parameters and data
12 matches
Mail list logo
