Text in Japanese garbled

[wolfman0719]

This is a great tool.
So I would like to use it, however it looks like not suppporting Japanese.
All Japanese are shown ???.
This is the typical symptom of not being trasnlated properly from unicode to other encoding
Looking at the content-type of the output , I've found that the content-type is application/json; charset=RAW.
I assume if I can set it to charset=UTF-8 instead of RAW, the issue will probably be resolved.
Is there a way to set it up to UTF-8?

[wolfman0719]

After I directly changed the line in Form.REST.Abstract.cls

Parameter CHARSET = "utf-8";

I can show Japanese properly.

However this solution seems a little uncool to me.

[isc-afuentes]

I remember at some point Form.REST.Abstract had CHARSET="utf-8" and CONVERTINPUTSTREAM="1". Have a look at this commit.
Probably @eduard93 had to made that change for a reason.

@wolfman0719 you can also create a pull request including your changes and maybe some UnitTests containing Japanese characters.
You can find instructions on running the UnitTests on README.md.

I'll try to have a look at this project again as soon as I can.

[eduard93]

How does your HTTP request looks like?

Do you send UTF8 header?

Generally, broker can work without UT8 param, if requests sent to broke include:

content-type application/json charset=utf-8

@wolfman0719

[eduard93]

These 2 commits are relevant:

1bbd766#diff-ae34c1f3723bb416483811f5382167b70577eb3aa5f979b3cf053fe730aee684
832e849#diff-ae34c1f3723bb416483811f5382167b70577eb3aa5f979b3cf053fe730aee684

[wolfman0719]

Yes, the Header has content-type application/json charset=utf-8

[eduard93]

And still garbled text? In object or SQL mode? Both?

[wolfman0719]

I am not sure what object or SQL mode means here, but I added mode=1 to the url.
still garbled
attached the screenshot