DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28705.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=5335.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29608.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I guess I'm the guilty one here--but I have the
tabbing option shut off in JEdit, I'll be more careful
(and test at home what is happening.)
Sorry/Thanks,
Glen
--- [EMAIL PROTECTED] wrote:
jeremias2004/09/23 03:04:36
Modified:src/java/org/apache/fop/area
StorePagesModel.java
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=5335.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=14356.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
[Thread moved from fop-user]
Jeremias Maerki wrote:
Note: Support for EPS graphics in PDF has been deprecated
with the latest specs.
When I saw this comment, I went looking for this in the PDF Reference, Third
Edition (for PDF 1.4) and Fourth Edition (for PDF 1.5), and couldn't find
it.
On 23.09.2004 16:38:51 Victor Mote wrote:
[Thread moved from fop-user]
Jeremias Maerki wrote:
Note: Support for EPS graphics in PDF has been deprecated
with the latest specs.
When I saw this comment, I went looking for this in the PDF Reference, Third
Edition (for PDF 1.4) and
Jeremias Maerki wrote:
PDF Reference Fourth Edition Version 1.5:
Chapter 4.7.1, page 296:
Note: Since PDF 1.4 encompasses all of the Adobe imaging
model features of the PostScript language, there is no longer
any reason to use PostScript XObjects. This feature is likely
to be removed
Yes, I mean java.awt.Graphics2D because if you have that you can
generate PDF (using the PDF transcoder) and SVG (using Batik's
SVGGraphics2D) from it already and you can even use it with the AWT
renderer (which I prefer to call Java2D renderer). Obviously, this is
not important for PS output
On Sep 23, 2004, at 11:07 AM, Jeremias Maerki wrote:
Well, you've just loaded me with another exciting thing to watch. I've
already got too many of them. Damn. Can we vote on making a day last
26h
instead of 24?
+1! Ride 'em cowboy! This *is* exciting! I haven't had this much fun
watching the
On 23.09.2004 20:18:33 Clay Leeds wrote:
On Sep 23, 2004, at 11:07 AM, Jeremias Maerki wrote:
Well, you've just loaded me with another exciting thing to watch. I've
already got too many of them. Damn. Can we vote on making a day last
26h
instead of 24?
+1! Ride 'em cowboy! This *is*
Hi Team,
I think the API for adding additional element mappings to the
FOUserAgent is bound to cause problems when fop is deployed in a multi
classloader environment.
Using tomcat as an example, an extension mapping deployed in a webapp
can not be found if a well meaning administrator has
On 23.09.2004 23:34:20 Finn Bock wrote:
I think the API for adding additional element mappings to the
FOUserAgent is bound to cause problems when fop is deployed in a multi
classloader environment.
Using tomcat as an example, an extension mapping deployed in a webapp
can not be found if
--- Jeremias Maerki [EMAIL PROTECTED] wrote:
So I propose to change the API signature from
FOUserAgent.addElementMapping(String)
to
FOUserAgent.addElementMapping(ElementMapping)
Keep both, please.
Unless there is a legitimate reason, I would strongly
prefer choosing one or
Hi,
Thanks for the support.
I will go ahead and do whatever I can to help out with this and be part
of the XML graphics PMC.
I have read all the emails about this concept and think that it is a
good idea and should help things develop in useful directions.
Regards,
Keiron Liddle
-Original
Jeremias Maerki wrote:
Batik and FOP devs,
things have been quiet but I finally know the
reason.
The board hasn't
approved the creation of the XML Graphics project
due to the following
concern: They didn't recognize any names on the PMC
list.
Jeremias, this is just not plausible.
(resending...having email problems)
Team (probably Jeremias),
According to [1] JIMI is for pre-Java2 JDK's (1.1
series). JAI is for 1.3 or later JDK's [2], which is
FOP 1.0's area of concern. If so, does this mean we
can get rid of image.JimiImage in HEAD, FOP 1.0
presumably not designed to
On Sep 23, 2004, at 5:54 PM, Glen Mazza wrote:
Jeremias Maerki wrote:
Batik and FOP devs,
things have been quiet but I finally know the
reason.
The board hasn't
approved the creation of the XML Graphics project
due to the following
concern: They didn't recognize any names on the PMC
list.
Team,
Anyone know of a reason to keep Area.Title subclassed
[1] from LineArea? The subclass is empty and has been
since its inception three years ago, and the
definition of the fo:title element [2] doesn't appear
to indicate anything special that would call for its
subclassing from LineArea.
20 matches
Mail list logo