Repository navigation
Help: non-ASCII punctuation is literal in rules (engine 4.2.7) - #230
Merged
Merged
Conversation
Adds a row to the rule-file token tables in Tokens.md and Pass_Files.md: curly quotes, guillemets, inverted marks and dashes are literal as written, with or without a backslash (VisualText/nlp-engine#467). Before 4.2.7 any of them in a rule file was a syntax error. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Documents VisualText/nlp-engine#758 (closes VisualText/nlp-engine#467).
Merge after the engine v4.2.7 release is published — the row is marked NEW 4.2.7.
Adds one row to the rule-file token tables in
NLP_PP_Stuff/Tokens.mdandNLP_PP_Stuff/Pass_Files.md: curly quotes, guillemets,¿ ¡and dashes are literal as written, with or without a backslash; only ASCII punctuation has a syntax role and needs one. Before 4.2.7, following the existing advice ("Backslash any nonalphanumeric char") with a curly quote still produced a syntax error.🤖 Generated with Claude Code