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.

Sign up for GitHub

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

Jump to bottom

UTF-8/16 string validation #3

Closed
miloyip opened this issue Jun 6, 2014 · 1 comment
Closed

UTF-8/16 string validation #3

miloyip opened this issue Jun 6, 2014 · 1 comment
Labels
enhancement

Comments

@miloyip
Copy link
Collaborator

miloyip commented Jun 6, 2014

From milo...@gmail.com on November 22, 2011 22:40:20

String in JSON are not validated to be UTF-8 or UTF-16. The parser do not detect whether the string contain invalid encoding.

Both YAJL and ultrajspon supports UTF-8 validation. YAJL can turn it on/off, while ultrajson make it mandatory.

Add an parsing option to validate UTF-8/UTF-16.

Original issue: http://code.google.com/p/rapidjson/issues/detail?id=2
@miloyip
Copy link
Collaborator Author

miloyip commented Jun 6, 2014

From milo...@gmail.com on November 24, 2011 09:13:37

The change for this is done now.

Status: Fixed

@miloyip miloyip closed this as completed Jun 6, 2014
@tunage tunage mentioned this issue Nov 3, 2014
Closed
@RSpliet RSpliet mentioned this issue Apr 14, 2015
Closed
@xinthose xinthose mentioned this issue Aug 19, 2015
Closed
@lonelymemo lonelymemo mentioned this issue Sep 2, 2016
Open
@shierei shierei mentioned this issue Mar 31, 2017
Closed
This was referenced May 16, 2017
Closed
Closed
@VikingExplorer VikingExplorer mentioned this issue Mar 29, 2018
Closed
@uscanner uscanner mentioned this issue Apr 26, 2018
Open
@StilesCrisis StilesCrisis mentioned this issue May 11, 2018
Closed
@EnchantedJohn EnchantedJohn mentioned this issue May 15, 2018
Closed
miloyip pushed a commit that referenced this issue Jun 18, 2018
@StilesCrisis
Merge pull request #3 from miloyip/master
1391e42 
Merge back
@lichuan lichuan mentioned this issue Oct 29, 2018
Open
@dnj12345 dnj12345 mentioned this issue Apr 25, 2019
Closed
@amamidela amamidela mentioned this issue Sep 4, 2019
Open
@MishraKhushbu MishraKhushbu mentioned this issue Sep 10, 2019
Open
@hyhtemple hyhtemple mentioned this issue May 28, 2020
Open
This was referenced Jan 13, 2021
Closed
Open
@jin-long jin-long mentioned this issue Sep 22, 2021
Open
GerHobbelt pushed a commit to GerHobbelt/rapidjson that referenced this issue Aug 4, 2024
@chri7325
conan: Remove header only (Tencent#3)
0b74c20 
Using header only actually invalidates all settings. These settings are
useful for executable permissions and line endings.

Issue-number: https://devtopia.esri.com/runtime/devops/issues/694
Signed-off-by: Christian O. Venegas <cvenegas@esri.com>
Reviewed-by: Raghuveer Nanduri <RNanduri@esri.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@miloyip