From: Eli Zaretskii <eliz@gnu.org>
To: Yichao Yu <yyc1992@gmail.com>
Cc: wengxt@gmail.com, 10867@debbugs.gnu.org
Subject: bug#10867: 26.3; XIM preedit/status font handling
Date: Sat, 08 Aug 2020 11:00:19 +0300 [thread overview]
Message-ID: <83bljl7ejw.fsf@gnu.org> (raw)
In-Reply-To: <CAMvDr+SOkjexcBgeiFbmU+Tb9XXgG=zmMmc4b=UK+2Dpcvcbrw@mail.gmail.com> (message from Yichao Yu on Sun, 2 Aug 2020 16:07:26 -0400)
> From: Yichao Yu <yyc1992@gmail.com>
> Date: Sun, 2 Aug 2020 16:07:26 -0400
> Cc: Xuetian Weng <wengxt@gmail.com>
>
> > ## What other programs do
> > * xterm seems to use "fixed" to lookup font
> > * qt4 https://dreamswork.github.io/qt4/qximinputcontext__x11_8cpp_source.html
> > AFAICT uses different fonts?
> > * gtk I don't actually see where it set fonts...
> > @Xuetian Weng dug deeper into this
> >
> > ## Fix
> > I'm not sure what's the correct one. It seems that setting the fontSet
> > is necessary although I'm not sure how/if gtk get away with it.
> > According to @Xuetian Weng virtually no one use this setting anymore
> > so setting a dummy value to comfort xlib might be good enough? It
> > would avoid both issues at the same time.
>
> And since it's basically a useless setting at this point, this fix seems to work
Thanks. Can someone with access to a system with this issue and
sufficient knowledge of what's going on please review this patch?
TIA
next prev parent reply other threads:[~2020-08-08 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 11:41 bug#10867: 23.4 must export LC_CTYPE to zh_CN.UTF-8 or similar CJK locale to use X input method Weng Xuetian
2020-08-02 19:03 ` bug#10867: 26.3; XIM preedit/status font handling Yichao Yu
2020-08-02 20:07 ` Yichao Yu
2020-08-08 8:00 ` Eli Zaretskii [this message]
2020-08-21 4:53 ` Yichao Yu
2020-10-07 4:20 ` Lars Ingebrigtsen
2020-12-28 3:19 ` Lars Ingebrigtsen
2020-12-28 3:26 ` Yichao Yu
2020-12-28 3:28 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bljl7ejw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10867@debbugs.gnu.org \
--cc=wengxt@gmail.com \
--cc=yyc1992@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).