cvs commit: xml-fop/docs/xml-docs/fop track.png readme.xml

keiron 02/05/16 01:37:09 Modified:docs/xml-docs/fop readme.xml Added: docs/xml-docs/fop track.png Log: added status info to main page Revision ChangesPath 1.20 +25 -0 xml-fop/docs/xml-docs/fop/readme.xml Index: readme.xml

FW: Environment problem

Sorry for crossposting, but the problem occures, if I try to get the Parser from FOInputHandler in the junit test case. inputHandler.getParser() throws a FOPException: org.apache.fop.apps.FOPException: org.apache.xerces.parsers.SAXParser is not a SAX driver at org.apache.fop.apps.InputHandler.cre

status on website

Hi, I added some status info to the website. So hopefully this will answer some peoples questions (I'm sure they will still want to know more things that are unknown). Any comments, complaints, suggestions? (apart from my poor spelling!) Keiron. ---

Re: status on website

Hi, Comment: Good idea. Suggestion: It probably wouldn't hurt to go ahead (on the page) and answer the inevitable, "Can you please tell me when to expect the release FOP0.20.4|FOP10 DR1 announced on your status page?" The same answer that would otherwise appear here, that is. Complaint: My co

RE: Environment problem (fixed)

Hi, just for information, for anyone, who gets in the same trouble! I've found the problem with the obsoleter SAX-2 implementation. In my classpath are 2 different xml-api's (I know about that, but I cannot avoid that, because of foreign parts in our app are delivered with this api contained in

DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 6997] - Row-spanned row data breaks over a page within a column

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: [PATCH] Proper use of font encodings for "native" fonts

Keiron Liddle schrieb: > One reason for waiting was to see how it would work. There are some user > issues that have popped up but nothing too serious. It would be good to > know how people should deal with this situation. > > A new patch would certainly help. Christian might be able to say more

[GUMP] Build Failure - xml-fop

This email is autogenerated from the output from: Buildfile: build.xml init-avail: init-filters-xalan2: [copy] Copying 1

Compile error with FOP

Hy Keiron. I suppose you have an SCM problem with Batik class. The actual release delivered with FOP last build xml-fop_20020516103601.tar.gz As you wrote PDFGraphics2D.java, I send you that mail. As I'm not very graphics today, I just wrote this empty method public VolatileImage createC

AW: direct rendering of images to pdf

These notes apply to under FOP 0.20.1: o FOP images are kept as XObjects until the end of job, because - the image is written to the output file - and the complete image object is added to the XObjects vector in order to build the ressource dictionary at the end of the PDF docume

RE: Font Metrics AWT

I have found the problem and worked out its repair. The modified code is attached below. The problem stems from a bug in java's handling of drawing of AttributedStrings when a font attribute is specified. Bug parade #4650042 describes a similar problem unique to jdk 1.4, but makes also suggests

Re: new batik

Keiron Liddle schrieb: > Hi, > > Since a new beta of batik has been released I think we can go with this > for the next release. > > I will put the new batik into cvs and update the code to work with it. Is it possible to make Fop work without batik.jar ? (of course if no svg is used) > Keiro

Re: Character encoding on other platforms (previously os/390)

[EMAIL PROTECTED] schrieb: > I've had a couple folks ask me for the modified code so the proper character > encoding is returned on the toString().getBytes() > is US-ASCII. This is cool that other people besides me need this. [..] > I downloaded this snapshot xml-fop_20020515162132 and I don't s

Re: status on website

Keiron Liddle schrieb: > Hi, > > I added some status info to the website. So hopefully this will answer Cool > some peoples questions (I'm sure they will still want to know more > things that are unknown). Sure ;-) > Any comments, complaints, suggestions? (apart from my poor spelling!) Maybe

AW: new batik

Hello Christian, yes, it is possible to run FOP without batik, but you have to change the source. You have to remove all the imports to packages svg... and kick out all the references to classes having to do with svg. In fact we did this and we have a working version based on FOP 0.20.3 running

Type H Encoding printing problems

I encountered a problem with embedding fonts with the command prompt like this... ( java org.apache.fop.fonts.apps.TTFReader C:\myfonts\arial.ttf arial.xml) Why is it that it always has this Encoding Type H ? The encoding really ruins the printing format and the line spacing in Acrobat Reader? Is

Re: status on website

Christian Geisert wrote: > Maybe put it on top of the page (or an extra page?) > I fear quite a few people won't scroll down that far ... According to one of the Norman Nielsen usability studies, http://www.useit.com/alertbox/ nearly 30% of (average) web users wont find information if it's not

Re: Compile error with FOP

GALLO Jean-Claude wrote: > I suppose you have an SCM problem with Batik class. The actual release > delivered with FOP last build xml-fop_20020516103601.tar.gz ... > But running result build, I get the following. > .. > WARNING: child LM not a BPLayoutManager: > org.apache.fop.layoutmgr.BlockL

Interesting Comment

Example #4 in Brett McLaughlin's XML Data Binding article on OReilly Net (http://www.onjava.com/pub/a/onjava/2002/05/15/databind.html). Pretty obvious stuff but it's nice to see that people outside the XSL-FO community are aware of the technology and finding uses for it. Regards, AHS

Re: new batik

On Thu, 2002-05-16 at 17:53, Christian Geisert wrote: > Is it possible to make Fop work without batik.jar ? (of course if no svg > is used) This is addressed in the new code. Until then no, not without disabling it entirely.