Character encoding not detected when opening / not respected when saving in files added to Workspace (developer tools)
Reported by
pere.pas...@gmail.com,
Mar 18 2016
|
||||||
Issue description
Chrome Version : 49.0.2623.87 m
URLs (if applicable) :
Other browsers tested: doesn't apply
have tested this issue:
Safari: -
Firefox: -
IE: -
What steps will reproduce the problem?
(1) Add js file to workspace, with ISO-8859-1 encoding
(2) Make some changes
(3) Save the file
What is the expected result?
The expected result is the original file with the new added content, without changes to the existing content.
What happens instead?
New content is saved, but the original file encoding is not preserved, thus garbling whatever non-standard ASCII characters the original file could had - accents, opening question marks, and that all.
I'm attaching a triple-screenshot with the file opened without modification, displaying the wrong decoding of accents, the same file with "special" characters added inside the developer tools editor itself, then saved, and then opened in my IDE of choice (Netbeans), which has the project configured as ISO-8859-1 as their encoding for source files, displaying the accents and special characters as totally garbled.
Developer tools workspace should detect (and respect) proper encoding of files and/or have an option for selecting it manually.
,
Mar 18 2016
By the way, I reported this ALMOST a year ago... The problem is I did in the V8 project (https://bugs.chromium.org/p/v8/issues/detail?id=4070) and it went unnoticed... ONE YEAR and this bug persist, plus noone moved it to the proper project issue tracker...
,
Mar 21 2016
,
Jul 1 2016
,
Jul 4 2016
This bug went untouched because it was closed and was requested to create a new bug and file it under devtools (as you did here). I believe we do everything in devtools as UTF8 and if you are using latin1 there is a conflict of multi-byte and single-byte encoding. It would be extremely useful for us if you supplied a sample file for us to test with. We may be able to handle it better, but we'll need a real test case.
,
Jul 25 2016
,
Sep 16 2016
Created testcase (see attached files): - bug-exist.png; - bug-no-exist.png; - model.json; - testcase.txt;
,
Sep 16 2016
For "Comment 7" - fixed: 1) "Settings >> Show advanced settings >> Web content >> Customize fonts >> Encoding" = Unicode (UTF-8); 2) "More tools >> Encoding" = Unicode (UTF-8); W3C recomendation: "Choose UTF-8 for all content and consider converting any content in legacy encodings to UTF-8." - https://www.w3.org/International/questions/qa-choosing-encodings
,
Dec 10 2017
We didn't include this in our plans for the upcoming year. If you think this is important, please re-file with justification. Thanks.
,
Jan 8 2018
For me, Chrome is saving as "Hebrew (Windows)" when the original file is "Unicode (UTF-8) with signature" |
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted