how to resolve the encode problem?
See original GitHub issuei got a xml file include some chinese characters, when i use the XLSX.write api, the chinese characters changed.
here is my code
workbook is a xml string
var workbook = XLSX.read(content, {type: 'binary'});
workbook.Sheets[‘ag-grid’][‘A24’].v
the cell value became this, the oringin value is ‘中文测试’,apologize for my bed english,.
Issue Analytics
- State:
- Created 6 years ago
- Comments:21 (9 by maintainers)
Top Results From Across the Web
How to solve unicode encoding issues - Invivoo
In ths new article, our expert will explain you how to solve unicode encoding issues. If you have any question, don't hesite to...
Read more >Solving character encoding problems - jAlbum Wiki
The easiest workaround is to stay away from using foreign characters in file and folder names, but if you want to use them,...
Read more >How to Fix OBS “Encoding Overloaded” Issue [2022] - Movavi
Choose the right settings in OBS · Reduce your output resolution · Lower frame rate · Change the encoder preset · Try hardware...
Read more >How to fix character encoding issue in html? - Stack Overflow
1 Answer 1 · On Notepad++ select Encoding -> UTF-8 (without BOM) and save the file. · Use <meta http-equiv="Content-Type" content="text/html; ...
Read more >How to fix: Invalid UTF-8 encoding - Google Support
Use proper UTF-8 encoding for text and avoid double encodingMerchant Center supports UTF-8, UTF-16, Latin-1, and ASCII. If you're unsure of your file's ......
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 FreeTop 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
Top GitHub Comments
A small local change seemed to have fixed the immediate problem but we need to do some more tests to be sure. Expect a release tomorrow or Friday
This is very strange. I will raise a new issue