The work-around obviously only works for simple cases. In FOP 0.20.5 there's no chance to do what you suggest. Even with the current development code I doubt this would be so simple. I don't think this is even on the task list.
Theoretically, you could try to create a Batik extension to handle FO elements. You could then write a simple wrapper around the FO snippet to create a full XSL-FO document that could be rendered by FOP's AWT renderer to the Graphics2D interface given by Batik. But this is very adventurous. It's probably better on the long run to somehow support the current development so FOP 1.0 gets into arm's reach. On 02.07.2004 19:38:50 Adam Augusta wrote: > Apparently FOP doesn't support rotating areas. The compliance page > suggests using SVG, but then I'd have to have radically different > transforms for handling block spacing, progression, etc just because an > area was rotated. > > To that end, I was thinking of generating the area in FOP, and somehow > saving that output and giving it to SVG to rotate, which I would in > turn embed in FOP. Has anyone had experience with this or other, > hopefully better, workarounds? Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
