You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Jeremias Maerki <de...@jeremias-maerki.ch> on 2007/12/14 10:00:07 UTC
AFP Renderer problems (Re: svn commit: r603590)
Adrian,
I wanted to plug in the new image package into the AFPRenderer in the
branch and found out that I cannot even render the simplest of SVGs
(like [1]) after the addition of the Graphics2D implementation here. The
image is painted but much too small and in the wrong place.
Furthermore, I noticed that there are NullPointerExceptions as soon as a
user calls AFPGraphics2D.create() because the parent values are not
copied from the parent Graphics2D in the copy constructor.
AFPGraphics2D.create() is called whenever there's a need for a new
coordinate system inside the image (it's the equivalent to gsave/grestore
in PostScript). Maybe you need to test with some more complex SVG and
maybe you need to provide a configurable fallback mechanism to paint
SVGs using bitmaps as long as the Graphics2D implementation is not
stable enough.
[1] https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/resources/images/img-w-size.svg
On 12.12.2007 13:24:16 acumiskey wrote:
> Author: acumiskey
> Date: Wed Dec 12 04:24:10 2007
> New Revision: 603590
>
> URL: http://svn.apache.org/viewvc?rev=603590&view=rev
> Log:
> * Added an SVG handler and Graphics2D implementation for AFP which injects AFP GOCA structured fields into the AFPDataStream.
> * Fixed many checkstyle problems.
> * Updated xmlgraphics-commons-1.3svn.jar to include changes to TextHandler
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 15.01.2008 18:04:14 Adrian Cumiskey wrote:
> Hi Jeremias,
>
> The AFPRenderer should still work fine and produce valid AFP documents, its just source documents
> which contain embedded SVG will not be rendered correctly (but will still contain valid AFP).
Uhm, in that case you should run block-container_absolute-position_reference-orientation.xml
through the AFP renderer. No SVG and still no luck:
- IE plugin & AFP workbench are not displaying any text
- AFP Explorer is even crashing
> It
> should be fine to just update me with the details of your area tree changes and I will make the
> necessary adjustments to the AFPRenderer... that'll teach me to work from trunk.. :)
Thanks!
> Adrian.
>
> Jeremias Maerki wrote:
> > Thanks for the feedback. It's certainly cool if you can make a single
> > SVG (or other graphic) a separate resource group that can potentially be
> > reused. It's something I'd like to do for PDF at some point.
> >
> > The reason I was pinging you was that I'm working on that semantic
> > change in the area tree I was writing about last week. Since the
> > AFPRenderer is currently broken and you're working on it I will not be
> > able to adjust the AFPRenderer to that semantic change. I'll just fix
> > the other renderers and will inform you about the details. Can you then
> > do the necessary adjustments in the AFPRenderer? It won't be too hard.
> > Thanks.
> >
> > On 15.01.2008 17:25:14 Adrian Cumiskey wrote:
> >> Hi Jeremias,
> >>
> >> I have tested the AFP output with a number of applications and the AFPRenderer is at fault here.
> >> The GOCA should have been included as part of an overlay rather than just added to the current page.
> >> But in doing so would break the current way that documents are constructed by the AFP datastream.
> >>
> >> Another issue which is related to this implementation is the more general way that resources
> >> (images/graphics/fonts etc) are handled (or not). Currently the AFP renderer simply creates a new
> >> copy of the resource object with a unique name and embeds it directly in the current page. So I am
> >> looking at adding some flexibility here so that resource objects are not duplicated and are instead
> >> included and stored (keeping their original source name) within a resource group. A configurable
> >> option will also be provided so you are able to set the level at which you would like the resources
> >> to be stored (externally, print-file, document, page-group or page). When this is done I will use
> >> the this new implementation to include graphics objects correctly.
> >>
> >> Adrian.
> >>
> >> Jeremias Maerki wrote:
> >>> Adrian,
> >>>
> >>> do you have an update on this topic? It would be good to know if the IE
> >>> plug-in is at fault or the AFPRenderer.
> >>>
> >>> On 14.12.2007 15:31:19 Jeremias Maerki wrote:
> >>>> FO file is attached (to be run from the FOP root directory).
> >>>>
> >>>> Expectation: see out.pdf
> >>>> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
> >>>>
> >>>> (produced with FOP Trunk rev 604185)
> >>>>
> >>>> It could very well be that the IE plug-in has a problem here. I have no
> >>>> other viewer to check against.
> >>>>
> >>>> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
> >>>>> Jeremias Maerki wrote:
> >>>>>> I only have the IE plugin. No AFP hardware to test with. snif.
> >>>>>>
> >>>>>> Basically, it was just a:
> >>>>>> <fo:block>
> >>>>>> <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> >>>>>> </fo:block>
> >>>>>>
> >>>>>> No special configuration (i.e. the defaults). Really the simplest of
> >>>>>> possible cases and it came out wrong.
> >>>>> How did you expect it to come out? How do you think it is wrong?
> >>>>>
> >>>>> Adrian.
> >>>>
> >>>>
> >>>> Jeremias Maerki
> >>>
> >>>
> >>>
> >>> Jeremias Maerki
> >>>
> >>>
> >
> >
> >
> >
> > Jeremias Maerki
> >
> >
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Resources like graphics, fonts and XMP are not really the problem here.
Graphics are still referenced by URI or embedded as foreign XML. Fonts
need to be handled by the IFHandler anyway, the fonts are only
referenced by name plus additional properties. XMP is handled the same
way as foreign XML. Some other extensions may have more impact here.
Furthermore, the renderers handle resource management themselves,
based on what they support (PDF has objects which makes it easy, PS
requires rewriting the whole PS file to factor out resources used
multiple times, Java2D doesn't do any resource optimization).
The main point I wanted to make here is differences in the fundamental
approach of the different output formats. An example:
PDF, PS and Java2D can all handle free-form transformation à la
AffineTransform (translation, free rotation, skewing). PCL, however,
only allows rotation by 90 degree steps, no scaling (you can only scale
by modifying font sizes and line widths), no skewing. If you switch from
PCL to HP/GL you can do some more but you still stay way behind the
first three formats. I'm not sure about AFP but it may have some
restrictions, too, but probably not as many as PCL.
If we did what you propose, we'd actually have to incorporate
renderer-specific code in the IFRenderer which I absolutely want to
avoid because it splits the logic between two components which doesn't
help us.
On 16.01.2008 23:13:56 Andreas L Delmelle wrote:
> On Jan 16, 2008, at 08:15, Jeremias Maerki wrote:
>
> > Hey, I don't like doing stuff twice or more times. Each output format
> > has its own specifics and there are limits to what extent
> > commonalities
> > can be extracted. For example, some formats don't support free-form
> > transformations. In PCL, it's impossible to write a Graphics2D
> > implementation that doesn't end up using bitmaps instead of native
> > commands to paint the individual elements. Actually, that fact is
> > exactly the point what's concerning me most if I think about a new
> > intermediate format which will result in a different kind of
> > abstraction
> > for the rendering components.
>
> Hmm... So it seems like it does not only depend on the renderer, but
> also on the type of resource (graphic, font, XMP metadata packet...).
> Maybe separating into an AbstractRendererResource would be an idea:
> a PDFFontResource could easily share logic with an AWTFontResource or
> AFPFontResource, or even PDFGraphicResource.
>
> Point being that their interface towards the AbstractRenderer remains
> uniform, while the behaviour can still be dedicated to one specific
> renderer.
>
> Those components/resources that apply to all types of renderers, can
> be handled in AbstractRenderer.
> AbstractRenderer could provide a generic createResource() method,
> which can be overridden or re-implemented in the specific renderer
> types to handle the renderer-specific stuff.
>
> Coming to the Intermediate Format: that document should, as you
> mentioned earlier IIRC, ideally be renderer-agnostic. So, if all is
> set up well, the resources can be embedded/referenced in the
> intermediate document as abstract <resource> nodes, with a reference
> (attribute?) to the applicable renderers. Some resources may have to
> be inserted multiple times for different renderers? So be it. The
> IFHandler should probably be made intelligent enough to ignore/
> disregard any nodes that do not apply to the current output format,
> so they get excluded real early in the game. When the document is
> ultimately rendered, the eventual renderer type will determine what
> needs to happen with the embedded resource.
>
>
> Cheers
>
> Andreas
>
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jan 17, 2008, at 09:55, Chris Bowditch wrote:
> Andreas L Delmelle wrote:
>
> <snip/>
>
>> Those components/resources that apply to all types of renderers,
>> can be handled in AbstractRenderer.
>> AbstractRenderer could provide a generic createResource() method,
>> which can be overridden or re-implemented in the specific
>> renderer types to handle the renderer-specific stuff.
>> Coming to the Intermediate Format: that document should, as you
>> mentioned earlier IIRC, ideally be renderer-agnostic. So, if all
>> is set up well, the resources can be embedded/referenced in the
>> intermediate document as abstract <resource> nodes, with a
>> reference (attribute?) to the applicable renderers. Some
>> resources may have to be inserted multiple times for different
>> renderers? So be it. The IFHandler should probably be made
>> intelligent enough to ignore/ disregard any nodes that do not
>> apply to the current output format, so they get excluded real
>> early in the game. When the document is ultimately rendered, the
>> eventual renderer type will determine what needs to happen with
>> the embedded resource.
>
> The downside to including a resource node for each possible
> renderer is the space occupied by the Intermediate Format.
Wouldn't be much, if we precisely aim at keeping them in the document
root.
> The major problem with the current IF XML is how verbose it is.
> This verbosity is what makes the performance of FO->IF->PDF so
> slow. This is the main driver for re-working the current
> implementation.
Qua processing, when the eventual IF XML is read back in, the
resource nodes that do not apply to the output format for that run
should generate only very little overhead, since we would ignore
them. If the goal is to have one and the same IF XML that can be
transparently rendered to either PDF, AFP or PCL, then including
separate resources for separate renderers may turn out to be a
necessary evil... If some renderers can be made to share resources
(or logic in handling specific resource types), all the better, but I
think Jeremias precisely hinted on that having its limits.
Cheers
Andreas
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Chris Bowditch <bo...@hotmail.com>.
Andreas L Delmelle wrote:
<snip/>
>
> Those components/resources that apply to all types of renderers, can be
> handled in AbstractRenderer.
> AbstractRenderer could provide a generic createResource() method, which
> can be overridden or re-implemented in the specific renderer types to
> handle the renderer-specific stuff.
>
> Coming to the Intermediate Format: that document should, as you
> mentioned earlier IIRC, ideally be renderer-agnostic. So, if all is set
> up well, the resources can be embedded/referenced in the intermediate
> document as abstract <resource> nodes, with a reference (attribute?) to
> the applicable renderers. Some resources may have to be inserted
> multiple times for different renderers? So be it. The IFHandler should
> probably be made intelligent enough to ignore/ disregard any nodes that
> do not apply to the current output format, so they get excluded real
> early in the game. When the document is ultimately rendered, the
> eventual renderer type will determine what needs to happen with the
> embedded resource.
The downside to including a resource node for each possible renderer is
the space occupied by the Intermediate Format. The major problem with
the current IF XML is how verbose it is. This verbosity is what makes
the performance of FO->IF->PDF so slow. This is the main driver for
re-working the current implementation.
Chris
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jan 16, 2008, at 08:15, Jeremias Maerki wrote:
> Hey, I don't like doing stuff twice or more times. Each output format
> has its own specifics and there are limits to what extent
> commonalities
> can be extracted. For example, some formats don't support free-form
> transformations. In PCL, it's impossible to write a Graphics2D
> implementation that doesn't end up using bitmaps instead of native
> commands to paint the individual elements. Actually, that fact is
> exactly the point what's concerning me most if I think about a new
> intermediate format which will result in a different kind of
> abstraction
> for the rendering components.
Hmm... So it seems like it does not only depend on the renderer, but
also on the type of resource (graphic, font, XMP metadata packet...).
Maybe separating into an AbstractRendererResource would be an idea:
a PDFFontResource could easily share logic with an AWTFontResource or
AFPFontResource, or even PDFGraphicResource.
Point being that their interface towards the AbstractRenderer remains
uniform, while the behaviour can still be dedicated to one specific
renderer.
Those components/resources that apply to all types of renderers, can
be handled in AbstractRenderer.
AbstractRenderer could provide a generic createResource() method,
which can be overridden or re-implemented in the specific renderer
types to handle the renderer-specific stuff.
Coming to the Intermediate Format: that document should, as you
mentioned earlier IIRC, ideally be renderer-agnostic. So, if all is
set up well, the resources can be embedded/referenced in the
intermediate document as abstract <resource> nodes, with a reference
(attribute?) to the applicable renderers. Some resources may have to
be inserted multiple times for different renderers? So be it. The
IFHandler should probably be made intelligent enough to ignore/
disregard any nodes that do not apply to the current output format,
so they get excluded real early in the game. When the document is
ultimately rendered, the eventual renderer type will determine what
needs to happen with the embedded resource.
Cheers
Andreas
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Hey, I don't like doing stuff twice or more times. Each output format
has its own specifics and there are limits to what extent commonalities
can be extracted. For example, some formats don't support free-form
transformations. In PCL, it's impossible to write a Graphics2D
implementation that doesn't end up using bitmaps instead of native
commands to paint the individual elements. Actually, that fact is
exactly the point what's concerning me most if I think about a new
intermediate format which will result in a different kind of abstraction
for the rendering components.
On 15.01.2008 23:18:07 Andreas L Delmelle wrote:
> On Jan 15, 2008, at 17:53, Jeremias Maerki wrote:
>
> Hi guys
>
> Sorry to interrupt (currently being completely AFP-agnostic :-))
>
> > Thanks for the feedback. It's certainly cool if you can make a single
> > SVG (or other graphic) a separate resource group that can
> > potentially be
> > reused. It's something I'd like to do for PDF at some point.
>
> I do hope Adrian read this as:
> "By all means, if you can extract logic and put it in
> AbstractRenderer, go right ahead." ;-)
>
> Seriously, this would be beneficial to all renderer types, so some of
> it at least deserves a place at the higher level.
>
> Just my two cents.
>
> Cheers
>
> Andreas
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Adrian Cumiskey <ad...@gmail.com>.
Hi Jeremias,
The AFPRenderer should still work fine and produce valid AFP documents, its just source documents
which contain embedded SVG will not be rendered correctly (but will still contain valid AFP). It
should be fine to just update me with the details of your area tree changes and I will make the
necessary adjustments to the AFPRenderer... that'll teach me to work from trunk.. :)
Adrian.
Jeremias Maerki wrote:
> Thanks for the feedback. It's certainly cool if you can make a single
> SVG (or other graphic) a separate resource group that can potentially be
> reused. It's something I'd like to do for PDF at some point.
>
> The reason I was pinging you was that I'm working on that semantic
> change in the area tree I was writing about last week. Since the
> AFPRenderer is currently broken and you're working on it I will not be
> able to adjust the AFPRenderer to that semantic change. I'll just fix
> the other renderers and will inform you about the details. Can you then
> do the necessary adjustments in the AFPRenderer? It won't be too hard.
> Thanks.
>
> On 15.01.2008 17:25:14 Adrian Cumiskey wrote:
>> Hi Jeremias,
>>
>> I have tested the AFP output with a number of applications and the AFPRenderer is at fault here.
>> The GOCA should have been included as part of an overlay rather than just added to the current page.
>> But in doing so would break the current way that documents are constructed by the AFP datastream.
>>
>> Another issue which is related to this implementation is the more general way that resources
>> (images/graphics/fonts etc) are handled (or not). Currently the AFP renderer simply creates a new
>> copy of the resource object with a unique name and embeds it directly in the current page. So I am
>> looking at adding some flexibility here so that resource objects are not duplicated and are instead
>> included and stored (keeping their original source name) within a resource group. A configurable
>> option will also be provided so you are able to set the level at which you would like the resources
>> to be stored (externally, print-file, document, page-group or page). When this is done I will use
>> the this new implementation to include graphics objects correctly.
>>
>> Adrian.
>>
>> Jeremias Maerki wrote:
>>> Adrian,
>>>
>>> do you have an update on this topic? It would be good to know if the IE
>>> plug-in is at fault or the AFPRenderer.
>>>
>>> On 14.12.2007 15:31:19 Jeremias Maerki wrote:
>>>> FO file is attached (to be run from the FOP root directory).
>>>>
>>>> Expectation: see out.pdf
>>>> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
>>>>
>>>> (produced with FOP Trunk rev 604185)
>>>>
>>>> It could very well be that the IE plug-in has a problem here. I have no
>>>> other viewer to check against.
>>>>
>>>> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
>>>>> Jeremias Maerki wrote:
>>>>>> I only have the IE plugin. No AFP hardware to test with. snif.
>>>>>>
>>>>>> Basically, it was just a:
>>>>>> <fo:block>
>>>>>> <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
>>>>>> </fo:block>
>>>>>>
>>>>>> No special configuration (i.e. the defaults). Really the simplest of
>>>>>> possible cases and it came out wrong.
>>>>> How did you expect it to come out? How do you think it is wrong?
>>>>>
>>>>> Adrian.
>>>>
>>>>
>>>> Jeremias Maerki
>>>
>>>
>>>
>>> Jeremias Maerki
>>>
>>>
>
>
>
>
> Jeremias Maerki
>
>
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Andreas L Delmelle <a_...@pandora.be>.
On Jan 15, 2008, at 17:53, Jeremias Maerki wrote:
Hi guys
Sorry to interrupt (currently being completely AFP-agnostic :-))
> Thanks for the feedback. It's certainly cool if you can make a single
> SVG (or other graphic) a separate resource group that can
> potentially be
> reused. It's something I'd like to do for PDF at some point.
I do hope Adrian read this as:
"By all means, if you can extract logic and put it in
AbstractRenderer, go right ahead." ;-)
Seriously, this would be beneficial to all renderer types, so some of
it at least deserves a place at the higher level.
Just my two cents.
Cheers
Andreas
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Thanks for the feedback. It's certainly cool if you can make a single
SVG (or other graphic) a separate resource group that can potentially be
reused. It's something I'd like to do for PDF at some point.
The reason I was pinging you was that I'm working on that semantic
change in the area tree I was writing about last week. Since the
AFPRenderer is currently broken and you're working on it I will not be
able to adjust the AFPRenderer to that semantic change. I'll just fix
the other renderers and will inform you about the details. Can you then
do the necessary adjustments in the AFPRenderer? It won't be too hard.
Thanks.
On 15.01.2008 17:25:14 Adrian Cumiskey wrote:
> Hi Jeremias,
>
> I have tested the AFP output with a number of applications and the AFPRenderer is at fault here.
> The GOCA should have been included as part of an overlay rather than just added to the current page.
> But in doing so would break the current way that documents are constructed by the AFP datastream.
>
> Another issue which is related to this implementation is the more general way that resources
> (images/graphics/fonts etc) are handled (or not). Currently the AFP renderer simply creates a new
> copy of the resource object with a unique name and embeds it directly in the current page. So I am
> looking at adding some flexibility here so that resource objects are not duplicated and are instead
> included and stored (keeping their original source name) within a resource group. A configurable
> option will also be provided so you are able to set the level at which you would like the resources
> to be stored (externally, print-file, document, page-group or page). When this is done I will use
> the this new implementation to include graphics objects correctly.
>
> Adrian.
>
> Jeremias Maerki wrote:
> > Adrian,
> >
> > do you have an update on this topic? It would be good to know if the IE
> > plug-in is at fault or the AFPRenderer.
> >
> > On 14.12.2007 15:31:19 Jeremias Maerki wrote:
> >> FO file is attached (to be run from the FOP root directory).
> >>
> >> Expectation: see out.pdf
> >> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
> >>
> >> (produced with FOP Trunk rev 604185)
> >>
> >> It could very well be that the IE plug-in has a problem here. I have no
> >> other viewer to check against.
> >>
> >> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
> >>> Jeremias Maerki wrote:
> >>>> I only have the IE plugin. No AFP hardware to test with. snif.
> >>>>
> >>>> Basically, it was just a:
> >>>> <fo:block>
> >>>> <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> >>>> </fo:block>
> >>>>
> >>>> No special configuration (i.e. the defaults). Really the simplest of
> >>>> possible cases and it came out wrong.
> >>> How did you expect it to come out? How do you think it is wrong?
> >>>
> >>> Adrian.
> >>
> >>
> >>
> >> Jeremias Maerki
> >
> >
> >
> >
> > Jeremias Maerki
> >
> >
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Adrian Cumiskey <ad...@gmail.com>.
Hi Jeremias,
I have tested the AFP output with a number of applications and the AFPRenderer is at fault here.
The GOCA should have been included as part of an overlay rather than just added to the current page.
But in doing so would break the current way that documents are constructed by the AFP datastream.
Another issue which is related to this implementation is the more general way that resources
(images/graphics/fonts etc) are handled (or not). Currently the AFP renderer simply creates a new
copy of the resource object with a unique name and embeds it directly in the current page. So I am
looking at adding some flexibility here so that resource objects are not duplicated and are instead
included and stored (keeping their original source name) within a resource group. A configurable
option will also be provided so you are able to set the level at which you would like the resources
to be stored (externally, print-file, document, page-group or page). When this is done I will use
the this new implementation to include graphics objects correctly.
Adrian.
Jeremias Maerki wrote:
> Adrian,
>
> do you have an update on this topic? It would be good to know if the IE
> plug-in is at fault or the AFPRenderer.
>
> On 14.12.2007 15:31:19 Jeremias Maerki wrote:
>> FO file is attached (to be run from the FOP root directory).
>>
>> Expectation: see out.pdf
>> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
>>
>> (produced with FOP Trunk rev 604185)
>>
>> It could very well be that the IE plug-in has a problem here. I have no
>> other viewer to check against.
>>
>> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
>>> Jeremias Maerki wrote:
>>>> I only have the IE plugin. No AFP hardware to test with. snif.
>>>>
>>>> Basically, it was just a:
>>>> <fo:block>
>>>> <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
>>>> </fo:block>
>>>>
>>>> No special configuration (i.e. the defaults). Really the simplest of
>>>> possible cases and it came out wrong.
>>> How did you expect it to come out? How do you think it is wrong?
>>>
>>> Adrian.
>>
>>
>>
>> Jeremias Maerki
>
>
>
>
> Jeremias Maerki
>
>
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Adrian,
do you have an update on this topic? It would be good to know if the IE
plug-in is at fault or the AFPRenderer.
On 14.12.2007 15:31:19 Jeremias Maerki wrote:
> FO file is attached (to be run from the FOP root directory).
>
> Expectation: see out.pdf
> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
>
> (produced with FOP Trunk rev 604185)
>
> It could very well be that the IE plug-in has a problem here. I have no
> other viewer to check against.
>
> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
> > Jeremias Maerki wrote:
> > >
> > > I only have the IE plugin. No AFP hardware to test with. snif.
> > >
> > > Basically, it was just a:
> > > <fo:block>
> > > <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> > > </fo:block>
> > >
> > > No special configuration (i.e. the defaults). Really the simplest of
> > > possible cases and it came out wrong.
> >
> > How did you expect it to come out? How do you think it is wrong?
> >
> > Adrian.
>
>
>
>
> Jeremias Maerki
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Oops, forgot the FO file.
On 14.12.2007 15:31:19 Jeremias Maerki wrote:
> FO file is attached (to be run from the FOP root directory).
>
> Expectation: see out.pdf
> Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
>
> (produced with FOP Trunk rev 604185)
>
> It could very well be that the IE plug-in has a problem here. I have no
> other viewer to check against.
>
> On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
> > Jeremias Maerki wrote:
> > >
> > > I only have the IE plugin. No AFP hardware to test with. snif.
> > >
> > > Basically, it was just a:
> > > <fo:block>
> > > <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> > > </fo:block>
> > >
> > > No special configuration (i.e. the defaults). Really the simplest of
> > > possible cases and it came out wrong.
> >
> > How did you expect it to come out? How do you think it is wrong?
> >
> > Adrian.
>
>
>
>
> Jeremias Maerki
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
FO file is attached (to be run from the FOP root directory).
Expectation: see out.pdf
Effective output in AFP plug-in for IE: see screenshot-ie-afp.png
(produced with FOP Trunk rev 604185)
It could very well be that the IE plug-in has a problem here. I have no
other viewer to check against.
On 14.12.2007 14:58:39 Adrian Cumiskey wrote:
> Jeremias Maerki wrote:
> >
> > I only have the IE plugin. No AFP hardware to test with. snif.
> >
> > Basically, it was just a:
> > <fo:block>
> > <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> > </fo:block>
> >
> > No special configuration (i.e. the defaults). Really the simplest of
> > possible cases and it came out wrong.
>
> How did you expect it to come out? How do you think it is wrong?
>
> Adrian.
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Adrian Cumiskey <ad...@gmail.com>.
Jeremias Maerki wrote:
>
> I only have the IE plugin. No AFP hardware to test with. snif.
>
> Basically, it was just a:
> <fo:block>
> <fo:external-graphic src="test/resources/images/img-w-size.svg"/>
> </fo:block>
>
> No special configuration (i.e. the defaults). Really the simplest of
> possible cases and it came out wrong.
How did you expect it to come out? How do you think it is wrong?
Adrian.
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
On 14.12.2007 14:18:36 Adrian Cumiskey wrote:
> Jeremias,
>
> Jeremias Maerki wrote:
> > Adrian,
> >
> > I wanted to plug in the new image package into the AFPRenderer in the
> > branch and found out that I cannot even render the simplest of SVGs
> > (like [1]) after the addition of the Graphics2D implementation here. The
> > image is painted but much too small and in the wrong place.
>
> The example [1] you provide is very small (only 16pt in width and height). I have tested the
> Graphics2D implementation with a number of complicated SVG examples (tax return forms, fractal
> patterns etc). All my tests were done AFP-Lookup Professional, AFP Explorer and IBM's AFP Workbench
> Viewer (which is essentially the same app as the IE plugin), as I've found all of these products to
> be lacking in some way so I use all of them for the purposes of software testing. When I'm happy
> with how the software is interpreting the AFP byte codes I do a hard copy test by sending it to a
> queue on IBM's Infoprint Manager where it is serviced by an IBM Infoprint 1585. Could I ask you how
> you are testing your AFP output and what the context is of referencing the svg file in your fo?
I only have the IE plugin. No AFP hardware to test with. snif.
Basically, it was just a:
<fo:block>
<fo:external-graphic src="test/resources/images/img-w-size.svg"/>
</fo:block>
No special configuration (i.e. the defaults). Really the simplest of
possible cases and it came out wrong.
> > Furthermore, I noticed that there are NullPointerExceptions as soon as a
> > user calls AFPGraphics2D.create() because the parent values are not
> > copied from the parent Graphics2D in the copy constructor.
>
> This is an oversight in my testing, I tested its use only through AFPSVGHandler (which is the
> standard way it is handled). I will fix the copy constructor.
>
> Adrian.
Jeremias Maerki
Re: AFP Renderer problems (Re: svn commit: r603590)
Posted by Adrian Cumiskey <ad...@gmail.com>.
Jeremias,
Jeremias Maerki wrote:
> Adrian,
>
> I wanted to plug in the new image package into the AFPRenderer in the
> branch and found out that I cannot even render the simplest of SVGs
> (like [1]) after the addition of the Graphics2D implementation here. The
> image is painted but much too small and in the wrong place.
The example [1] you provide is very small (only 16pt in width and height). I have tested the
Graphics2D implementation with a number of complicated SVG examples (tax return forms, fractal
patterns etc). All my tests were done AFP-Lookup Professional, AFP Explorer and IBM's AFP Workbench
Viewer (which is essentially the same app as the IE plugin), as I've found all of these products to
be lacking in some way so I use all of them for the purposes of software testing. When I'm happy
with how the software is interpreting the AFP byte codes I do a hard copy test by sending it to a
queue on IBM's Infoprint Manager where it is serviced by an IBM Infoprint 1585. Could I ask you how
you are testing your AFP output and what the context is of referencing the svg file in your fo?
> Furthermore, I noticed that there are NullPointerExceptions as soon as a
> user calls AFPGraphics2D.create() because the parent values are not
> copied from the parent Graphics2D in the copy constructor.
This is an oversight in my testing, I tested its use only through AFPSVGHandler (which is the
standard way it is handled). I will fix the copy constructor.
Adrian.