Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think the fundamental problem here is your expectations. </p> <p>If I understand you correctly, you expect to be able to change <code>Á</code> to <code>Ã</code> by changing character encodings. That cannot happen. Those are different characters; i.e. different code points - <code>Á</code> is Unicode codepoint 00C1 (or C1 in ISO-8859-1) and <code>Ã</code> is 00C3 / C3.</p> <p>So when you transcode a <code>Á</code> in ISO-8859-1 to Unicode to UTF-8 you <em>should</em> get exactly the same character <code>Á</code>. If you don't then the translation would be broken.</p> <p><sup>You also expect <code>MÉXICO</code> to translate to <code>MÉXICO</code> ... which seems totally bizarre to me. Perhaps there's a problem in your transcription of the characters into the Question ...</sup></p> <p>Now if the lexicography rules for your language / region say that <code>Á</code> to <code>Ã</code> are actually equivalent, then it would be reasonable to "normalize" to a preferred form. However, it is not the role of the character encoding / decoding to do such locale-related translations. You need to code it yourself ... or find some other library that does it.</p> <hr> <p>Messing around at the byte level (encoding with one charset and decoding with a different one) is not going to "fix" this. If anything it is going to make things worse. Your messing around is generating byte sequences that can't be mapped to the target encoding scheme ... and hence the question marks.</p>
    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. 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.
 

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