Skip to main content
Solved

encoding issue when published on server

  • September 10, 2018
  • 6 replies
  • 21 views

boubcher
Contributor
Forum|alt.badge.img+11

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

Best answer by boubcher

 

Hello Guys

 

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

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

6 replies

david_r
Celebrity
  • 8394 replies
  • September 10, 2018

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


danilo_fme
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • 2077 replies
  • September 10, 2018

Hi @boubcher

I agree with @david_r

More information is necessary in this case.

Thanks,

Danilo


boubcher
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • 212 replies
  • Best Answer
  • September 12, 2018

 

Hello Guys

 

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

 


boubcher
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • 212 replies
  • September 12, 2018

 

Hello Guys

 

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

 


david_r
Celebrity
  • 8394 replies
  • September 12, 2018

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
Celebrity
Forum|alt.badge.img+51
  • Celebrity
  • 2077 replies
  • September 12, 2018

 

Hello Guys

 

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

 

 

Hi @boubcher

 

great news!