Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Okay, let's elaborate. Both <a href="https://stackoverflow.com/questions/138449/how-to-convert-a-unicode-character-to-its-extended-ascii-equivalent#138579">csgero</a> and <a href="https://stackoverflow.com/questions/138449/how-to-convert-a-unicode-character-to-its-extended-ascii-equivalent#138583">bzlm</a> pointed in the right direction.</p> <p>Because of blzm's reply I looked up the Windows-1252 page on wiki and found that it's called a codepage. The wikipedia article for <a href="http://en.wikipedia.org/wiki/Codepage" rel="nofollow noreferrer">Code page</a> which stated the following: </p> <blockquote> <p>No formal standard existed for these ‘<a href="http://en.wikipedia.org/wiki/Extended_ASCII" rel="nofollow noreferrer">extended character sets</a>’; IBM merely referred to the variants as code pages, as it had always done for variants of EBCDIC encodings.</p> </blockquote> <p>This led me to codepage 437:</p> <blockquote> <p>n ASCII-compatible code pages, the lower 128 characters maintained their standard US-ASCII values, and different pages (or sets of characters) could be made available in the upper 128 characters. DOS computers built for the North American market, for example, used <a href="http://en.wikipedia.org/wiki/Code_page_437" rel="nofollow noreferrer">code page 437</a>, which included accented characters needed for French, German, and a few other European languages, as well as some graphical line-drawing characters.</p> </blockquote> <p>So, codepage 437 was the codepage I was calling 'extended ASCII', it had the ê as character 136 so I looked up some other chars as well and they seem right.</p> <p>csgero came with the Encoding.GetEncoding() hint, I used it to create the following statement which solves my problem:</p> <pre><code>byte[] bytes = Encoding.GetEncoding(437).GetBytes("ê"); </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

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