Issue 18355

Species API not displayed in UTF-8

18355
Reporter: peterdesmet
Assignee: mblissett
Type: Feedback
Summary: Species API not displayed in UTF-8
Status: Open
Created: 2016-03-31 12:55:37.713
Updated: 2016-04-21 12:30:38.862
        
        
Description: The output of http://api.gbif.org/v1/species/105758006 does not correctly display certain characters. E.g. in {{publishedIn}} we have (see screenshot):

bq. Bulletin de la Société Impériale des naturalistes de Moscou

That information is apparently correctly in the source dataset, e.g. in the verbatim view for this species the characters are shown correctly: http://www.gbif.org/species/105758006/verbatim]]>
    

Attachment api.gbif.org v1 species 105758006.png



Author: mblissett
Created: 2016-03-31 13:41:03.137
Updated: 2016-03-31 13:41:03.137
        
The data is in UTF-8, but the webserver doesn't say this.  Depending on the configuration of your web browser, when presented with data without an encoding, it may assume ISO-8859-1, UTF-8 or something else.

It should be straightforward for us to add the UTF-8 statement to the HTTP header.
    


Author: mdoering@gbif.org
Comment: in POR-2010 we looked at that before. As JSON requires unicode and defaults to UTF8 we decided not to take any action. But maybe we should to avoid confusion, its not hurting.
Created: 2016-04-04 11:42:44.229
Updated: 2016-04-04 11:42:44.229