You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Some EU reports are reporting Cp1252 charset in the download headers and not being correctly
// parsed by PHP. In those cases, replacing the encoding value with ISO-8859-1 allows PHP to
// correctly detect and convert the document to UTF-8
But that doesn't seem to be correct, at least with the reports I'm getting. For example, one of my SKU's titles in the Amazon.de marketplace contains „ and “ characters. In a JSON encoding of the result from Document::download, these are encoded as \u0084 and \u0093 respectively, which are control codes, instead of \u201e and \u201c, which are the correct punctuation mark codepoints.
Do you have more info on what led to this encoding switch being made? I'm wondering if it was the titles themselves on someone's report that were incorrectly encoded, not the report itself.
The text was updated successfully, but these errors were encountered:
Hi,
In lib/Document.php there is this note:
But that doesn't seem to be correct, at least with the reports I'm getting. For example, one of my SKU's titles in the Amazon.de marketplace contains „ and “ characters. In a JSON encoding of the result from Document::download, these are encoded as \u0084 and \u0093 respectively, which are control codes, instead of \u201e and \u201c, which are the correct punctuation mark codepoints.
Do you have more info on what led to this encoding switch being made? I'm wondering if it was the titles themselves on someone's report that were incorrectly encoded, not the report itself.
The text was updated successfully, but these errors were encountered: