On Wednesday 19 September 2001 12:15, Keiron Liddle wrote: > In this case I don't think there is any need for a backward compatible > interface. The thing that I really want is the getWidth method to be > useable when batik1.1 is released. This is a runtime compatibility issue > that I was aware of soon after the change, I just haven't got around to > raising the issue, preoccupied with some other areas. I suppose it could be > useful for this sort of problem to also be made publicly known in a similar > way that the interface changes are known.
In order to properly implement getWidth (which was not the case in the method I were using) - you can have a look at the ImageTranscoder. The ImageTranscoder handles correctly the width and height attributes on the outermost svg element (thoses attributes are in fact not required). > As a side note: > It would be good if the TextPainter system was easily extended so that for > simple text that can be represented in pdf we put the text directly into > the pdf and for more complicated text (effects, overline, underline etc.) > the stroking text painter could handle it. Rather than the current > situation where the stroking text painter can handle everything but makes > large pdf files, the pdf text painter only handles simple text. I will think about that and try to provide a mecanism to control which TextPainter to use in different cases. Thierry. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
