Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have not tested this, but it seems to me that you need to use the <a href="http://www.adobe.com/devnet/opentype/archives/glyph.html" rel="nofollow noreferrer">Adobe Glyph Naming convention</a> for this:</p> <blockquote> <p>The purpose of the Adobe Glyph Naming convention is to support the computation of a Unicode character string from a sequence of glyphs. This is achieved by specifying a mapping from glyph names to character strings.</p> </blockquote> <p>The <a href="http://www.adobe.com/devnet-archive/opentype/archives/glyphlist.txt" rel="nofollow noreferrer">glyphlist.txt</a> linked on that page seems to be relevant for your issue.<br> Sample fragment:</p> <blockquote> <p>...<br> epsilon;03B5<br> epsilontonos;03AD<br> <strong>equal;003D</strong><br> equalmonospace;FF1D<br> equalsmall;FE66<br> equalsuperior;207C<br> ...</p> </blockquote> <p>Then all you need to do is <a href="https://stackoverflow.com/questions/6839287/nsstring-unicode-display">putting those unicode values in your NSString instance</a>.</p> <p><strong>Edit:</strong><br> Confirming the information provided above, I found the following explanation on the <a href="http://www.adobe.com/devnet/pdf/pdf_reference_archive.html" rel="nofollow noreferrer">PDF Reference Document from Adobe</a>, <em>Section 5.9 - Extraction of Text Content</em>:</p> <blockquote> <p>If the font is a simple font that uses one of the predefined encodings MacRomanEncoding, MacExpertEncoding, or WinAnsiEncoding, or that has an encoding whose Differences array includes only character names taken from the Adobe standard Latin character set and the set of named characters in the Symbol font (see Appendix D): </p> <ol> <li>Map the character code to a character name according to Table D.1 on page 996 and the font’s Differences array.</li> <li>Look up the character name in the Adobe Glyph List (see the Bibliography) to obtain the corresponding Unicode value.</li> </ol> </blockquote>
 

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