Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Bokka,</p> <p>what exactly are you wanting to <em>do</em>? As far as I'm aware Visual Studio (2005 at least) will just use the local codepage for the operating system you are using. If you're an English speaking that's probably Latin1, ISO-8859-1, Extended-ASCII, whatever. If you have no accented/European characters they're all "pretty much" the same representation.</p> <p>We saw some behaviour at work where Visual Studio 2005 on 64bit operating systems (eg. Vista64) was saving in Unicode (UTF8 with BOM) by default; the commenter above suggests that Visual Studio 2008 behaves the same way.</p> <p>Which brings me back to the question - what do you want to do? Are you considering using web.config <a href="http://msdn.microsoft.com/en-us/library/hy4kkhe0(VS.80).aspx" rel="nofollow noreferrer">globalization section</a>? It has an option to specify fileEncoding as well as the request and response.</p> <pre><code> &lt;system.web&gt; &lt;globalization fileEncoding="iso-8859-1" requestEncoding="utf-8" responseEncoding="utf-8" /&gt; &lt;/system.web&gt; </code></pre> <p>For any particular stream of bytes you receive, it's difficult to "know" what encoding was used (unless it's UTF-8 with BOM, in which case it's easy to check the first few bytes) or it was created on your PC (in which case it uses your default codepage).</p> <p>A long while back I wrote <a href="http://www.conceptdevelopment.net/Localization/NCharDet/" rel="nofollow noreferrer">NCharDet</a> which attempts to determine encodings (mainly for different Asian languages) but I'm not sure this is what you need either (besides which it is a little out-of-date). <strong>MLang</strong> used the be the main 'API' Microsoft provided for stuff like this.</p> <p>Sorry I can't provide an actual answer...</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload