(cc'ing batik-dev)
If I interpret this correctly, Batik uses the following entry in
XMLResourceDescriptor.properties to instantiate a parser in
SAXDocumentFactory through the SAX XMLReaderFactory:
org.xml.sax.driver = org.apache.xerces.parsers.SAXParser
There's no Xerces-dependency in Java code,
Fop-devs,
In spite of the huffing and puffing, my original implementation of
text-decoration was wrong. Such hubris. Currently being corrected in Defoe.
Peter
We can't do it for you. You have to do it yourself.
Instructions are here:
http://xml.apache.org/fop/dev/index.html#mail-fop-dev
But all you need to do, is send an e-mail here *from the e-mail address
with which you subscribed* (presumably [EMAIL PROTECTED]):
[EMAIL PROTECTED]
On Jan 13, 2005
Title: Message
Please unsubscribe
me from the list
Jeremias Maerki wrote:
I see. I've added JAXP and Xerces to the classpath.
Isn't it somewhat strange that org.apache.xerces.parsers.SAXParser
is explicitely referenced? I'd think everyone uses JAXP meanwhile.
Do you access Xerces specific functionality?
J.Pietschmann
I see. I've added JAXP and Xerces to the classpath. This approach still
allows us to verify that the repackaging process is set up correctly.
Sorry for the trouble. I rarely work with JDK 1.3 and I have Xerces and
Xalan in the endorsed directory for all my JDK 1.4+ VMs.
On 13.01.2005 21:14:25 Simo
On Wed, Jan 12, 2005 at 09:02:37PM +0100, Jeremias Maerki wrote:
> Uhm, the classpath was quite ok like it was. If you look into the
> fop-transcoder-allinone.jar, it contains all classes (or at least should
> contain all classes) that are needed to run the transcoder tests. That
> JAR is for peopl
I'd prefer if you helped working on those things we really need for a 1.0
release. But as long as you don't break 1.0 compatibility I'm -0. So no
real objection.
On 13.01.2005 19:52:40 Glen Mazza wrote:
> Team,
>
> The bookmarks are finished. In doing them, I found
> perhaps about 10 bugs in the
Team,
The bookmarks are finished. In doing them, I found
perhaps about 10 bugs in the 1.1 spec with them
(mostly typos but a few functional ones as well), and
I sent emails to the XSL-Editors list about those.
Next, I'd like to start this weekend looking into
bringing fo:flow-map [1] into our 1.
There seems to have been some discussion about this in the CR phase:
http://www.w3.org/2001/08/28-XSL-PR-DOC.html (see comment 20)
It would seem that in the case of reference-area generating FOs
start-indent should simply be inherited (comment 20, item 3). In my
example the start-indent of the bl
I'm trying to figure out what the indent of the orange block under the
block-container may be, or rather if our current implementation is
really ok. It's clear that for the yellow block start-indent is 10pt.
5.3.2 says for FOs that don't generate a reference area (ex. fo:block)
the following is tr
11 matches
Mail list logo