A. Sparling said:
Wow, this is actually really interesting. As it happens, I'm using the
U.S. extended keyboard. Now, I can locate the characters of
single-prime and double-prime by their Unicode numbers on the character
palette, but I don't see any way to find out what the corresponding
keystrokes are, and Google hasn't helped me. Of course, I can get the
right glyphs by switching keyboards to the U.S. standard one, now that
you have given me the keystrokes for it. I tried to find the glyphs by
inspection on the keyboard viewer, but without success. I also looked
aroundon the Web, but (unusually) Google didn't take me to what I
needed.
So ' What is the keystroke for my preferred keyboard?
'' is there an easy way to get from the glyph on the character palette
to the corresponding keystroke? and
(feeble answer)
put it in favourites and it is easier to find.
''' Is there a table somewhere that will tell me what every keystroke
does in all the main keyboard layouts?
You already know about the keyboard viewer. That's the best I know.
Thanks for all your help!
It *is* interesting in a banging your head against a wall kind of way.
There is a bit of a gap between autocorrect and the insert symbol add
shortcut thingy. There is no way that I can find to define a shortcut
on insert symbol if the glyph is not on the tiny little table Word
offers.
I fashioned this truly ugly method using the autocorrect in tools.
First I created a symbol field for each of single and double prime
{ SYMBOL 0x2032 \u} and { SYMBOL 0x2033 \u} respectively. Then for each
I selected the whole field, then in tools»autocorrect I typed (p) and
later (pp) in the replace part. The 'with' part already showed the
prime character, so I hit 'add' and the autocorrect table grew a (p) in
the first column and a *SYMBOL 0x2032 \u* in the second. The
disjointness between the way the field is displayed in the main window
and the way it is dsplayed in the autocorrect is faintly disturbing.
What was wrong with { and } eh?
Ugly and all, it works, as long as you can remember how to toggle
between the field source and the result (It's opt-F9 here, but I can no
longer remember if that is the default), and you can live with the
prime characters looking a bit grey.
The nice part is that it works for all keyboard nationalities - well
all the ones where I can still recognise the main letters.
I wish I could have thought of an easier way, but using curly quote
marks is *so* last Tuesday.
