Solved

encoding issue when published on server

  • 10 September 2018
  • 6 replies
  • 1 view
boubcher
Rank
Badge +10

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

icon

Best answer by boubcher 12 September 2018, 10:26

View original

6 replies

david_r
Rank
Userlevel 4

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

danilo_fme
Rank
Userlevel 4
Badge +30

Hi @boubcher

I agree with @david_r

More information is necessary in this case.

Thanks,

Danilo

boubcher
Rank
Badge +10

 

Hello Guys

 

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

 

boubcher
Rank
Badge +10

 

Hello Guys

 

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

 

david_r
Rank
Userlevel 4

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.

danilo_fme
Rank
Userlevel 4
Badge +30

 

Hello Guys

 

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

 

 

Hi @boubcher

 

great news!

 

Reply


Community Stats

28,723
Posts
109,510
Replies
36,559
Members
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.