Comment #10 on issue 18615 by [email protected]: change "default encoding" by default to UTF-8 in Linux http://code.google.com/p/chromium/issues/detail?id=18615
If you're bi-lingual and use English Chrome, but most of time visits Windows-1251 pages (needless to say, it'd not help if you visit *unlabelled* pages in KOI8-R or iso-8859-5), you can just change the default encoding to windows-1251. That's what the UI for changing the default encoding is for. Setting the default to UTF-8 does NOT help any of your cases. It would help ONLY if both of the following conditions are met: 1) the majority of pages you visit are in UTF-8 2) the majority of them do NOT specify the encoding explicitly. And, if you think the above conditions are met for your case, you can just go ahead and change the default encoding to UTF-8. Nobody can tell you what default encoding to use. It's totally up to you. As for English pages not using non-ASCII characters, that's not true. Even now, some of NYTimes.com does not specify charset explicitly (I wrote them a few times over the last 10 years and they still didn't fix them all) and relies on the fact that the default encoding would be windows-1252. Nonetheless, those non-ASCII characters in English pages are not many, you can live with them being incorrectly displayed from time to time when your default encoding is windows-1251. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
