Closed prmr closed 10 years ago
The messed up accents come from the json data files. When I pull directly from the CR API and encode as UTF-8, I get the correct accents instead. I can send everyone a copy of the data with clean accents, but it might not be worth the trouble of having everyone switch the data files.
Moving this to the next milestone. I'm currently investigating the cause of the product count drop.
Closing the issue since the new data set that was posted by @nishanth1991 on the discussion board encodes accents correctly.
Search for "Sparking Ros" and you should get a category intended to be "Sparkingly Rosé" that's got a messed up acute accent.