-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Previously the JSON parser was deliberately designed to choke if it encountered \x00 or \u0000, since those represent the NUL character, which is treated as the terminating character in any string passed from NPP to a plugin or vice versa. However, I have decided that this limitation does not make much sense, because when JsonTools reformats JSON, it represents all control characters using the \u escape (so it is internally consistent and correct to represent NUL as \u0000), and thus most plugin commands will not cause problems when working with JSON that contains \u0000 or \x00. WARNINGS: 1. JsonTools is still incapable of parsing text that contains a literal NUL character (as opposed to the \x00 or \u0000 escape sequences), because when Notepad++ sends the text of a file to a plugin, it truncates that text at the first NUL character. 2. The "Dump JSON string(s) as raw text" plugin command (and any other plugin commands that return the raw text of a JSON string), when used to dump a JSON string that contains \x00 or \u0000 escapes, will instead dump all the raw text in that string *up until the first \x00 or \u0000*, because JsonTools sends Notepad++ a string containing a literal NUL character, which Notepad++ treats as the end of the string.
- Loading branch information
1 parent
7c6ce50
commit f3df446
Showing
8 changed files
with
75 additions
and
68 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.