Timeline for How to detect the encoding of a file?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2020 at 16:31 | comment | added | Abdollah | 1k like for "Notepad++ does its best to guess what encoding a file is using". | |
| May 14, 2018 at 3:43 | comment | added | phuclv | as you can never be sure what encoding a file is really using, it can be used for malicious purposes "When the browser isn't told what the character encoding of a text is, it has to guess: and sometimes the guess is wrong. Hackers can manipulate this guess in order to slip XSS past filters and then fool the browser into executing it as active code. A great example of this is the Google UTF-7 exploit" | |
| Aug 30, 2015 at 17:56 | comment | added | bytepusher | "no file in the world" sounds to me like "no-one would ever do that". | |
| Oct 18, 2014 at 18:48 | comment | added | Revious | Floppy Disks became obsolete. Encoding are still all there.. :o | |
| Oct 18, 2014 at 18:47 | comment | added | Revious | Actually I think it's "funny" that the encoding problem still stays in 2014 since no file in the world will begin with "" and I'm very surprised when I see a HTML page which has been loaded with the wrong encoding.. It's a matter of probability. It's unthinkable to choose the wrong encoding if another encoding would avoid strange chars.. Looking for the encoding which avoids strange chars would work in 99,9999% of cases I guess. But still there are errors.. Also it's a very confusing message to use ascii instead of UTF8 to save space.. it's confusing junior developers this idea of perform.. | |
| Dec 8, 2013 at 19:39 | comment | added | Donal Fellows | With experience, alas, metadata (“headers”) can also be wrong. The database holding the information could be corrupted, or the original uploader could have got this wrong. (This has been a significant problem for us in the past few months; some data was uploaded as “UTF-8” except it was “really ISO8859-1, since they're the same really?!” Bah! Scientists should be kept away from origination of metadata; they just get it wrong…) | |
| Feb 15, 2013 at 11:01 | comment | added | vaughandroid | Gah, meant to say "UTF-8" not "UTF-2" in my previous comment. | |
| Feb 15, 2013 at 11:00 | history | edited | vaughandroid | CC BY-SA 3.0 |
added 245 characters in body
|
| Feb 15, 2013 at 10:48 | comment | added | vaughandroid | @MichaelBorgwardt You are definitely right on the the UTF-2. The UCS-2/UTF-16 is a bit less clear. Will update my answer. | |
| Feb 15, 2013 at 10:39 | comment | added | Michael Borgwardt | And if a file started with 0xFF,0xFE it should be auto-detected as UTF-16, not UCS-2. UCS-2 is probably guessed because it contains mainly ASCII characters and thus every other byte is null. | |
| Feb 15, 2013 at 10:36 | comment | added | Michael Borgwardt | Why would a file that starts with a BOM be auto-detected as "UTF-8 without BOM"? | |
| Feb 15, 2013 at 10:34 | comment | added | Jan Doggen | BOMs: msdn.microsoft.com/en-us/library/windows/desktop/… | |
| Feb 15, 2013 at 10:26 | vote | accept | Marcel | ||
| Feb 15, 2013 at 10:16 | history | answered | vaughandroid | CC BY-SA 3.0 |