Fix path numbers adjacent to exponents#454
Open
Sanjays2402 wants to merge 1 commit into
Open
Conversation
SVG path numbers may be adjacent when the next number starts with a decimal point. Separate completed exponents so the following coordinate is not consumed as part of the exponent. Add an API regression test comparing adjacent and explicitly separated forms. Fixes Kozea#421
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
1 participant
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.
SVG path data can place a decimal-leading number immediately after an exponent (
2e2.0means2e2followed by.0). CairoSVG kept it as one token, consuming the next arc parameter and misrendering or crashing; normalization now inserts the number boundary, with a regression test comparing adjacent and whitespace-separated forms.Fixes #421.