Stefan Monnier wrote:
Well, my patch does not address the issue mentioned by Dave: it can only
display multilingual chars that are part of the user's locale.
Could it select the locale according to the characters to be displayed?
The locale info is embedded somewhere in the Xt widget inf
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> Well, my patch does not address the issue mentioned by Dave: it
>> can only display multilingual chars that are part of the user's
>> locale.
>> Could it select the locale according to the characters to be displayed?
>
> The locale info is
> Well, my patch does not address the issue mentioned by Dave: it can only
> display multilingual chars that are part of the user's locale.
> Could it select the locale according to the characters to be displayed?
The locale info is embedded somewhere in the Xt widget info (I'm not sure
wh
Well, my patch does not address the issue mentioned by Dave: it can only
display multilingual chars that are part of the user's locale.
Could it select the locale according to the characters to be displayed?
___
Emacs-devel mailing list
Emacs-d
>> OTOH, dynamically changing the font by tweaking the `menu' face
>> doesn't seem to work on the menu bar.
> It should work now to change the Motif menu bar by changing the menu face.
Yes, it does work.
Stefan
___
Emacs-devel mailing list
E
Stefan Monnier wrote:
OTOH, dynamically changing the font by tweaking the `menu' face
doesn't seem to work on the menu bar.
It should work now to change the Motif menu bar by changing the menu face.
Jan D.
___
Emacs-devel mailing list
Emacs-devel@gnu.
> Thanks for implementing this.
> Is the following TO-DO item now deletable?
> ** Make the Lucid menu widget display multilingual text. [This
> probably needs to be done from actual Emacs buffers, either directly
> in the menu or by rendering in an unmapped window and copying the
> pixels.
Thanks for implementing this.
Is the following TO-DO item now deletable?
** Make the Lucid menu widget display multilingual text. [This
probably needs to be done from actual Emacs buffers, either directly
in the menu or by rendering in an unmapped window and copying the
pixels. Note that t
> The failure to support non-ASCII characters in menus is a bug, in my
> opinion. If you've fixed it, and your fix works well, let's install
> it now.
Installed,
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/ma
In any case, here is the new improved patch. This new patch should also
enable non-ASCII in Motif menus, although I haven't actually checked it.
I'll be happy to keep this patch for post-21.4, but if people feel like this
is important, I can install it as well.
The failure to sup
In any case, here is the new improved patch. This new patch should also
enable non-ASCII in Motif menus, although I haven't actually checked it.
>>
>>> I think you can have that already as long as your menu strings are in
>>> your
>>> locale. It works for me :-)
>>
>> Actually, I doub
In any case, here is the new improved patch. This new patch should
also
enable non-ASCII in Motif menus, although I haven't actually checked
it.
I think you can have that already as long as your menu strings are in
your
locale. It works for me :-)
Actually, I doubt this is true because the e
>> In any case, here is the new improved patch. This new patch should also
>> enable non-ASCII in Motif menus, although I haven't actually checked it.
> I think you can have that already as long as your menu strings are in your
> locale. It works for me :-)
Actually, I doubt this is true becaus
> Actually it seems that Motif always assumes the string passed to it is
> latin-1 (e.g. even in a greek locale, the greek chars (encoded by Emacs
Scratch that. I finally got it to work (also for utf-8).
OTOH, dynamically changing the font by tweaking the `menu' face
doesn't seem to work on the m
Stefan Monnier wrote:
Just to make sure I understand your judgment: you think it's not important
because the difference is minor, or because the "new" default (if
different") is also different for other apps and so it's still considered as
a legitimate default, or ...
All of the above, but I thi
>>> It is incompatible in the sense that settings in .Xresources that
>>> previously
>>> used
>>> ...*menu*font: ...
>>
>>> now must use
>>> ...*menu*fontSet:
>>
>>> for the lucid menus. This should be mentioned in NEWS.
>>
>> Hmm... good point. Do you happen to know how I could get the expect
On Mon, 14 Mar 2005 21:56:35 +0100, Jan D. <[EMAIL PROTECTED]> wrote:
> > BTW, is the HAVE_X_I18N test still necessary? It'd help if we could just
> > assume that X_I18N is available.
>
> I'm not sure. It is possible some older VMS or other systems still
> have X11R3 or X11R4 (not exactly sure w
Basically you have to set the default to something else than the
XtDdefaultFont(Set), and then check if either has been changed.
But the default is specified as a string (the name of the default
font),
whereas in the code I only have access to mw->menu.font which is
an XFontStruct*. How can I te
>>> It is incompatible in the sense that settings in .Xresources that
>>> previously
>>> used
>>> ...*menu*font: ...
>>
>>> now must use
>>> ...*menu*fontSet:
>>
>>> for the lucid menus. This should be mentioned in NEWS.
>>
>> Hmm... good point. Do you happen to know how I could get the expect
The patch below makes the Lucid menu use fontsets to draw its text, so that
it's able to write non-ASCII (the set of chars supported is dependent on the
locale, and of course on the fonts).
Thanks very much.
I'm very much an idiot when it comes to X11 programming, xfaces.c, and
Stefan Monnier <[EMAIL PROTECTED]> writes:
> The patch below makes the Lucid menu use fontsets to draw its text,
> so that it's able to write non-ASCII (the set of chars supported is
> dependent on the locale, and of course on the fonts).
Hmm. Is the dependency on the locale necessary?
> I'm ve
It is incompatible in the sense that settings in .Xresources that
previously
used
...*menu*font: ...
now must use
...*menu*fontSet:
for the lucid menus. This should be mentioned in NEWS.
Hmm... good point. Do you happen to know how I could get the expected
behavior that "if `font' is set but `
>> The patch below makes the Lucid menu use fontsets to draw its text, so that
>> it's able to write non-ASCII (the set of chars supported is dependent on the
>> locale, and of course on the fonts).
>>
>> I'm very much an idiot when it comes to X11 programming, xfaces.c, and
>> lwlib, so this migh
Stefan Monnier wrote:
The patch below makes the Lucid menu use fontsets to draw its text, so that
it's able to write non-ASCII (the set of chars supported is dependent on the
locale, and of course on the fonts).
I'm very much an idiot when it comes to X11 programming, xfaces.c, and
lwlib, so this m
24 matches
Mail list logo
