"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
It has _not_ been in this state for a while. It was _not_ in this
state in 20.4, and not in some sufficiently early 21.0 betas.
Note that I changed the font-menu to be Custom aware quite recently. I
probably messed something up there or uncovered an hidden problem.
If I am correct your problem is that choosing a different font from
the font menu screws up other fonts (in this case the Kanji ones)?
If so could you tell me
1. Where this also happens if you make exactly the same change with
Customize (i.e. M-x customize-face RET default RET)
2. If you save options and then restart XEmacs are the fonts OK?
3. If setting font-menu-ignore-scaled-fonts to nil really early
(i.e. before the first access to the font-menu) helps.
4. If you have an old .xemacs-options from an XEmacs that worked
and you used a 'option-save-faces = t' to save them, what are
the settings saved for the fonts.
The options menu differs
- from customize-face in that it contains some trickery to update
the other fonts. This however is more or less the same as in the
old font-menu.
- from the old font-menu in that it now just informs customize of
the change and let it change the default font. The old fontmenu
used its own mechanism to derive the new font from the old. Maybe
that preserved the mule info better.
Unfortunately in order to 'keep it simple for the User' and to
preserve compatibility with FSF Emacs the customize view of fonts is
decidedly more primitive than the XEmacs one.
Jan