vg/vgsvg: fix font size handling again #513
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#507 apparently did not fix font size handling for all SVG renderers. It did for my machine locally (eog, the file dialogue preview and firefox all render the test outputs correctly), and according to the spec it should.
Please take a look.
I'd like to suggest we submit a proposal to the W3C that the XML spec should be loosened to allow anything that contains paired left and right angle brackets, with the semantic of the text to be "What was intended". This would at a single step fix all XML data processing globally, and bring the spec into line with current usage.
/cc @chmike