Terminal.app won't display OpenType fonts (.otf)

Question

Level 1

0 points

Terminal.app won't display OpenType fonts (.otf)

Where the characters should be, blanks are displayed. This is a serious problem for me because, while I use Monaco in my terminal, the fallback font for Japanese characters is Hiragino, which is an OpenType font: as a result, Japanese text is not visible in my terminal.

Here is a screenshot: http://i.imgur.com/wlNPV.png
Note that, since I set the system's language to Japanese, most of the text in Terminal's preferences is also invisible.

The problem only seems to occur in Terminal.app, and does not affect other users on the same machine (I tried logging in as guest). It occurs with all OpenType fonts I tried, not just Japanese ones.

Strangely, if I delete Terminal's preferences, the problem almost disappears (except that it still says ル in the window's title bar instead of ターミナル); however, if I close and relaunch Terminal, the problem immediately reoccurs, even though the preferences file is pristine.

I tried resetting the ATS cache (atsutil databases -remove) and restarting in safe mode, but the problem still occurs. I've tried googling around, and I found some other people mentioning the same problem, but no solution. Can you help?

MacBook, Mac OS X (10.6.6)

Posted on Mar 8, 2011 3:38 PM

Reply

Answer 1

Linc Davis

Level 10

209,535 points

Mar 8, 2011 4:59 PM in response to CamilloL

You seem to be saying that everything is completely normal in the guest account, but not in your account. Do you have any fonts installed in your home Fonts folder that might conflict with the system fonts? If not, move your entire Library folder aside. Log out and back in. Recreate your font preferences in Terminal and verify that it works. Then start adding back the stuff you removed, testing as you go along until you find the culprit.

Reply

Answer 2

CamilloL Author

Level 1

0 points

Mar 9, 2011 5:18 AM in response to Linc Davis

I have some fonts in my home, but none that conflict, according to Font Book. To be honest, I am a bit concerned that resetting the entire Library might cause additional problems, even if I later attempt to set it back. :/

BTW, I just noticed that it's not entirely true that only Terminal.app is affected. As you can see in the picture linked below, the ー character in キーチェーン is not visible in the title bar of Keychain Access, though the same word is displayed correctly in the line below. Very strange.

http://imgur.com/bz4fK

Reply

Answer 3

Linc Davis

Level 10

209,535 points

Mar 9, 2011 5:49 AM in response to CamilloL

+I am a bit concerned that resetting the entire Library might cause additional problems, even if I later attempt to set it back.+

Then create a new user account and copy your Library folder (and whatever else is needed to reproduce the problem) to it, changing the ownership to the new user. Don't do anything in the test account besides launching Terminal.

Reply

Answer 4

CamilloL Author

Level 1

0 points

Mar 10, 2011 6:07 PM in response to CamilloL

