Ticket Options

Question Details

TICKET ARCHIVE -> Keyboard Layout On a Japanese Ibook G3

annersanners - Jul 29, 2005 - 4:16 am

This is the deal: I have a Japanese iBook G3, with both roman characters and hiragana on the keyboard. A few weeks ago I got it serviced in Vietnam (had to get the logic board replaced), and when I got it back from the repair shop, the keyboard layout seems to have been switched to US. That is, I have to press shift-2 to get the @ sign now...pressing the key labelled "@" on my keyboard doesn't work anymore. Likewise, apostrophes and quotation marks are not where they're supposed to be anymore.

I can't figure out how to switch it back...I've tried deselecting "US" in the input menu in System Preferences--International, but the computer won't let me do that.

Any help appreciated...thanks.

earthsaver - Jul 29, 2005 - 6:19 am

It's impossible to uncheck an item in Input Menu preferences when only one is checked. You need to select your preferred Japanese input method before you can deselect U.S. (Use Keyboard Viewer if you need to confirm the desired layout.)

- Ben

annersanners - Jul 29, 2005 - 7:41 am

Hi Ben, thanks for your reply. My computer still won't let my uncheck "US" in Input Menu preferences even though I've selected "kotoeri／ことえり" Japanese input.

Can you tell me how to access Keyboard Viewer?

Thanks again,

Annamarie

earthsaver - Jul 29, 2005 - 12:39 pm

I don't know what version of Mac OS X you're using. If you have 10.2, it's still called Key Caps and it's in the Utilities folder. If you have 10.3 or later, it's another item you can check in the Input Menu preferences and view from that menu. I don't know why you can't uncheck U.S., but with Kotoeri selected, can you select Kotoeri from the Input Menu?

- Ben

annersanners - Jul 29, 2005 - 8:50 pm

I'm using 10.2. Even with Kotoeri selected, when I'm typing in both English and Japanese the keyboard still follows a US layout.

Would this have something to do with the logic board?

earthsaver - Jul 29, 2005 - 9:21 pm

I doubt there's a connection. Are you updated to 10.2.8? I don't know that anything particular to this issue was fixed, but if you're not, it's worth a shot. Other than that, I'm out of ideas for the moment.

- Ben