The actual displayed error is:
The "font-family" property does not support integer values.
This hints towards Batik trying to parse each of the tokens which constitute the font name independently, instead of taking the whole expression. :-|
According to my tests (from a while ago), having multi-word font names without any delimiters should be the proper way of declaring multiple word fonts (or, at least, handled gracefully) due to a few reasons:
- An example [1] hints towards not surrounding names with delimiters;
- ASV (Adobe SVG Viewer) doesn't support apostrophe (');
- Opera complains if quote (") is used.
Note that BATIK-922 already exists to track issues with vendor-specific properties (such as "-inkscape-font-specification", which are also embedded in the file), which is also somehow related. By surrounding the font family with apostrophes, nothing unexpected happened, though (i.e., the file is parsed without any errors)...
For now, I'm only slightly decreasing importance as this can be somehow easily worked around.
Thanks for the report!
[1] http://www.w3.org/Style/Examples/007/fonts#font-family
Attachment Konsistenz.svg has been added with description: Example drawing to reproduce the error