Hmm, interesting. I just installed GPGTools (http://www.gpgtools.org/, version 2011.03.02) and the problem now occurs in Mail.app too. I had also installed Xcode 4 just before. Let's see if removing GPGTools fixes it.

Reply

Answer 5

CamilloL Author

Level 1

0 points

Mar 10, 2011 6:09 PM in response to CamilloL

Removing GPGMail.mailbundle solved the problem in Mail.app! Now to find out how it caused it in the first place...

Reply

Answer 6

rémi

Level 1

0 points

Apr 22, 2011 4:07 AM in response to CamilloL

Hi,

I have the same problem. Japanese fonts in terminal don't work any more in my account, but they work correctly in the guest account. I tried removing com.apple.Terminal.plist and re-logging as advised elsewhere on this board, but it did not work.

I also installed Xcode 4 recently.

The suggestion of moving my Library folder sounds really scary. If anyone has a better solution, that would be welcome.

Rémi

Reply

Answer 7

Tom Gewecke

Level 10

115,806 points

Apr 22, 2011 6:22 AM in response to rémi

The suggestion of moving my Library folder sounds really scary.

You can try moving your folder Home/Library/Fonts to your desktop. No harm can come from that. Same for Home/Library/Preferences. If no improvement, just put them back.

Reply

Answer 8

CamilloL Author

Level 1

0 points

Apr 27, 2011 9:39 AM in response to CamilloL

Apple has just released a Snow Leopard Font Update. It sounded promising, but after installing it I am sad to report that nothing has changed. OpenType fonts still don't work in Terminal.

Reply

Answer 9

May 14, 2011 11:38 AM in response to CamilloL

I've got the same problem with my new MBP 2011 with Snow Leopard and it really annoys me as I'm dealing with multilingual texts every day.

What surprises me is that I had no problems at all since MacOs 10.1 and now it appears in 10.6 !

Back in the old days I had to put a .inputrc file for displaying Japanese characters but that was not a big deal.

When I create a new account, it works for a few hours (Japanese characters display well even with menlo or courier fonts set as default). But after a few manipulations here and there (that do not seem related to terminal or fonts like setting my iTunes account) and a couple of reboots, the problem reappears again, ie the Japanese characters do not display again.

I can temporarily solve the problem by using the Osaka font but 1 it is not nicely displayed with irregular spaces between characters and 2 when I want to display other characters (thai, khmer or whatever), I have to change the default font again. This is a real pain in the neck😠.

I read in another thread that there is a solution to convert the OpenType Font you wish to use into a TrueType font but it is not a solution for me neither as there is no existing font that covers all the unicode characters.

Is Apple aware of this bug? Did they acknowledge that there is a problem?

If someone finds a solution, I'll be really happy.

Reply

Answer 10

CamilloL Author

Level 1

0 points

May 14, 2011 1:04 PM in response to mathieufromchambery

Apple is aware of the bug; I submitted it last year (rdar://8724546). They have not reacted to it so far. Posting more reports to bugreport.apple.com would probably help them devote some engineering resources to this problem. I don't think we're ever going to see a fix for Snow Leopard, but at least I hope we won't have to suffer the same bug in Lion!

Reply

Answer 11

rémi

Level 1

0 points

Jul 9, 2011 3:27 AM in response to Tom Gewecke

Tom Gewecke wrote:

The suggestion of moving my Library folder sounds really scary.

You can try moving your folder Home/Library/Fonts to your desktop. No harm can come from that. Same for Home/Library/Preferences. If no improvement, just put them back.

Thanks for your suggestion. I tried it, and moving Preferences solves the problem. But, of course, I lose all my preferences, which is very annoying, and not really acceptable. I tried moving only com.apple.Terminal.plist, but it does not work. Now, I have 389 files in my Preferences directory, and finding the culprit among them will be very tedious. I know binary search should take only 9 iterations, but that is still very annoying to do.

I wonder if anybody has made progress with this bug.

Thanks,

Rémi

Reply

Answer 12

CamilloL Author

Level 1

0 points

Jul 24, 2011 7:03 PM in response to CamilloL

I am sorry to announce that the problem is still present in Lion. This is really disheartening. 😟

Reply

Answer 13

rémi

Level 1

0 points

Mar 30, 2012 8:08 AM in response to CamilloL

One year later, this bug is still making me crazy. Has anybody made progress? Can anybody suggest a solution?

Thanks.

Reply

Answer 14

etresoft

Level 8

46,046 points

Mar 30, 2012 6:26 PM in response to rémi

rémi wrote:

One year later, this bug is still making me crazy. Has anybody made progress? Can anybody suggest a solution?

Can anybody even reproduce it?

Reply

Answer 15

AnXa

Level 1

0 points

Jun 2, 2012 3:04 PM in response to rémi

I had this problem 15 minutes ago and I solved it by installing another console font 5 minutes ago. I replaced "monaco" with a font called "monapo" (http://www.geocities.jp/ep3797/modified_fonts_01.html). It corrected my JIS-art files (http://en.wikipedia.org/wiki/2channel_Shift_JIS_art) to what they should be.

Reply