Status: Untriaged
Owner: ----
New issue 4070 by [email protected]: Wrong dectected and saving
character encoding when opening ISO-8859-1 js files in debugger
https://code.google.com/p/v8/issues/detail?id=4070
Version: Chrome 42.0.2311.90 m
OS: Windows 7
Architecture: x64
What steps will reproduce the problem?
1. Open developer console
2. Go to Sources tab and open a .js file you want to debug. The file must
be encoded using IS0-8859-1
3. If you have "special characters" or accents in your file, they should be
rendered as "?".
4. If the file is mapped to your filesystem and you save it, then it will
be totally messed up and when you open it with your favourite editor or IDE
(or even live, as I was, with the file open both in Chrome debugger and in
Netbeans), the file will be permanently messed up, displaying garbagge
every time an special character should appear.
I'm using Apache as webserver, and it is configured to properly send files
as ISO-Latin-1 (AddDefaultCharset iso-8859-1); also Chrome is interpreting
properly the file, when opened in a browse tab, with that encoding, and
also is in Netbeans.
There should be a way to set the character encoding from the sources,
either file by file or by folder and its descendents.
This bug renders live js editing and saving unreliable if using any
non-English language.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
