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

Batik CSS Scanner does not handle unicode-range correctly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 1.6
    • Fix Version/s: None
    • Component/s: CSS
    • Labels:
    • Environment:
      Operating System: Windows XP
      Platform: PC

      Description

      Batik's org.apache.batik.css.parser.Scanner class's nextToken() method has a section to handle when a "U" character is followed by a "+" character, as is typically the case for unicode character ranges specified in CSS-2 style @font-face rules.

      For example, a simple unicode range might look like this:

      @font-face {
      src:url("myfont.ttf");
      unicode-range: U+0030-U+0039;
      }

      However, there can be multiple entries in the ranges separated by a comma, and each entry can be just a single character, or include wild cards too. It seems the Batik CSS Scanner does not take these multiple entries into consideration.

      @font-face {
      src:url("myfont.ttf");
      unicode-range: U+0030-U+0039,U+002E;
      }

        Attachments

        1. bug46055.patch
          6 kB
          Peter Farland

          Activity

            People

            • Assignee:
              batik-dev@xmlgraphics.apache.org Batik Developer's Mailing list
              Reporter:
              pfarland@adobe.com Peter Farland
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: