Keiron wrote:
> try using:
> addTranscodingHint
>
> you are removing transocding hints with the setTranscodingHints.
Actually, that's not the case. Notice that I'm calling
"public void setTranscodingHints(Map hints)" and NOT
"public void setTranscodingHints(TranscodingHints hints)".
The first does "this.hints.putAll(hints);" (i.e. "add"),
the second one does "this.hints = hints;" (i.e. replace).
The JavaDoc for these two methods is a litte confusing
by the way. I had to look at the code to figure this out.
Keiron wrote:
> The hint has a StringKey as the key and a Boolean as the value.
Hmm. Then why do I get this exception:
java.lang.IllegalArgumentException: false incompatible with
[EMAIL PROTECTED]
at org.apache.batik.transcoder.TranscodingHints.put(Unknown Source)
at org.apache.batik.transcoder.TranscodingHints.putAll(Unknown
Source)
at
org.apache.batik.transcoder.TranscoderSupport.setTranscodingHints(Unknown
Source)
[snip]
...when I try this:
Map hints = new HashMap();
hints.put(PDFTranscoder.KEY_STROKE_TEXT, Boolean.FALSE);
pdfTranscoder.setTranscodingHints(hints);
...and this exception:
java.lang.ClassCastException: java.lang.String
at
org.apache.fop.svg.PDFTranscoder.transcode(PDFTranscoder.java:174)
at
org.apache.batik.transcoder.XMLAbstractTranscoder.transcode(Unknown Source)
...when I try this:
Map hints = new HashMap();
hints.put(PDFTranscoder.KEY_STROKE_TEXT, "false");
pdfTranscoder.setTranscodingHints(hints);
Keiron wrote:
> > 1) There seem to be two ways to configure text stroking.
> > What's the difference and which is the preferred way?
>
> One is for FOP, ie converting fo to pdf.
> The other is for batik, converting svg to pdf.
> The configuration and other things are not related.
Ok, so I guess [1] is for FOP and [2] is for Batik.
[1] org.apache.fop.configuration.Configuration.put("strokeSVGText",
Boolean.FALSE);
[2] transcodingHints.put(PDFTranscoder.KEY_STROKE_TEXT, Boolean.FALSE);
Keiron wrote:
> > 2) In the mailing list archive I've read that there are
> > limitations when not stroking text in FOP.
> > What exactly are these limitations?
>
> This would probably be the following:
> - if there is a font or character substitution then it won't work
> properly
> - it may ignore things like tspan x and y changes or colourings
Ok, thanks.
Regards,
Thomas
************************************
If this email is not intended for you, or you are not responsible for
the delivery of this message to the addressee, please note that this
message may contain ITT Privileged/Proprietary Information. In such
a case, you may not copy or deliver this message to anyone. You should
destroy this message and kindly notify the sender by reply email.
Information contained in this message that does not relate to the
business of ITT is neither endorsed by nor attributable to ITT.
************************************
