Github messages for voidlinux
 help / color / mirror / Atom feed
From: imapproxy <imapproxy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] GIMP: Chinese unable to be input within the text tool
Date: Sat, 30 Mar 2024 12:29:29 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49605@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

New issue by imapproxy on void-packages repository

https://github.com/void-linux/void-packages/issues/49605

Description:
System info: 
Void 6.5.13_1 x86_64 GenuineIntel uptodate FFFF
xfce desktop (glibc), system all updated.

GIMP info: 2.10.36_1

Input method: 
ibus-rime-1.5.0.1 in ibus 1.5.28

Actual behaviour: 
Chinese not able to be input within GIMP text tool.
Seemingly ibus-rime not triggered, as no response/effect to the switch between English and Chinese.

Expected behaviour:
Chinese can be input within GIMP text tool.
ibus-rime works normally in GIMP like elsewhere in the system. 

Does it exist in other distros?
At least not exist in Artixlinux, EndeavourOS.
GIMP works well with Chinese input in both the distros.

Does it exist for other non-english input methods in ibus?
At least not exist for Arabic and Russian in ibus, not all methods tested. 
Tried typing a few characters in GIMP text layer, the Arabic/Russian characters appeared in success.

Hi , not sure if it is a bug, but it's an itch that cannot be got rid of in daily use.
Much obliged if it be resolved.

             reply	other threads:[~2024-03-30 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 11:29 imapproxy [this message]
2024-03-30 21:32 ` GIMP: ibus-rime not work in " oreo639
2024-03-31 11:27 ` [ISSUE] [CLOSED] " imapproxy
2024-03-31 11:27 ` imapproxy

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49605@inbox.vuxu.org \
    --to=imapproxy@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).