Chris' many letters
Will Robertson
Some comments are lumped together here. Surprisingly, there's not too
much.
>> >> \MathAlphabetChar{\mathbfsfit}{956}{"1D7B5}%
>
> Not having read your wonderful documentation, I am unsure why an
> actual
> command \math... appears in these declarations ... I woudl have
> expected
> something more abstract since there may be many diufferent ways of
> envoking these types of mathchar changes.
To your dislike :) at the moment I'm using \mathcode switching to
implement the maths alphabets. (This still isn't set in stone,
however.) So the \MathAlphabetChar (indeed, a better name is
possible) stuff is exclusively for effecting this.
At some stage I'll ask if a "maths font selection scheme" is desired
so we might want to type \mathbf{\mathsf{...}} as an option or
instead of \mathbfsf{...}.
***
I see there's some back and forth between Ross' ideas and your own
(and Frank's), so I'm glad I haven't taken sides yet. The whole thing
behind that cryptic code
> \catcode`\^=12\relax
> \gdef\test#1#2{%
> \lowercase{\scantokens{\let#1^^#2}}}
is to do things like `\let\testmacro^^65` and setting the mathcode of
^^65 (or whatever) directly rather than \mathchardef-ing the macro in
the first place.
But I think Ross changed his mind on that due to the weird properties
of \testmacro in this case.
***
I'm glad we're in (strong) agreement about avoiding some complex
definition for the maths alphabet macros that involves parsing
whatever's inside. Once I finish up my implementation using mathcode
switching, we can take a look at what's going on and examine if using
XeTeX font mappings is a better idea. That is, do we want a:
> sensible use of XeTeX!
:)
Busy week ahead.
Cheers,
Will