empty charset registry?

[Ilya N. Golubev]

Before all, I do not like inquiring like that.  It is too much like
demanding to prove that my system(s) conform to some undefined
standard, with implication that everybody with system like that is
screwed.

Moreover, one of my X servers exhibiting the "inconvenient" behavior
may be unavailable right now, so I may be unable to give detailed
answers.  This only means that someone (not necessarily me) will hit
the same restriction in xemacs with some server like that couple of
months later.  And that user will not necessarily be able to post
complete and useful bug report, let alone figure what is actually
wrong.  So what is the way forward?  To try to place obscure
restrictions on user x environments?  Or to avoid these restrictions?

At least by implementing a boolean (specifier?) option to revert to
old unrestricted behavior.


Still having the answers.

> Which fonts do you want to use?

All that are available to clients of given x server.  That is the
point since the very beginning of this <empty charset registry?>
thread of Tue, 07 Nov 2006 20:19:32 +0300, <96wt67fa3f.fsf at mo.msk.ru>.

> How do you specify them?

With string instantiators in font specifiers.  These strings are not
necessarily in xlfd dashed form.

> Which X servers do you want to use? 

Ones that implement X11 protocol.  Including, but not limited to
native `SCO:XServer::5.2.1b' from `i586-pc-sco3.2v5.0.4'.

> When you run xfd -fn font-specification , does it list a full XLFD with
> dashes at the top of the window? 

Not necessarily.  For `850pc8x14' font name it outputs just the same
string.  From font directory lookups it also appears that in that
particular system there just no other name for that font, let alone
xlfd format one.