Unicode characters get messed up
See original GitHub issueFor example d3.js uses some weird unicode characters as variable names: https://github.com/mbostock/d3/blob/91d35b4205d4ef150c61c415b7379404bced7267/d3.js#L1283
Browserify outputs this as
var π = Math.PI, ε = 1e-6, d3_radians = π / 180, d3_degrees = 180 / π;
Which is syntax error.
Terrible practice by d3, but this should not break Browserify.
Issue Analytics
- State:
- Created 10 years ago
- Comments:11
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 >Display Problems - Unicode
Display Problems? If you are unable to read some Unicode characters in your browser, it may be because your system is not properly...
Read more >Unicode characters messed up after linebreak - Stack Overflow
The solution is that when using a text editor to view data, the editor should be set to use a font that contains...
Read more >Common Unicode and UTF-8 issues - HESA
Using Unicode solves this problem of ISO character set incompatibility, since these two characters are assigned different numbers in Unicode. Unicode plays a ......
Read more >Free Unicode Character Detector for Text Messages
With this simple tool, you can instantly identify GSM characters and Unicode symbols in your text messages. Characters in the GSM charset will...
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
In case this helps anyone in the future: on Windows using powershell (posh git/git shell), redirecting browserify’s output with
>
mucks up utf8 characters. Instead, use-o
:browserify [entry files] -o outputfile.js
.Ha!