Uploaded image for project: 'Batik'
  1. Batik
  2. BATIK-286

Problem with dy on <tspan>

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Resolution: Fixed
    • 1.5
    • None
    • GVT Text
    • None
    • Operating System: other
      Platform: Other

    Description

      The following report shows a situation where the second (and empty)
      tspan dy attribute seems to override the value of the first tspan
      dy.

      From Ivan Hermann's original message:

      Consider the following svg file:

      <?xml version="1.0" encoding="utf-8"?>
      <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1220 880">
      <style type="text/css">
      rect.Background

      {fill: #ffcc99; }

      rect.slideContent

      {fill: white; }

      .blockquote

      {font-size: 38px; }

      </style>
      <rect class="Background" width="1220" height="880"/>
      <g class="slideContent" transform="translate(30 80)">
      <rect class="slideContent" width="1170" height="770" x="-5" y="-5"/>
      <text transform="translate(5)">
      <tspan x="40" dy="60" class="blockquote">Some text</tspan>
      <tspan x="0" dy="10"/>
      </text>
      </g>
      </svg>

      The only unusual feature is that there an 'empty' tspan following the
      other tspan. Foolish it may be but it is correct, I believe.

      The interesting thing is that the positioning of 'Some text' goes
      wrong. If you display it, the text should be fully in the white
      rectangle, but it is not. If

      • I exchange the 'dy=60' to 'y=60', or
      • I delete the empty tspan

      then the positioning is o.k. I guess this is a bug.

      I ran it with 1.5-beta3

      Attachments

        Activity

          People

            batik-dev@xmlgraphics.apache.org Batik Developer's Mailing list
            vincent.hardy@sun.com Vincent Hardy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: