It only provides a "stand-in" glyph if you don't otherwise have a font for
that character on your system. That "stand-in" just indicates the type of
character (eg script).
No single font with current technology can handle all of Unicode. The most
complete open font set I know of is the Noto family:
https://www.google.com/get/noto/. I don't think it has a full set of
symbols (others: correct me if I'm wrong.) Symbola is pretty good for
There are many other resources on http://unicode.org/resources/fonts.html.
*— Il meglio è l’inimico del bene —*
On Thu, Mar 26, 2015 at 8:53 AM, Michael McGlothlin <
> Similar but with a couple differences. Most important would be getting
> vendors to actually use the font. Also it should be appropriate to actually
> display the characters rather than being debugging information.
> Does this last resort font represent every character in some meaningful
> way? e.g. I've tried to use somewhat rare characters like runes before and
> it was a pretty big pain to find fonts that were free to distribute,
> weren't buggy, and displayed the correct symbol for that character. And
> some applications wouldn't display them correctly even after installing a
> font. (Visual Studio let me use runes as variable names and compiled fine
> but wouldn't actually display the rune symbols.)
> Sent from my iPad
> On Mar 25, 2015, at 5:18 PM, Shervin Afshar <shervinafshar_at_gmail.com>
> Just like Unicode Last Resort Font?
> : http://www.unicode.org/policies/lastresortfont_eula.html
> ↪ Shervin
> On Wed, Mar 25, 2015 at 2:24 PM, Michael McGlothlin <
> mike.mcglothlin_at_gmail.com> wrote:
>> I'd like to see a free/open "default" font that has a correct, simple
>> styled, symbol for every Unicode character. Vendors should be pressured to
>> use this font when other options aren't available. I get tired of seeing
>> default symbols, incorrect symbols, and mystery white spaces that aren't
>> really white space. It's pretty silly to have a code point without a
>> default symbol I think.
>> Michael McGlothlin
>> Sent from my iPhone
>> On Mar 25, 2015, at 12:20 PM, Robert Wheelock <rwhlk142_at_gmail.com> wrote:
>> When you’re typing, do you find yourself winding up being CONFUSED over
>> what you type?!?! It’s a crucially SERIOUS matter—especially when typing
>> on a computer!
>> For instance: When you type in a HOLLOW HEART SUIT (U+02661), it may
>> show up as an IDENTICAL TO SIGN (U+02261) or a GREEK CAPITAL LETTER XI
>> (U+0039E)... it all DEPENDS on whatever FONT you’re using to type with!
>> The default Microsoft Sans Serif font (within Microsoft Windows) has this
>> ABOMINABLE habit of substituting this IDENTICAL TO SIGN (which should be at
>> U+02261)—because Microsoft (regrettably) placed this math symbol where the
>> HOLLOW HEART SUIT should be (at U+02661)! * ¡AGONISTES!*
>> What Microsoft SHOULD DO *is* *THIS*: Please move the IDENTICAL TO SIGN
>> from (U+02661—the location where the HOLLOW HEART SUIT goes) to its PROPER
>> LOCATION at (U+02261)!! THAT would be MUCH better!!
>> What other CHARACTER CALAMITIES have you come across?!?!
>> Thank You!
>> Unicode mailing list
> Unicode mailing list
Unicode mailing list
Received on Thu Mar 26 2015 - 04:56:42 CDT
This archive was generated by hypermail 2.2.0 : Thu Mar 26 2015 - 04:56:43 CDT