Details
-
Bug
-
Status: Open
-
Resolution: Unresolved
-
1.7
-
None
-
None
-
Operating System: Windows XP
Platform: PC
Description
The spec says that a comma (,) in attribute u1 or u2 of element <hkern> or <vkern> needs to be specified as a Unicode range (or using g1 and g2), like <hkern u1="T" u2="U+002C" k="100"/>. However, for compatibility with some old SVG viewer, it would be nice if a comma is recognized as literal character if u1 and/or u2 either contain only a comma as the only character (u2=","), or if they start or end with two commas (e.g. u2=",,.,;") – these seem to be unlikely cases for accidental typos.
Both u2="U+002C" and u2="U+2c" is recognized as a comma, but not u2="u+002c". However, the example lex scanner in the appendix of the spec is case-insensitive, so maybe a lowercase u+ should also be recognized for compatibility?
A workaround for authors might be to use u2=",,U+002C" which seems to work on both.