[Bug] Foreign/UTF8 characters are not displayed correctly
See original GitHub issueWhat happened?
Hello,
Some foreign characters in NFT attributes are not displayed properly in the wallet. For example :
Photography
Musée du Louvre
On their side, Mintgarden and Spacescan show them properly
https://mintgarden.io/nfts/nft180hvw9wun06uqke37xkuxs0nvrjm2tfw6vty3hu7ncg22pda8mfquye3tw https://www.spacescan.io/xch/nft/nft180hvw9wun06uqke37xkuxs0nvrjm2tfw6vty3hu7ncg22pda8mfquye3tw
If you send me your xch address, I’ll give you one 👍
Version
1.5.1.dev
What platform are you using?
Linux
What ui mode are you using?
GUI
Relevant log output or stacktrace
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Foreign characters are not displayed correctly
Reason. The most likely cause is that the character set in Microsoft Outlook is not set to send outgoing messages in Unicode (UTF-8)....
Read more >UTF-8 characters not displayed correctly in GUI application
When UTF-8 characters are entered into the OpenEdge traditional GUI UI the characters are not displayed correctly.
Read more >foreign and special characters not displaying - Stack Overflow
foreign and special characters not displaying · Try adding ini_set('default_charset', 'UTF-8'); at the top of the script · It's impossible to say, ...
Read more >Display problems caused by the UTF-8 BOM - W3C
An editor which does not handle the UTF-8 signature correctly displays the bytes that compose that signature according to its own character ......
Read more >CSCuj89450 - UTF-8 special characters not ... - Cisco Bug
Symptom: Using foreign UTF-8 characters such as ö, ä and ü in an EUN can result in those characters not showing up properly...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for uncovering this interesting edge case. Long story short, because the metadata URL response for these arweave URLs returns a 302 redirect status code, a long-standing Electron net.request bug omits the content-type header from the response object. So by default the charset is interpreted as iso-8859-1 (I believe).
I have a workaround fix that works. Longer-term, there will be some upcoming changes that should further change how we fetch metadata.
Yeah, we’ll get it in. Thanks for reporting it!