DO NOT REPLY [Bug 5674] - postscript generated by FOP is missing end commands

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

cvs commit: xml-fop/src/documentation/content/xdocs resources.xml

vmote 2003/06/27 08:07:17 Modified:src/documentation/content/xdocs resources.xml Log: Add platform comment for XPath Visualizer. (Submitted by Clay Leeds). Revision ChangesPath 1.28 +4 -1 xml-fop/src/documentation/content/xdocs/resources.xml Index:

RE: [PATCH] fop's resource.xml

Clay Leeds wrote: Forgive my newbie-ness here, but I'm having problems figuring out how to send this [patch] in. I'm sending it here... Please enlighten me (gently ;-p) so that next time I'm doing it as efficiently as possible. Thanks! Thanks for the patch. The instructions are here:

RE: cvs commit: xml-fop checkstyle1.3.0-head

Peter B. West wrote: Definitely a w.i.p. It throws up too many exceptions at the moment, and needs to be pruned back by those with a better grasp of the style requirements. OK. I'll keep using the old-style version for now. Btw, are you using JBuilder with FOP? If so, could you add some

DO NOT REPLY [Bug 5674] - postscript generated by FOP is missing end commands

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

RE: [PATCH] fop's resource.xml

Clay Leeds wrote: Thanks. So essentially, I did everything correctly except I didn't open a new bugzilla item, and put '[PATCH]' at the beginning of the SUMMARY. I'll do that next time. I'll then attach the DIFF file (were there any problems with that DIFF file?). Since much of what I'll be

Re: [PATCH] fop's resource.xml

On 6/27/2003 10:33 AM, Victor Mote wrote: The only problem I saw with the DIFF file was that it was not in unified format, which helps the patch programs find the context more easily. On the one that you submitted, it didn't matter because it was easier to cut-and-paste than to run patch anyway.

cvs commit: xml-fop/src/java/org/apache/fop/rtf/rtflib/rtfdoc BorderAttributesConverter.java

vmote 2003/06/27 12:28:17 Modified:src/java/org/apache/fop/rtf/rtflib/rtfdoc BorderAttributesConverter.java Log: style changes only Revision ChangesPath 1.2 +46 -41

RE: [PATCH] fop's resource.xml

Clay Leeds wrote: I'm launching MacCvsX as we speak (I don't run WinCVS ;-p). I just checked and unfortunately, Unified diff is not an option. I thought I Double-check the WinCVS MacCVS page to see if they have a later version. I am actually running a beta version of WinCVS, and seeing no

RE: [RTF] Jfor integration

Bertrand: Checkstyle is complaining about the Apache license header in the jfor files, because of the additional credits to the jfor team near the bottom. Do you mind if I rework that a bit so that the standard header is intact, and then add the additional credits for the jfor team below? That

Re: [PATCH] fop's resource.xml

Victor, On 6/27/2003 12:35 PM, Victor Mote wrote: Double-check the WinCVS MacCVS page to see if they have a later version. I am actually running a beta version of WinCVS, and seeing no known problems. I'm using MacCvsX (which appears to be different from MacCVS ;( ). It took a bit to get it

Re: [RTF] Jfor integration

...Do you mind if I rework that a bit so that the standard header is intact, and then add the additional credits for the jfor team below?... No problem - I didn't know that checkstyle cared for this as well. -Bertrand - To