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
Could Json::encode()
allow JSON_INVALID_UTF8_SUBSTITUTE
#274
Comments
I recently ran into this issue where JSON_INVALID_UTF8_SUBSTITUTE is silently ignored. That's 30 minutes of my life im never getting back! So, i just updated all the calls to: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User data can include invalid characters, e.g. "\xF6" which is an
ö
in ISO-8859-1, but invalid for UTF-8.Invalid characters can be replaced with a
"?"
, by usingmb_convert_encoding($string, 'UTF-8', 'UTF-8')
; but this needs to be done on every individual string (tricky with large arrays), andmbstring
is a non-default extension (so not always available).Would it be possible to use the
JSON_INVALID_UTF8_SUBSTITUTE
flag to json_encode(), so invalid characters can be replaced with \0xfffd (i.e.�
), and a usable value is returned (rather than getting an exception).The text was updated successfully, but these errors were encountered: