Hmm, you're right. This is more complicated that I thought. Getting the
actual position of a link destination on a page is easily done with
information from PDFRenderer. But to know the actual page of the link
destionation requires the registration of the ID as an item of interest
at layout time.
It just occurred to me that as an alternative we could simply track all
XSL-FO IDs unconditionally. That would make scanning the SVG (or HTML or
MathML) for links unnecessary. The overhead is probably even smaller and
could actually have additional side-benefits for certain special use
cases. For
I have to call in sick today so this is my last message for now. Just to
give you some feedback. BTW, I noticed this should move to fop-dev since
we're discussion development. Please drop the fop-users CC in any
follow-ups.
On 03.09.2008 10:00:59 Stefan Bund wrote:
Jeremias Maerki [EMAIL
Hi,
We am more than happy to spend time on this and hopefully fix and submit it
back. However having never filed a defect or committed to FOP before is
there are starter for 10 that tells me about servers/repositories/locations
etc and the general process to be followed.
Many Thanks
Lea.
Manuel,
We create the XML using a version of BASIC. To create this particular
character, we send CHR(130) to the XML. When I open the XML in vi, I
see the proper FRENCH symbol.
Jeff
From: Manuel Mall [mailto:[EMAIL PROTECTED]
Sent:
There are four kinds of accent current in French (é è ê ë) so you should
be more precise.
None of them can possibly correspond to CHR(130) neither in UTF-8 nor in
ISO-8859-1
On what kind of system/platform/OS are you working ?
Mentioning vi makes me guess it should be some kind of Unix but at
Jean-Francois,
fop-0.95
I am running Redhat Linux 2.4.21-47.0.1.
The letter I am referring to is: é è
I assume I am having problems with any French character that includes a glyph.
What are you using for ?xml version=1.0 encoding=?
I appreciate any suggestions. I have not had to
Jean-Francois,
On my Linux box I have this entry in: /etc/sysconfig/i18n
LANG=en_US.iso885915
Jeff Steffanina
FOSSE Development, Bethesda, MD
(301)380-2047
[EMAIL PROTECTED]
This communication contains information from Marriott International, Inc.
that may be confidential. Except for
On Sep 3, 2008, at 15:05, Steffanina, Jeff wrote:
Hi Jeff
fop-0.95
I am running Redhat Linux 2.4.21-47.0.1.
The letter I am referring to is: é è
I assume I am having problems with any French character that
includes a glyph.
What are you using for ?xml version=1.0 encoding=?
I
There is always one MORE option to consider!!
What would you suggest as the best way to handle this?
Jeff
-Original Message-
From: Andreas Delmelle [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 03, 2008 12:32 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Error when
On 8/28/2008 9:34 AM, Jubal Kessler wrote:
Aug 28, 2008 6:20:05 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: No ImagePreloader found for
As closure, it turns out I had been staring too long at the same XSL-FO
template, and the problem was a simple error in
On Sep 3, 2008, at 18:35, Steffanina, Jeff wrote:
Hi Jeff
There is always one MORE option to consider!!
What would you suggest as the best way to handle this?
I think I'd opt for using (N)umeric (C)haracter (R)eferences.
Reasoning would be that if one changes the BASIC code to emit the
Hi all,
I'm currently using FOP 0.93, and I've just started looking at
using SVG images in the rendered PDFs. One thing that I have
noticed is that the image size of the resulting PDF grows
considerably.
It would appear that if I import an SVG multiple times, the
resulting PDF includes a new
13 matches
Mail list logo
