6:03 p.m.
Greetings,
running on Xubuntu 16.4 I'm currently still using XEmacs 21.4.22 which
is the version officially provided by Xubuntu (I have yet to have the
spare time to compile XEmacs directly from the Mercurial repository ...
sigh)-:
Whenever I start XEmacs I receive the following warning message:
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
In my "~/.Xresources" file I have several fonts specified for quite a
few Xemacs resources, but I'm not using any "helvetica" font. So
I'm
assuming XEmacs is falling back to some default here for some resource I
did not specify. Since it's a bold font, it's probably for some weird
menu I'm not even using ...
In file "/etc/X11/fonts/misc/xfonts-base.alias" I found the following
line:
variable -*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-1
so XEmacs could also use "variable" as a default for some unspecified
resource.
If somebody could point me to the resource name associated with that de-
fault font in XEmacs, I could update my "~/.Xresources" file according-
ly, get rid of this annoying warning message, and would again be very
happy :-)
Sincerely,
Rainer
8:08 a.m.
On 2018-03-21, Dr Rainer Woitok <rainer.woitok(a)gmail.com> wrote:
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Alternatively, you could install the font (and whatever comes with
it).
I'm also on Xubuntu 16.04.
Try installing xfonts-75dpi and xfonts-100dpi
9:56 a.m.
Julian,
On Thursday, 2018-03-22 08:08:56 +0000, you wrote:
...
> Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
Alternatively, you could install the font (and whatever comes with
it).
That's true, but given the screen resolution of my display all fonts I
use in XEmacs have a size of 150. So even if I installed this font and
let XEmacs use it, I'd have to change font size. And to do so I'd need
to know the name of the resource specifying this font. And if I knew
that, I could as well use the fonts I'm used to.
Thus I still need to know that resource name.
Any takers?
Sincerely,
Rainer
2:57 p.m.
On Thu, Mar 22, 2018 at 3:56 AM, Dr Rainer Woitok
<rainer.woitok(a)gmail.com> wrote:
That's true, but given the screen resolution of my display all
fonts I
use in XEmacs have a size of 150. So even if I installed this font and
let XEmacs use it, I'd have to change font size. And to do so I'd need
to know the name of the resource specifying this font. And if I knew
that, I could as well use the fonts I'm used to.
Thus I still need to know that resource name.
Any takers?
Take a look in etc/Emacs.ad in the source distribution. I see the
following occurrences of that font:
*menubar*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
*popup*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
-*-*-*-*-*-*-*-120-*-iso10646-1, \
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0, \
-*-*-*-*-*-*-*-120-*-jisx0201.1976-0
*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
-*-*-*-*-*-*-*-120-*-iso10646-1, \
-*-*-*-*-*-*-*-120-*-jisx0208.1983-0, \
-*-*-*-*-*-*-*-120-*-jisx0201.1976-0
*XmDialogShell*FontList: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
There is also an instance of that font baked into the source code; see
lwlib/xlwmenu.c, line 86, which is only used if your XEmacs is built
with Motif support.
I will note that, for the purposes of building XEmacs for the Fedora
Linux distribution, I replace all of those "iso8859" specifiers with
"*", because most of the available fonts are Unicode fonts these days.
--
Jerry James
http://www.jamezone.org/
3:26 p.m.
Jerry,
On Thursday, 2018-03-22 08:57:10 -0600, you wrote:
...
*menubar*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
*popup*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
I was missing these two, even though I had defined all the others you
mentioned here, in particular
*menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
...
*popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
So adding these two missing simple "*Font" resources to my
".Xresources"
file solved my problem. Thanks a lot :-)
However, I'm still not aware of what precisely the semantic difference
between these two forms is. Why do I still need "*menubar*Font" when
"*menubar*FontSet" is already defined? Can anybody explain?
Sincerely,
Rainer
11:19 a.m.
Ar an ceathrú lá is fiche de mí Márta, scríobh Dr Rainer Woitok:
Jerry,
On Thursday, 2018-03-22 08:57:10 -0600, you wrote:
> ...
> *menubar*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
> *popup*Font: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*
I was missing these two, even though I had defined all the others you
mentioned here, in particular
> *menubar*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
> ...
> *popup*FontSet: -*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, \
So adding these two missing simple "*Font" resources to my
".Xresources"
file solved my problem. Thanks a lot :-)
However, I'm still not aware of what precisely the semantic difference
between these two forms is. Why do I still need "*menubar*Font" when
"*menubar*FontSet" is already defined? Can anybody explain?
The internationalisation support for the X11 toolkits was added on after
their initial development, and involves the FontSet resources in addition to
the Font resources. We do it this way because the X toolkits do it this way.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
1:32 p.m.
Aidan,
On Sunday, 2018-03-25 11:19:51 +0100, you wrote:
Ar an ceathrú lá is fiche de mí Márta, scríobh Dr Rainer Woitok:
> ...
> However, I'm still not aware of what precisely the semantic difference
> between these two forms is. Why do I still need "*menubar*Font" when
> "*menubar*FontSet" is already defined? Can anybody explain?
The internationalisation support for the X11 toolkits was added on after
their initial development, and involves the FontSet resources in addition to
the Font resources. We do it this way because the X toolkits do it this way.
Does that mean I should also specify the resource
XEmacs.default.attributeFontSet: \
-*-my favorite font-medium-r-*--0-150-*-*-m-*-*-*,
-*-some unicode font-medium-r-*--0-150-*-*-*-*-*-*
in addition to the already existing resource
XEmacs.default.attributeFont: \
-*-my favorite font-medium-r-*--0-150-*-*-m-*-*-*
in order to correctly display a file containing Unicode characters?
Sincerely,
Rainer
9:35 p.m.
Ar an t-ochtú lá is fiche de mí Márta, scríobh Dr Rainer Woitok:
Aidan,
On Sunday, 2018-03-25 11:19:51 +0100, you wrote:
> Ar an ceathrú lá is fiche de mí Márta, scríobh Dr Rainer Woitok:
> > ...
> > However, I'm still not aware of what precisely the semantic difference
> > between these two forms is. Why do I still need "*menubar*Font"
when
> > "*menubar*FontSet" is already defined? Can anybody explain?
>
> The internationalisation support for the X11 toolkits was added on after
> their initial development, and involves the FontSet resources in addition to
> the Font resources. We do it this way because the X toolkits do it this way.
Does that mean I should also specify the resource
XEmacs.default.attributeFontSet: \
-*-my favorite font-medium-r-*--0-150-*-*-m-*-*-*,
-*-some unicode font-medium-r-*--0-150-*-*-*-*-*-*
in addition to the already existing resource
XEmacs.default.attributeFont: \
-*-my favorite font-medium-r-*--0-150-*-*-m-*-*-*
in order to correctly display a file containing Unicode characters?
No, the buffer text internationalisation is its own thing, implemented
independently of the X11 toolkits. Font configuration for that, if needed,
should be done in Lisp. See
http://mid.xemacs.org/509e.dccf.443b6.b732＠parhasard.net for some details on
how to do that.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
4 p.m.
Aidan,
On Thursday, 2018-03-29 21:35:05 +0100, you wrote:
...
No, the buffer text internationalisation is its own thing, implemented
independently of the X11 toolkits. Font configuration for that, if needed,
should be done in Lisp. See
http://mid.xemacs.org/509e.dccf.443b6.b732＠parhasard.net for some details on
how to do that.
The web page you are referring to (dating back to 2012-11-10) is about
Xft font specifications rather than XLFD with which I'm more familiar.
Is it enough to just replace "Monospace-11.5:lang=en" with a suitable
XLFD font specification? But in any case I cannot evaluate the form
(with-fboundp ...)
because function "with-fboundp" is not defined in my XEmacs 21.4 :-(
Is it really that hard to display Unicode in an XEmacs buffer?
Sincerely,
Rainer
8:26 a.m.
Ar an cúigiú lá de mí Aibreán, scríobh Dr Rainer Woitok:
Aidan,
On Thursday, 2018-03-29 21:35:05 +0100, you wrote:
> ...
> No, the buffer text internationalisation is its own thing, implemented
> independently of the X11 toolkits. Font configuration for that, if
> needed, should be done in Lisp. See
> http://mid.xemacs.org/509e.dccf.443b6.b732＠parhasard.net for some
> details on how to do that.
The web page you are referring to (dating back to 2012-11-10) is about
Xft font specifications rather than XLFD with which I'm more familiar.
Is it enough to just replace "Monospace-11.5:lang=en" with a suitable
XLFD font specification?
Yes, it should be.
But in any case I cannot evaluate the form
(with-fboundp ...)
because function "with-fboundp" is not defined in my XEmacs 21.4 :-(
That’s fine, you can just delete it (it’s a construct to suppress warnings,
and not necessary for the functionality.)
Is it really that hard to display Unicode in an XEmacs buffer?
It shouldn’t be, see the “if needed” above.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
5:08 p.m.
Aidan,
On Friday, 2018-04-06 08:26:11 +0100, you wrote:
...
> But in any case I cannot evaluate the form
>
> (with-fboundp ...)
>
> because function "with-fboundp" is not defined in my XEmacs 21.4 :-(
That’s fine, you can just delete it (it’s a construct to suppress warnings,
and not necessary for the functionality.)
What precisely am I expected to delete? The structure of the form is
like this:
(with-fboundp '(fc-name-unparse fc-font-match fc-name-parse)
(set-specifier ...)
(macrolet ((define-tags-and-set-faces ...))
(define-tags-and-set-faces ...)
)
)
and the form starting with "set-specifier" calls functions (or macros)
"fc-name-unparse", "fc-font-match", and "fc-name-parse"
which again are
undefined in my XEmacs 21.4.
Sincerely,
Rainer
1:45 p.m.
Ar an t-aonú lá déag de mí Aibreán, scríobh Dr Rainer Woitok:
Aidan,
On Friday, 2018-04-06 08:26:11 +0100, you wrote:
> ...
> > But in any case I cannot evaluate the form
> >
> > (with-fboundp ...)
> >
> > because function "with-fboundp" is not defined in my XEmacs 21.4
:-(
>
> That’s fine, you can just delete it (it’s a construct to suppress
> warnings, and not necessary for the functionality.)
What precisely am I expected to delete? The structure of the form is
like this:
(with-fboundp '(fc-name-unparse fc-font-match fc-name-parse)
(set-specifier ...)
(macrolet ((define-tags-and-set-faces ...))
(define-tags-and-set-faces ...)
)
)
and the form starting with "set-specifier" calls functions (or macros)
"fc-name-unparse", "fc-font-match", and "fc-name-parse"
which again are
undefined in my XEmacs 21.4.
Ah, sorry.
So, first of all, are you actually having trouble displaying characters you
want displayed? Because if not, then we don’t have an issue.
If you *are* having trouble, after looking a bit further I have bad news.
The support for specifying a font for a given character set is my code from
2006, and it never made it into 21.4. You would need to switch to 21.5 to be
able to use it.
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)
6:24 p.m.
On 2018-04-14, Aidan Kehoe <kehoea(a)parhasard.net> wrote:
So, first of all, are you actually having trouble displaying
characters you
want displayed? Because if not, then we don’t have an issue.
If you *are* having trouble, after looking a bit further I have bad news.
The support for specifying a font for a given character set is my code from
2006, and it never made it into 21.4. You would need to switch to 21.5 to be
able to use it.
Or if you're deeply wedded to 21.4, you could switch to jcbmacs (as
Aidan called it), which specifies fonts (plural) for character sets,
and pulls out the first glyph it finds for the character, and can fall
back to looking for a glyph to the Unicode equivalent character.
4:54 p.m.
Julian,
On Saturday, 2018-04-14 18:24:49 +0100, you wrote:
...
Or if you're deeply wedded to 21.4, you could switch to jcbmacs (as
Aidan called it), which specifies fonts (plural) for character sets,
and pulls out the first glyph it finds for the character, and can fall
back to looking for a glyph to the Unicode equivalent character.
Would you mind elaborating a bit?
Sincerely,
Rainer
3:05 p.m.
Aidan,
On Saturday, 2018-04-14 13:45:10 +0100, Aidan Kehoe wrote:
Ar an t-aonú lá déag de mí Aibreán, scríobh Dr Rainer Woitok:
...
So, first of all, are you actually having trouble displaying characters you
want displayed? Because if not, then we don’t have an issue.
Well, yes. Let me just take the first line from your mail (which ends
in "scriobh Dr Rainer Woitok:"). It more or less looks like garbage in
my XEmacs:
Ar an t-aonú lá déag de mà Aibreán, scrÃobh Dr Rainer Woitok:
But, oddly, when I hit "reply" it looks quite ok as can be seen above.
To show you what I mean:
$ # Processing the "garbage" from your mail:
$ echo 'Ar an t-aonú lá déag de mà Aibreán, scrÃobh Dr Rainer Woitok:'| od
-A d -t x1a
0000000 41 72 20 61 6e 20 74 2d 61 6f 6e c3 83 c2 ba 20
A r sp a n sp t - a o n C etx B : sp
0000016 6c c3 83 c2 a1 20 64 c3 83 c2 a9 61 67 20 64 65
l C etx B ! sp d C etx B ) a g sp d e
0000032 20 6d c3 83 c2 ad 20 41 69 62 72 65 c3 83 c2 a1
sp m C etx B - sp A i b r e C etx B !
0000048 6e 2c 20 73 63 72 c3 83 c2 ad 6f 62 68 20 44 72
n , sp s c r C etx B - o b h sp D r
0000064 20 52 61 69 6e 65 72 20 57 6f 69 74 6f 6b 3a 0a
sp R a i n e r sp W o i t o k : nl
0000080
$ # Processing the "auto-converted" line in my reply mail:
$ echo 'Ar an t-aonú lá déag de mí Aibreán, scríobh Dr Rainer Woitok:' | od -A d
-t x1a
0000000 41 72 20 61 6e 20 74 2d 61 6f 6e c3 ba 20 6c c3
A r sp a n sp t - a o n C : sp l C
0000016 a1 20 64 c3 a9 61 67 20 64 65 20 6d c3 ad 20 41
! sp d C ) a g sp d e sp m C - sp A
0000032 69 62 72 65 c3 a1 6e 2c 20 73 63 72 c3 ad 6f 62
i b r e C ! n , sp s c r C - o b
0000048 68 20 44 72 20 52 61 69 6e 65 72 20 57 6f 69 74
h sp D r sp R a i n e r sp W o i t
0000064 6f 6b 3a 0a
o k : nl
0000068
$
Of course that's not a life-threatening problem, in paticular if you do
not understand that language anyway, it's not THAT important to see the
correct glyphs :-)
So ok, I'll postpone that until I find the time to install my own XEmacs
21.5.
Sincerely,
Rainer
2539
days inactive
2567
days old
14 comments
4 participants
participants (4)
-
Aidan Kehoe -
Dr Rainer Woitok -
Jerry James -
Julian Bradfield