You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by ke...@apache.org on 2002/07/05 08:33:16 UTC
cvs commit: xml-fop/docs/design embedding.xml
keiron 2002/07/04 23:33:16
Modified: docs/design embedding.xml
Log:
cleaned up notes
Revision Changes Path
1.3 +6 -9 xml-fop/docs/design/embedding.xml
Index: embedding.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/design/embedding.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- embedding.xml 8 Mar 2002 09:53:21 -0000 1.2
+++ embedding.xml 5 Jul 2002 06:33:16 -0000 1.3
@@ -95,19 +95,16 @@
</s2>
<s2 title="Others">
<p>
-render to more than one renderer at once (maybe not from the command line). Two independent
-sources have asked me in the last few weeks if this works. I must say
-that this would be nice, since I could generate a PDF for the archive
+render to more than one renderer at once (maybe not from the command line).
+For example you could generate a PDF for the archive
and the PS for the printer in one run. It would probably be faster than
converting the PDF to PostScript afterwards.
</p>
<p>
-I want to note that several code pieces for resolving URLs and/or
-file locations are scattered all over FOP and Batik. Replacing
-them all with an URIResolver invocation would unify behaviour and
-remove redundancies. I'd also recommend to lift the default
-URIResolver implementation from Saxon, it seems to tolerate the
-usual abuse better than everything else i came across elsewere.
+Several code pieces for resolving URLs and/or
+file locations are scattered all over FOP and Batik. These should
+be replaced with an URIResolver invocation to unify behaviour and
+remove redundancies.
</p>
</s2>
</s1>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org