You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Japollack, yes, this was an intentional design decision on my part. That said, I agree that it can make JSON with lots of non-ASCII characters less readable. I'm working on this right now and should have a patch finished in a couple of hours.
ADDED
1. Support for extended ASCII characters
(i.e., anything from `0x7f` (⌂) to `0xff` (ÿ))
in random JSON.
CHANGED
1. Non-ASCII characters (e.g., 😀, Я) are now
displayed normally rather than being converted to
ASCII using the `\u` notation (e.g., `\ud83d\ude00`, `\u042f`).
Resolve Issue #25.
FIXED
1. Fix bug where find/replace form advanced controls
would not be toggled if the user manually
resized the form.
"Pretty-print current JSON file" command would turn this:
{ "cities": [ "Tallinn", "Pärnu", "Tartu", "Valga", "Jõhvi", "Haapsalu", "Jõgeva", "Võru" ] }
into this:
{ "cities": [ "Tallinn", "P\u00e4rnu", "Tartu", "Valga", "J\u00f5hvi", "Haapsalu", "J\u00f5geva", "V\u00f5ru" ] }
Using Json Tools v4.6.1 with Notepad++ v8.4.7.
The JSON file is saved as UTF-8 BOM with Windows line endings.
Remove the .log from the file name: nppJsonToolUmlautaSample.json.log
PS. Probably the issue lies here:
JsonToolsNppPlugin/JsonToolsNppPlugin/JSONTools/JNode.cs
Line 271 in 6519711
The text was updated successfully, but these errors were encountered: