Skip to main content
  • EN

we have WS running with no encoding issue on the desktop, when published on the server and used as API we are getting a result with encoding issue

we did add an ecoder into the WS , but it didnt solve the problem

Any idea, please

What's the data source here? The more details, the better.

Hi @boubcher

I agree with @david_r

More information is necessary in this case.

Thanks,

Danilo

 

Hello Guys

 

Thanks for your replay we fixe problem by setting the encoding parameter into the writer

 

 

Hello Guys

 

Thanks for your replay we fixe problem by setting the encoding parameter into the writer

 

Great to hear that you found the solution, it's always a good idea to explicitely specify the encoding and utf-8 is the one to use for JSON.

Just a heads-up: you should not include the byte-order marker (BOM) when writing JSON, some applications may not like it as it's forbidden by the json standard:

Implementations MUST NOT add a byte order mark to the beginning of a JSON text.

 

Hello Guys

 

Thanks for your replay we fixe problem by setting the encoding parameter into the writer

 

 

Hi @boubcher

 

great news!

 

Reply


Community Stats

31,821
Posts
120,861
Replies
39,452
Members

Latest FME

Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.