Details
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;
}