empty charset registry?

[Ilya N. Golubev]

> (set-charset-registry 'latin-iso8859-1 "charset-registry-of-desired-font")

As described, charset registry being empty string allowed to display
at the *same* time the same buffer text in *different* frames /
windows in different fonts specified per locale (as in specifiers).
So this is not even a way around.


Another issue is that not all X servers represent all their fonts in
XLFD.  Used at least one where `8x14pc437' font could be specified
only with this string.  So there still have to be a way to specify
non- XLFD font name in X.


> That?s a horrible, evil hack. 

It is also clear use of documented features, with obvious and useful
effect.  After all, what frame / window specifications in font
specifiers are good for, if settings through them will be largely
ignored due to obscure internal filtering (which happened to be
charset registries).

Even at least once posted description of setups with fonts (for raw
text) specified per frame, in <023539c9d20f39-gin at mo.msk.ru> posted to
<xemacs-patches at xemacs.org> on Thu, 21 Sep 2000 09:17:03 +0 (before
the <xemacsweb/About/XEmacsServices.html#issue31> crash was
<http://www.xemacs.org/list-archives/xemacs-patches/200009/msg00064.html>).
So it is a long known use of xemacs.