Issue with non basic ascii characters
See original GitHub issueThese characters are not displayed once compiled
─┬┌┐─┴└┘│├─┼│┤│█░▒▓
I have been unable to track down where this is happening. It looks like they are replaced with spaces during compilation.
Is it possible to pass in a flag to allow non basic ascii characters?
$ nexe --version
1.1.1
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
How to Fix Non-ASCII Characters in a URL - Sitechecker
When generating a URL, only ASCII symbols are allowed to be used. An example of a non-ASCII character is the Ñ. The URL...
Read more >Non-ASCII Glyphs - TerpConnect
Description Name Glyph Numeric Glyph
no‑break space = non‑breaking space    
inverted exclamation mark ¡ ¡ ¡ ¡
cent sign ¢ ¢ ¢ ¢
Read more >Are there historical problems with non-ASCII identifier ...
Non -ASCII characters are associated with identifiers using non-English words. It is often mandated to only use English language in identifiers ...
Read more >Non-printable characters: Problems and how to overcome them
ABSTRACT. Non printable & special characters in clinical trial data create potential problems in producing quality deliverables. There could be major issues ......
Read more >How to Find Non-ASCII Characters in Text Files in Linux
Non -ASCII characters are those that are not encoded in ASCII, such as Unicode, ... We can use this command to find all...
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

Hmm… interesting. Not sure why this is.
Hi this might be done in lib/bundle.js. I’ll check it out 😃