title: HEX-edit UTF-8 file
body: <p>I am trying to create a UTF-8/no-BOM file with a HEX-Editor. My desired UTF character is the TUGRIK SIGN, which is <code>e2 82 ae</code> in UTF-8.</p>
  
  <p>I created an <strong>UTF-8/no BOM file</strong> with N++, copied the character in N++ and saved the file.
  Voilà, looks fine in the HEX-Editor, fancy <code>e2 82 ae</code> !</p>
  
  <p>So I tried it the other way arround, saving the 3 bytes <code>e2 82 ae</code> to a file with wxHexEdtior. Crap, N++ thinks for some reason that the file is <strong>ANSI(Latin1)</strong> encoded.</p>
  
  <p>I don't get it at all. 
  Might there be a collision with the windows -CP1252- encoding?</p>
  
  <p>Another interesting thing (which I also don't get at all), is that wxHexEditor shows some disassembly for the files.</p>
  
  <p>The disassembly for the N++ created file is okay for wxHexEditor, but the wxHexEditor created file has invalid disassembly.</p>
  
  <p>I would be really glad if someone could explan that black magic to me.</p>
  
  <p><img src="https://i.stack.imgur.com/V74ys.jpg" alt="Image 1"></p>
  
  <p><img src="https://i.stack.imgur.com/zj0hj.jpg" alt="Image 2"></p>