I've added a Wiki page dedicated to our transcoders:
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPBatikTranscoders
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
+1, but PDF transcoder only for the moment and only a release candidate
first.
Let's put together a checklist of things to do for the release:
- Tag CVS
- Check and update documentation (I've recently added an example to the
embedding examples I ported from the maintenance branch. Need to
docu
As there is likely to be a batik beta release sometime soon what does everyone
feel about having at least a PDF transcoder release.
A PS transcoder would be good if it is working okay (I have no PS viewer at the
moment).
Doing a release doesn't really depend on batik from our end. So if we can
Hi Keiron
On 06.03.2003 00:45:01 Keiron Liddle wrote:
> > > There are some minor bugs with patterns in patterns, drawing images and
> fonts
> > > but there won't be any fixes soon.
> >
> > Wouldn't it make sense to work with the Batik team to get the
Hi Jeremias,
> You mean Batik will have pdf-transcoder.jar and ps-transcoder.jar in
> their distributions? Not the source, right?
That is correct.
> What about factoring out the code for the transcoders and supporting
> classes (like fonts) into a separate container/subproject a
s? Not the source, right?
What about factoring out the code for the transcoders and supporting
classes (like fonts) into a separate container/subproject accessible by
both the FOP and Batik teams? XML-Commons, maybe? That way we could
encourage the Batik guys to participate in the future developm
Hi All,
The PDF transcoder could be packaged with Batik so that it can be used by users
of Batik only and also used independanlty from the rest of FOP.
So will there be any problems. There is the pdf-transcoder build target that
creates the transcoder jar. We could create a tag for the release
