Re: PostScript Renderer in redesign (was: strokeSVGText in Postscript format)
You're totally right. That was the stuff I've been talking about. The Transcoder is for Batik so it can convert SVG to PDF or PostScript without the XSL_FO-specific FOP renderers. You can just leave these out, but you're also welcome to help with these. :-) On 30.01.2003 22:48:14 George Yi wrote: > The PDFTranscoder is not referenced in current FOP source yet. Is it used by > Batik? > To my understanding, PSTranscoder has not adapted into Batik, am I right? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: PostScript Renderer in redesign (was: strokeSVGText in Postscriptformat)
Jeremias, The PDFTranscoder is not referenced in current FOP source yet. Is it used by Batik? To my understanding, PSTranscoder has not adapted into Batik, am I right? -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: Re: PostScript Renderer in redesign (was: strokeSVGText in Postscript format) Ok, as promised the PS renderer is setup as far as SVG output is possible. I haven't gotten through to the Batik transcoder, yet, but that's not necessary right now, anyway. I'm still pretty confident that we will be able to use the code from the redesign in the maintenance branch with relatively little work if that's necessary. I've introduced a new class: PSGenerator. This class is the central point where PostScript code is channeled through to the OutputStream. That means that PSRenderer writes to PSGenerator and PSGraphics2D also writes to PSGenerator. IMO PSGraphics2D should not call any methods on PSRenderer. Commands used both in PSRenderer (for XSL-FO) and PSGraphics2D (for SVG) should be implemented in PSGenerator. An example here are saveGraphicsState() and restoreGraphicsState(). I hope that'll get you started. If you have any questions fire away. I'll be glad to help. But I must say that I will be mostly away tomorrow and next week from Monday to Friday. On 23.01.2003 20:40:18 Jeremias Maerki wrote: > Deal. I'll start setting up the basic infrastructure for it tomorrow. I > hope we can get you started on this real fast. :-) > > On 23.01.2003 20:29:22 George Yi wrote: > > Sounds attractive to me. I don't know how much dedication I can put into > > this. My paid job has absolute No.1 priority. But if some committer take a > > lead, I am certainly willing to help to implement some features. > > Anyway, help me setup first. I can always learn something:-) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: PostScript Renderer in redesign (was: strokeSVGText in Postscriptformat)
Great. I will try to look at where my changes should be in your new design first. So far my changes are against 0.20.5rc. These changes are QUADTO implementation, correct color display and simple text embedding. I haven't worked out AttributedString embedding yet. I will get the snapshot again tonight, and work from there. George. -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 11:46 AM To: [EMAIL PROTECTED] Subject: Re: PostScript Renderer in redesign (was: strokeSVGText in Postscript format) Ok, as promised the PS renderer is setup as far as SVG output is possible. I haven't gotten through to the Batik transcoder, yet, but that's not necessary right now, anyway. I'm still pretty confident that we will be able to use the code from the redesign in the maintenance branch with relatively little work if that's necessary. I've introduced a new class: PSGenerator. This class is the central point where PostScript code is channeled through to the OutputStream. That means that PSRenderer writes to PSGenerator and PSGraphics2D also writes to PSGenerator. IMO PSGraphics2D should not call any methods on PSRenderer. Commands used both in PSRenderer (for XSL-FO) and PSGraphics2D (for SVG) should be implemented in PSGenerator. An example here are saveGraphicsState() and restoreGraphicsState(). I hope that'll get you started. If you have any questions fire away. I'll be glad to help. But I must say that I will be mostly away tomorrow and next week from Monday to Friday. On 23.01.2003 20:40:18 Jeremias Maerki wrote: > Deal. I'll start setting up the basic infrastructure for it tomorrow. I > hope we can get you started on this real fast. :-) > > On 23.01.2003 20:29:22 George Yi wrote: > > Sounds attractive to me. I don't know how much dedication I can put into > > this. My paid job has absolute No.1 priority. But if some committer take a > > lead, I am certainly willing to help to implement some features. > > Anyway, help me setup first. I can always learn something:-) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PostScript Renderer in redesign (was: strokeSVGText in Postscript format)
Ok, as promised the PS renderer is setup as far as SVG output is possible. I haven't gotten through to the Batik transcoder, yet, but that's not necessary right now, anyway. I'm still pretty confident that we will be able to use the code from the redesign in the maintenance branch with relatively little work if that's necessary. I've introduced a new class: PSGenerator. This class is the central point where PostScript code is channeled through to the OutputStream. That means that PSRenderer writes to PSGenerator and PSGraphics2D also writes to PSGenerator. IMO PSGraphics2D should not call any methods on PSRenderer. Commands used both in PSRenderer (for XSL-FO) and PSGraphics2D (for SVG) should be implemented in PSGenerator. An example here are saveGraphicsState() and restoreGraphicsState(). I hope that'll get you started. If you have any questions fire away. I'll be glad to help. But I must say that I will be mostly away tomorrow and next week from Monday to Friday. On 23.01.2003 20:40:18 Jeremias Maerki wrote: > Deal. I'll start setting up the basic infrastructure for it tomorrow. I > hope we can get you started on this real fast. :-) > > On 23.01.2003 20:29:22 George Yi wrote: > > Sounds attractive to me. I don't know how much dedication I can put into > > this. My paid job has absolute No.1 priority. But if some committer take a > > lead, I am certainly willing to help to implement some features. > > Anyway, help me setup first. I can always learn something:-) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: PostScript Renderer
Yeah, I was pretty impressed myself. Concept to realization, for complete SVG->PS renderer, in 45 minutes. :-) Now THAT is extreme programming! Regards, Arved Sandstrom Quoting Art Welch <[EMAIL PROTECTED]>: > Wow, that was fast. I was thinking that if I ever get to JDK 1.2+ I would > try to get the PCLRenderer working with Batik. I had been thinking that > this > would be a bit of a project. I guess it should not be that bad... > especially > since I can cheat and look at what you did for PS. > > Art > > -Original Message- > From: Keiron Liddle [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 22, 2001 10:48 AM > To: [EMAIL PROTECTED] > Subject: Re: PostScript Renderer > > > > On Fri, 22 Jun 2001 10:03:22 Keiron Liddle wrote: > > > > I might also have a look at the svg rendering. > > > > I have added an svg renderer for the postscript. > > This is unfinished since as I haven't bothered to work out a replacement > for the quad-to command (which means text won't work) and I haven't checked > images. > The other stuff should work ok. > > So if anyone knows a replacement for quad-to > > If the ps code was separated out then it would be a short step to creating > an svg -> ps transcoder for batik. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --- This mail was sent through the Nova Scotia Provincial Server, with technical resources provided by Chebucto Community Net. http://nsaccess.ns.ca/mail/ http://www.chebucto.ns.ca/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: PostScript Renderer
Wow, that was fast. I was thinking that if I ever get to JDK 1.2+ I would try to get the PCLRenderer working with Batik. I had been thinking that this would be a bit of a project. I guess it should not be that bad... especially since I can cheat and look at what you did for PS. Art -Original Message- From: Keiron Liddle [mailto:[EMAIL PROTECTED]] Sent: Friday, June 22, 2001 10:48 AM To: [EMAIL PROTECTED] Subject: Re: PostScript Renderer On Fri, 22 Jun 2001 10:03:22 Keiron Liddle wrote: > > I might also have a look at the svg rendering. > I have added an svg renderer for the postscript. This is unfinished since as I haven't bothered to work out a replacement for the quad-to command (which means text won't work) and I haven't checked images. The other stuff should work ok. So if anyone knows a replacement for quad-to If the ps code was separated out then it would be a short step to creating an svg -> ps transcoder for batik. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PostScript Renderer
On Fri, 22 Jun 2001 10:03:22 Keiron Liddle wrote: > > I might also have a look at the svg rendering. > I have added an svg renderer for the postscript. This is unfinished since as I haven't bothered to work out a replacement for the quad-to command (which means text won't work) and I haven't checked images. The other stuff should work ok. So if anyone knows a replacement for quad-to If the ps code was separated out then it would be a short step to creating an svg -> ps transcoder for batik. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PostScript Renderer
The Prostscript renderer is committed and working, at least for simple examples. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PostScript Renderer
I'll commit this for you. Thanks for the good work. I might also have a look at the svg rendering. On Thu, 21 Jun 2001 22:38:50 Jeremias Maerki wrote: > Hi all > > As promised I'm posting the PostScript renderer I started in March. I > adapted it to the current CVS version. I've run a few tests to make sure > I don't break anything. Hopefully I don't... > > As stated before, the renderer is far from being finished. For those who > want to improve it or want to know what the current problems are, please > consult the comments in PSRenderer.java. They list a few known bugs and > what still needs to be done. I also included some guidelines I'd like to > see being followed (especially DSC stuff). > > The ZIP contains the new package org.apache.fop.render.ps. The diff > "CmdLine.diff" contains the new Command Line Options for the new > PSRenderer. > > The second diff is a little goodie and fixes the problem with page > numbering with multiple page sequences which came up when the "static" > prefix was removed from runningPageNumberCounter. > > Thanks, Arved, for your encouragement to submit the code. I'd love to > see people helping me with the PostScript renderer, especially because > it's a little low on my priority list (I haven't touched the code for 2 > months now) and because I don't have so much free time. Isn't that > everybody's problem? :-) > > Tony, please don't be too disappointed if it doesn't fit your needs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
