https://issues.apache.org/bugzilla/show_bug.cgi?id=46055
Summary: Batik CSS Scanner does not handle unicode-range
correctly
Product: Batik
Version: 1.6
Platform: PC
OS/Version: Windows XP
Status: NEW
Keywords: RFC
Severity: normal
Priority: P2
Component: CSS
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
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;
}
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
