If a MO:DCA parser is added, then that should definitely be in
a separate sub-project of XML Graphics.

For the rest, knowing next to nothing about AFP, I have no opinion.

Vincent


Peter Hancock wrote:
> Hi Jeremias,
> 
> I totally agree with you here.  Time constraints did not allow me to
> create a proper parser/object model for the AFP resource but it is the
> only sensible way to read them safely - as your error reinforces.
> It would be great to use your MO:DCA parser to improve this feature,
> when you are ready to integrate it.
> 
> Thanks for your comments
> 
> Peter
> 
> On Fri, Aug 20, 2010 at 8:47 AM,  <[email protected]> wrote:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=49379
>>
>> --- Comment #2 from Jeremias Maerki <[email protected]> 2010-08-20 
>> 03:46:59 EDT ---
>> Peter, I've taken a look at your patch. I found that I get an IOException 
>> when
>> referencing the page segment "s1islogo.psg" that comes with IBM AFP 
>> Workbench:
>>
>> java.io.IOException: Malformed AFP resource with name 's1islogo':    No Begin
>> structured field
>> at
>> org.apache.fop.afp.util.AFPResourceUtil.copyNamedResource(AFPResourceUtil.java:123)
>>
>> I have the impression that the method AFPResourceUtil.findStart() may not be
>> ideal to parse an MO:DCA file. I haven't investigated more closely why the
>> above file fails, but stepping through findStart() feels a bit weird in terms
>> of how that method looks for the requested resource. Some time ago I started 
>> a
>> rudimentary AFP parser I used to dump the Type 1 data from an outline font, 
>> or
>> to simply dump the basic structure of an AFP file. I could include that in 
>> FOP
>> and we build from there. It allows to return an object for each structured
>> field encountered. A generic MO:DCA parser would also allow future
>> functionality that involves parsing an AFP file. WDYT?
>>
>> --
>> Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
>> ------- You are receiving this mail because: -------
>> You are the assignee for the bug.
>>

Reply via email to