Reputation
3,695
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
15 33
Newest
 Nice Answer
Impact
~29k people reached

Feb
3
comment Unstable command line startup time
Are you using a network license server? That could introduce variability.
Oct
1
comment How to prevent ExportString from reencoding diacritics when exporting as JSON
You could also do a FilePrint on the Exported file; it will show identical results to ExportString.
Oct
1
comment How to prevent ExportString from reencoding diacritics when exporting as JSON
The workarounds are solving a slightly different problem, which is how to decode the UTF-8 they get from producing JSON output. In a similar vein you might as well ask "why is the output from ExportString[expr, "PNG"] not showing me a picture?" The answer is because the string you get back actually stores the binary for the PNG, which requires decoding from something that understand the PNG serialization format to render the image.
Oct
1
comment How to prevent ExportString from reencoding diacritics when exporting as JSON
If you state the problem as "how do I decode the UTF-8 encoding of a JSON string", then this is the right solution. But ExportString[expr, "JSON"] by itself is doing what it's supposed to, including the encoding into UTF-8.
Oct
1
comment How to prevent ExportString from reencoding diacritics when exporting as JSON
This is not a bug, it's expected behavior. The output of ExportString is simply the same thing after running through UTF-8 encoding: Try ToString["Conexión", CharacterEncoding -> "UTF8"]. If you FilePrint what Export shows, you'll see the same thing that ExportString is giving. If you provide the output of ExportString[expr,JSON] to a file and use it in a web page, you'll see the right stuff.
Oct
1
comment How to prevent ExportString from reencoding diacritics when exporting as JSON
After you Export to JSON, try doing BinaryReadList on the file and comparing the bytes you see with ToCharacterCode on the string coming back from ExportString. Except for a possible difference in newlines, they should be identical. The reason Import of the Exported JSON string "works" is that it is converting back from UTF-8. @Szabolcs articulate answer explains what is happening and why it is correct behavior. In this case, what you get from ExportString is essentially a string representing a byte sequence, so what you see looks "messed up", as it shows the bare UTF-8 representation.
Jul
24
awarded  Nice Answer
Jul
22
awarded  Notable Question
May
8
awarded  Nice Question
Feb
24
awarded  Yearling
Nov
30
awarded  Nice Answer
Aug
22
awarded  Popular Question
Aug
18
comment Deploying to the Cloud for Public Access
It was a bug that "read" and/or login was required. All -> "Execute" should allow anyone to access the form without requiring a login.
Aug
18
answered Deploying to the Cloud for Public Access
Aug
12
comment Deploying to the Cloud for Public Access
The intention is that Permissions->"Public" for CloudDeploy of APIFunction, FormFunction, or Delayed means to set Execute only. Execute lets you run the code, read would let you peek at the source. Setting Permissions->"Public" for other kinds of objects typically means "read".
Jul
2
awarded  Curious
May
22
awarded  Enlightened
May
22
awarded  Nice Answer
Feb
24
awarded  Yearling
Dec
13
awarded  Nice Question