[BATIK-612] [PATCH] CSS character escape sequences not parsed correctly

• Type: Bug
• Status: In Progress
• Resolution: Unresolved
• Affects Version/s: 1.6
• Component/s: CSS
• Labels: PatchAvailable
• Environment: Operating System: other; Platform: Other
• Assignee: Batik Developer's Mailing list
• Reporter: Christian Roth
• Created: 10/Jan/06 03:47
• Updated: 28/Mar/07 05:47

Description

CSS character escape sequences do not seem to parse correctly.

For example, the following ruleset delivers a wrong element name for the selector via SAC:

.Headers\a0 \2b \a0 \28 Complex\29

{ display: inline }

It should be the string "Headers\a0 \2b \a0 \28 Complex\29", but is currently delivered as "Headers
\a0 ", which is wrong according to the CSS21 parsing/tokenization rules. It seems that the parser
chokes on two subsequent character escapes that have been delimited by a single space character.