Wireshark mailing list archives
Re: Wrongly escaped UTF-8 characters in JSON values ( epan/print.c )
From: Dario Lombardo <lomato () gmail com>
Date: Thu, 5 Jul 2018 17:46:42 +0200
On Thu, Jul 5, 2018 at 4:01 PM Andrea Lo Pumo <alopumo () movia biz> wrote:
I do not know the Wireshark code, so I am not submitting a patch. This, however, should work because JSON supports UTF-8 (see again [1]). What do you mean by "I do not know the Wireshark code"? What did you
patch? Do you mean you don't know the submission procedure instead? If that's the point, just file a bug report on bugzilla, with your test case, and the above patch if you care, and wait for someone to take care of it :). Posting the bug report here will speed up the process if someone is interested in patching the code for your case. Hope it helps. Dario.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Wrongly escaped UTF-8 characters in JSON values ( epan/print.c ) Andrea Lo Pumo (Jul 05)
- Re: Wrongly escaped UTF-8 characters in JSON values ( epan/print.c ) Dario Lombardo (Jul 05)
- Re: Wrongly escaped UTF-8 characters in JSON values ( epan/print.c ) Andrea Lo Pumo (Jul 06)
- Re: Wrongly escaped UTF-8 characters in JSON values ( epan/print.c ) Dario Lombardo (Jul 06)
- Re: Wrongly escaped UTF-8 characters in JSON values ( epan/print.c ) Richard Sharpe (Jul 06)