Chinese and special characters
See original GitHub issueHi all
I was trying to use your module and it’s very convenient and easy to use, but I can’t seem to make it work with special characters such as
作為以下歌曲的投資人,持有該上市歌曲的股票:
or
“
Do you have any idea ?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
The 100 Most Common Chinese Characters
The 100 Most Common Chinese characters: ; 2, 一, yī / yì /yí ; 3, 是, shì ; 4, 不, bù ; 5,...
Read more >Chinese characters - Wikipedia
Chinese characters are logograms developed for the writing of Chinese. ... the Kanas use a special set of simplified forms of Chinese characters, ......
Read more >List of Chinese characters - hanziDB
Pinyin Radical Stroke count
㐀 qiū 一 1.4 5
㐁 tiàn 一 1.5 6
㐂 一 1.5 6
Read more >Chinese Characters List (Top 100) || + Flashcards & Quiz
What are the 10 most common Traditional Chinese characters?
Read more >Chinese symbol: 特, special, unique, particular; distinctive ...
Chinese symbol 特 in calligraphy format and mp3 pinyin pronunciation, English interpretations: special, unique, particular; distinctive, exceptional, ...
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
@neocotic sorry again 😃 I confirm again. It’s important that Maybe you need add
<head> <meta charset="UTF-8"> </head>
in Converter.js line 194let html = <!DOCTYPE html><head> <meta charset="UTF-8"> </head><base href="${options.baseUrl}"
I’m sorry for the incredibly long delay in replying in responding to you but life sometimes gets in the way of OSS development. I thank you for your patience and, although I’m closing this issue out, I hope you’ll be glad to know that I believe this issue has been resolved in with today’s 0.6.0 release with the introduction of UTF-8 support.
If you continue to have this problem, please raise a new ticket with an SVG to reproduce the problem and, where possible, an expected and actual file of the output. I hope you can understand my delay.