view_href encoding
Hi, We are using the following API v2 call in a browser: https://community.blah.com/ejquo23388/api/2.0/search?q=SELECT+board.id%2C+conversation.id%2C+conversation.solved%2C+conversation.view_hr...
Forum Discussion
It's actually a question of how your browser implements support for UTF-8 characters
Are you using chrome? Can you give it a shot with opera?
Here is the related idea
https://community.lithium.com/t5/Product-Ideas/URL-without-accented-character/idi-p/71908
Hey VikasB,
Thanks for the reply. It is not really a 'browser' issue, but how the view_href is encoded in the JSON response. For grins I downloaded and opened the API call with opera and it has the same issue. I didn't know if there was an expression we could use at the end of an API call to say 'Use UTF-8', or make it pretty. Not sure why 'subject' is not encoded, but URL is when the API call is returned. As you say the browser should be able to interpret the characters and do what it needs to do, so am not clear why the JSON view_href is encoded? I'm sure there is a reason, but didn't know if other people had this issue and if they managed to solve it by adding an attribute to the API call ;)
Thanks,
Tim
