deps: ops v0.7.2, so a scanned-era form says what it says - #7
Merged
Conversation
This was two releases behind on ops, and one of them matters to what a reader sees: a symbolic TrueType font is now read through its own character map rather than through a standard encoding. A font marked symbolic does not promise its codes mean what Latin-1 says they mean. Read the wrong way it extracts as the wrong letters, and that is the ordinary case in forms of the scanned era, where the tick boxes and the rules are glyphs. A document co-edited here was showing those letters to everybody in the session. Nothing else changes: this module's own dependency on reader already pinned v0.6.0, so the denial-of-service fixes in the other release were already reaching it. 100% statement coverage, go vet and -race clean, nine cross-compile targets.
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.
Two releases behind on
ops, and one of them matters to what a reader sees: a symbolic TrueType font is now read through its own character map rather than through a standard encoding.A font marked symbolic does not promise its codes mean what Latin-1 says they mean. Read the wrong way it extracts as the wrong letters — the ordinary case in forms of the scanned era, where the tick boxes and the rules are glyphs. A document co-edited here was showing those letters to everybody in the session.
Nothing else changes: this module's own dependency on
readeralready pinned v0.6.0, so the denial-of-service fixes in the other release were already reaching it.100% statement coverage,
go vetand-raceclean, nine cross-compile targets.