[BATIK-414] TextNode.getBounds doesn't return correct boundary

• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Affects Version/s: 1.5
• Component/s: GVT Text
• Environment: Operating System: All; Platform: All
• Assignee: Batik Developer's Mailing list
• Reporter: Tonny
• Created: 10/Sep/03 19:47
• Updated: 12/Sep/03 21:25
• Resolved: 16/Nov/04 19:05

Description

GVT TextNode bug

This bug occur on SVGTSpanElement with dx & dy attrib without x & y attrib.
The getBounds() from TextNode doesn't return the correct boundary, the boundary
always
start from 0,0 coord.

Looking at the source the fix could be either in

• Batik Bridge
  when setting the AttributedCharacterIterator on TextElement it calculate the x
  & y attrib for non existent x & y attrib
  or
• Batik GVT
  when processing AttributedCharacterIterator, it calculate the x & y attrib for
  non existent x & y attrib

work around
instead of using gvtTextNode.getBounds(), use gvtTextNode.getOutline().getBounds()