I've been plunking around with spelling today and believe I have observed
Auto-correct word pairs:
Documentation is incorrect regarding userdict controlling word pairs. Jason
Buss reported this here a while back, I think. You can still customize
auto-correct by modifying autocorrect.xlf (found in the Editor install
custom/lib directory) manually. I copied autocorrect.xlf to my custom/lib
directory and edited it and got the behavior I expected. However, I deleted
all the contents of my autocorrect.xlf except for my customizations hoping
my entries would be added to the autocorrect.xlf entries in the install tree
but, no, when I did that, it overrode the entire file ... only my
autocorrect pairs were found. Auto-correct does not support replacing "e.g."
with "eg" although it will support the reverse.
You can add "e.g." or "eg" but not both.
Removing one removes either.
You can add "eg:e.g." but it will not auto-correct (as stated above). Both
will still be flagged.
When you add "eg:e.g." it is reported by a subsequent -list as "eg;e.g.".
(Note that's a semicolon, not a colon.)
It is not possible to reject word using userdict. (I was hoping for "-eg"
It is possible to specify required capitalization using userdict however you
can't SEE it in -list. (An entry of "Apple" will flag "apple" but be
reported as "apple" by -list.)
It is not possible to flag capitalization where it is wrong using userdict.
spell command, aptspell.acp, aptspell.rjt
It is possible to flag missing capitalization using "spell -accept".
It is not possible to flag capitalization where it is wrong using "spell
Entries in aptspell.rjt files override aptspell.acp (this can only tested by
editing the files manually).
Entries in aptspell.xxx files override userdict.
You can accept e.g. but not eg OR eg but not e.g. HOWEVER, if you reject
either, both are.
When you "spell -delete" e.g. or eg, both are deleted according to the Edit
Window, but an entry may get left behind in an aptspell.xxx file and be
respected in the next edit session.
I still need to experiment with the environment variables regarding the
location of aptspell.xxx. Specifically, what happens if I specify a location
to which authors only have read access. But it's lunch time ...