https://issues.apache.org/bugzilla/show_bug.cgi?id=44828
--- Comment #3 from Daniel Joyce <[EMAIL PROTECTED]> 2008-04-15 15:44:23 PST --- (In reply to comment #2) > You are correct that quotes shouldn't be required for this font family name > (but can be used to work around the bug). > I don't know alot about the internals of batik, but it seems to try and map everything to a CSS style for internal storage, from a cursory glance at the code base. So it converts the font-family into a @font-face CSS element. In a @font-face element, font-families with spaces in them SHOULD be single quoted So perhaps what is happening, is that batik is barfing on @font-face: Some Font Name With Digits 123 Which technical under w3c should still be okay, as commas are used to seperate multi fonts. But perhaps batik's css compliance is overly strict. And single quoting injects the quotes, so batik is then processing... @font-face: 'Some Font Name With Digits 123' And batik's overly strict CSS impl is then ok with that. -- 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]
