1

I just downloaded Code 2000 from Wayback Machine but when I tried to install it Font Book reported a serious error but no further details.

Anyone know what might be the problem? Are there any online resources that allows me to verify a font's integrity and hopefully could give me some more details about any potential issues?

  • It doesn't look like James Cass fully completed the Code 2000 project at all. – IconDaemon Oct 24 '17 at 16:21
  • @IconDaemon It was very advanced for its time, but Unicode coverage has grown tremendously and there are now many other fonts available to handle it, including google.com/get/noto – Tom Gewecke Oct 24 '17 at 16:52
  • @TomGewecke Newer alternatives such as? I like a font that my computer can fall back on when it's missing certain unicode characters. – d-b Oct 24 '17 at 17:55
  • @d-b do you have an example of something missing? Macos probably already covers more than the very old Code 2000. Did you not see the link i gave for Noto fonts? – Tom Gewecke Oct 24 '17 at 18:09
  • Futhark? @TomGewecke – d-b Oct 24 '17 at 18:57
1

In my experience Font Book warnings rarely have any real consequences.

It's also hard to imagine any issues that could not be easily fixed by just removing the font. Install it manually in Home/Library/Fonts and see if you find any problems.

To get to Home/Library, hold down the option key while doing Finder > Go.

If your goal is to ensure complete Unicode coverage, I suspect MacOS already has more of this than the very old Code 2000. To expand coverage beyond what Apple offers, I would recommend the Google Noto fonts and Symbola.

To see what font has a specific character when Apple's Character Viewer is empty, try Fileformat.

|improve this answer|||||

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .