On Fri, Jul 6, 2018 at 4:46 AM, Andrea Lo Pumo wrote:
> From: Dario Lombardo
>>
>> 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?
>
>
> I mean I do not know the full implications of changing the code as I
Ok, got it. Again, the best chances not to get this lost is to file a bug
on bugzilla.
On Fri, Jul 6, 2018 at 1:47 PM Andrea Lo Pumo wrote:
> *From*: Dario Lombardo
>
>> 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 proce
*From*: Dario Lombardo
> 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?
>
I mean I do not know the full implications of changing the code as I did.
It worked for me because I am just interested in gsm_sms.
On Thu, Jul 5, 2018 at 4:01 PM Andrea Lo Pumo 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
I am using "tshark -T json -V -r file.pcap" and specifically I am looking
for the gsm_sms.sms_text field.
I get this output:
"gsm_sms.sms_text": "Ok per\u00c3\u00b2 non piove"
Instead, using "tshark -V -r file.pcap" I get:
SMS text: Ok però non piove
(There is an accent in the "o" of "però")
T
