Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to Escape whitespace characters #31

Open
GoogleCodeExporter opened this issue May 19, 2015 · 5 comments
Open

Option to Escape whitespace characters #31

GoogleCodeExporter opened this issue May 19, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

Currently per the JSON standard, carriage returns, line feeds, and tabs are 
escaped inside strings in serialization output.

Have an option to turn this off for more readable output.

EscapeWhitespace





Original issue reported on code.google.com by [email protected] on 5 Nov 2008 at 4:50

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 25 Jan 2009 at 4:45

  • Removed labels: Milestone-Release3.0

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 25 Jan 2009 at 4:47

  • Added labels: Milestron-FutureRelase

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 25 Jan 2009 at 4:48

  • Added labels: Milestone-FutureRelease
  • Removed labels: Milestron-FutureRelase

@GoogleCodeExporter
Copy link
Author

I think this should be a default, but it could be optional I supposed, but 
double
quotes in strings are getting escaped. That is if the string being serialized 
is "My
name is "Gary"." using either '\"' or with verbatim strings @"""" the serialized
string that results is: "My name is \"Gary\".". Let me know if there is an 
existing
work-around (other than using "'").
Thanks.

Original comment by [email protected] on 17 Jun 2009 at 8:16

@GoogleCodeExporter
Copy link
Author

This issue actually pertains to escaping whitespace, not quotes.  There's
not really a workaround for what you are trying to do since that is how
quotes are supposed to be escaped according to the JSON standard.  What are
you expecting to see?

Original comment by [email protected] on 18 Jun 2009 at 2:38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant