Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Using Unicode, there is more than one valid way to represent the same letter. The characters you're using in your Tricky Name are a "latin small letter i with circumflex" and a "latin small letter a with ring above".</p> <p>You say "Note the <code>%CC</code> versus <code>%C3</code> character representations", but looking closer what you see are the sequences</p> <pre><code>i 0xCC 0x82 vs. 0xC3 0xAE a 0xCC 0x8A vs. 0xC3 0xA5 </code></pre> <p>That is, the first is letter <code>i</code> followed by 0xCC82 which is the UTF-8 encoding of the <a href="http://www.fileformat.info/info/unicode/char/0302/index.htm" rel="nofollow noreferrer">Unicode<code>\u0302</code></a> "combining circumflex accent" character while the second is UTF-8 for <a href="http://www.fileformat.info/info/unicode/char/00ee/index.htm" rel="nofollow noreferrer"><code>\u00EE</code></a> "latin small letter i with circumflex". Similarly for the other pair, the first is the letter <code>a</code> followed by 0xCC8A the "combining ring above" character and the second is "latin small letter a with ring above". Both of these are valid UTF-8 encodings of valid Unicode character strings, but one is in "composed" and the other in "decomposed" format.</p> <p>OS X HFS Plus volumes store strings (e.g. filenames) as "fully decomposed". A Unix file-system is really stored according to how the filesystem driver chooses to store it. You can't make any blanket statements across different types of filesystems.</p> <p>See the Wikipedia article on <a href="http://en.wikipedia.org/wiki/Unicode_equivalence" rel="nofollow noreferrer">Unicode Equivalence</a> for general discussion of composed vs decomposed forms, which mentions OS X specifically.</p> <p>See Apple's Tech Q&amp;A <a href="http://developer.apple.com/mac/library/qa/qa2001/qa1235.html" rel="nofollow noreferrer">QA1235</a> (in Objective-C unfortunately) for information on converting forms.</p> <p>A <a href="http://lists.apple.com/archives/java-dev/2010/Feb/msg00177.html" rel="nofollow noreferrer">recent email thread</a> on Apple's java-dev mailing list could be of some help to you.</p> <p>Basically, you need to normalize the decomposed form into a composed form before you can compare the strings.</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