Closed GoogleCodeExporter closed 9 years ago
Hi, thanks for your feedback.
About the localized keyboard layouts, it's a planned feature, and one of the
next things I'm going to work on. The corresponding tracking issue is here:
http://code.google.com/p/magickeyboard/issues/detail?id=13 (I'll mark this as
a duplicate of that one.)
Until it's resolved, you can manually edit the keyboard layouts in order to
move the keys to where you prefer. For example, if you want to swap A with Q
and W with Z in the default layout, you can do as follows:
- Locate MagicKeyboard in your Applications folder, ctrl-click it and choose
"Show Package Contents".
- Browse to the Contents/Resources/Layouts folder.
- Open the file QwertyMini.plist in your favorite text editor, such as
TextEdit, TextWrangler, etc (or a plist editor, in case you have XCode
installed)
- Locate the entries you want to swap. The Q key, for example, in a text
editor looks like this:
<dict>
<key>Button</key>
<integer>1</integer>
<key>Type</key>
<string>Symbol</string>
<key>Value</key>
<string>q</string>
<key>Comment</key>
<string>Q key</string>
</dict>
- Change the values that are inside the <string></string> entries to the ones
you want. You'll want to replace Q with A, q with a, W with Z, w with z, etc.
If you prefer, just use the file I attached: it contains the edits I just
mentioned. Put it in the Contents/Resources/Layout folder that's within the
MagicKeyboard app, replacing the existing one.
Please note that after any future update of MagicKeyboard, any edits to those
files will be overwritten again with the default versions. Make sure you have
a backup. In future I'll provide a way to make changes that persist after an
update.
The printable sticker (provided that the user has a suitable printer and paper
to print on, of course) will come soon, too. Tracking issue here:
http://code.google.com/p/magickeyboard/issues/detail?id=6
Original comment by emanuele...@gmail.com
on 5 Oct 2011 at 12:15
Attachments:
Issue 17 has been merged into this issue.
Original comment by emanuele...@gmail.com
on 5 Oct 2011 at 6:49
Original issue reported on code.google.com by
lelous...@gmail.com
on 4 Oct 2011 at 8:56