paul> Sweet. I ran out of time to do so myself, but this could be as
paul> easy as just replicating the custom.dic logic with the following
paul> two variations, no?

paul> - it loads to/from a different hashtable - it persists into
paul> the header of the file format

(Conceptually) simpler than that. I don't know anything about the
"custom.dic" logic.

There is a specific hash table off a document that spell checking uses
to keep the ignored words list. On export, the hash table is
traversed and the word list written to the file at a scope on par with
<section>. On import, the words are read and the same function is
used to load the ignored words list as is used by spell-checking
"IgnoreAll" activity to populate it. (Something like
"BLARG->appendIgnore(theWord)".)

paul> If so, that shouldn't be bad. Do all our prefs dialogs have an
paul> appropriate button which could be hooked up to flush this list?

I don't know the answer to this either way, but does "flush" mean "get
rid of" or "save to disk"?