Opened 13 years ago

Last modified 13 years ago

#6 new defect

Encoding problems in JSON responses

Reported by: stormi Owned by: nanardon
Priority: major Milestone:
Component: component1 Version:
Keywords: Cc:

Description

it looks like some characters are re-encoded several times which makes them really ugly in madb

Example :

​http://sophie.zarb.org/rpms/162cef2f77e3b7fc5b6c0a9e2240c5fe?json=1

Change History (2)

comment:1 Changed 13 years ago by stormi

  • Priority changed from minor to major
  • Summary changed from Encoding problems in JSON responses (not too problematic) to Encoding problems in JSON responses

Here is another example : ​http://sophie.zarb.org/distrib/Mageia/cauldron/i586/media/core-release/by-pkgid/f9158ccc01d3b7d69dde18905f751977?json=1

  • The description in the spec file is encoded in utf-8, I checked it
  • it shows correctly in sophie
  • in the JSON version of the page, no-ASCII characters are messed up, and I don't know if I can convert them back to the correct version.

Raising priority to major because it happens with an english description (which uses typographical symbols encoded in utf-8). It shows really ugly in mageia-app-db :(

comment:2 Changed 13 years ago by stormi

From my tests, the JSON strings are encoded from latin1 to utf8, but as the strings already are in utf-8, they are double encoded. Encoding back from utf8 to latin1 allows to get the valid utf8 string back.

Note: See TracTickets for help on using tickets.