Comments on: Why is my Monaco Borken? http://decafbad.com/blog/2003/06/25/font-borken It's all spinning wheels and self-doubt until the first pot of coffee. Tue, 06 Jan 2009 19:47:41 +0000 http://wordpress.org/?v=2.8-bleeding-edge hourly 1 By: Russ http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-885 Russ Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-885 <p>I'm nut ixectly soore-a vhet zee prublem is, boot I fuoond zee teetle-a su foonny thet I hed tu leefe-a a cumment leeke-a thees unyveys... :-)</p> I’m nut ixectly soore-a vhet zee prublem is, boot I fuoond zee teetle-a su foonny thet I hed tu leefe-a a cumment leeke-a thees unyveys… :-)

]]> By: Bob Lee http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-886 Bob Lee Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-886 <p>Everyone has this problem. I personally use Monaco size 15 and have been reasonably happy with it. Go to the "Additional Resources" page on http://iterm.sourceforge.net/ for more information and other font suggestions.</p> Everyone has this problem. I personally use Monaco size 15 and have been reasonably happy with it. Go to the “Additional Resources” page on http://iterm.sourceforge.net/ for more information and other font suggestions.

]]> By: Bob Schmorbin http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-887 Bob Schmorbin Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-887 <p>Check out ProFont http://www.tobias-jung.de/seekingprofont/ I wasted several days looking for the perfect monospace replacement for Monaco until I found ProFont, and I've never looked back. Thankfully there's a Windoze version too.</p> Check out ProFont
http://www.tobias-jung.de/seekingprofont/
I wasted several days looking for the perfect monospace replacement for Monaco until I found ProFont, and I’ve never looked back. Thankfully there’s a Windoze version too.

]]> By: dsandler http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-888 dsandler Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-888 <p>I'll put in my vote for ProFont. I used it for all my code in classic Mac OS; I now use it in Terminal.app (neatly side-stepping the Monaco issues) and on the Windows machines I'm forced to use during the day.</p> I’ll put in my vote for ProFont. I used it for all my code in classic Mac OS; I now use it in Terminal.app (neatly side-stepping the Monaco issues) and on the Windows machines I’m forced to use during the day.

]]> By: Tim http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-889 Tim Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-889 <p>I'd suggest grabbing Bitstream Vera, the free font Bitstream released to the Linux community. I use Vera Mono exclusively now and love it.</p> I’d suggest grabbing Bitstream Vera, the free font Bitstream released to the Linux community. I use Vera Mono exclusively now and love it.

]]> By: John Saxton http://decafbad.com/blog/2003/06/25/font-borken/comment-page-1#comment-890 John Saxton Tue, 30 Nov 1999 00:00:00 +0000 http://www.decafbad.com/blog/?p=430#comment-890 <p>This exact thing happened to me, and I tracked it down to a particular version/copy of Monaco that was behaving badly.</p> <p>I don't remember if I had done this myself or if some errant installer had foisted this upon me, but I had Monaco 3.5 from Mac OS 9.2.2 installed in my account's font folder (~/Library/Fonts), and it was overriding all other copies of Monaco on the system, even Monaco 4.0d3, which was in /System/Library/Fonts/Monaco.dfont.</p> <p>I removed that "bad" copy of Monaco 3.5 from my account's Fonts folder, and then quit and re-launched the apps that had been using it, and that cleared everything up.</p> <p>BTW, in the process of figuring this out, I went and got Apple's free OS X font tools from here: http://developer.apple.com/fonts/OSXTools.html (here's hoping that URL doesn't get stripped by the comments system)</p> <p>...and then used "ftxinstalledfonts -rlf" to see what all fonts and versions I had installed on my system, and what their precendence was.</p> <p>Hope this helps, -John</p> This exact thing happened to me, and I tracked it down to a particular version/copy of Monaco that was behaving badly.

I don’t remember if I had done this myself or if some errant installer had foisted this upon me, but I had Monaco 3.5 from Mac OS 9.2.2 installed in my account’s font folder (~/Library/Fonts), and it was overriding all other copies of Monaco on the system, even Monaco 4.0d3, which was in /System/Library/Fonts/Monaco.dfont.

I removed that “bad” copy of Monaco 3.5 from my account’s Fonts folder, and then quit and re-launched the apps that had been using it, and that cleared everything up.

BTW, in the process of figuring this out, I went and got Apple’s free OS X font tools from here:
http://developer.apple.com/fonts/OSXTools.html (here’s hoping that URL doesn’t get stripped by the comments system)

…and then used “ftxinstalledfonts -rlf” to see what all fonts and versions I had installed on my system, and what their precendence was.

Hope this helps,
-John

]]>