Bug#825573: [kde-runtime] Compose key not working or not correctly

[Aeris]

> I don't have a guillemotleft guillemotright key in my keyboard, and as 
> mentioned I'm generating it through Compose with Multikey < <. But the 
> generated guillemotleft/right is not being processed again by Compose, so
> the  rules:
> Are unreachable for me (in X/gtk/qt4 and qt5 apps), so I wanted to know how
> you manage to send a  event to Compose. Do you have a
> guillemot key in your keyboard?

I’m using Bepo layout, so I have direct « and » access
https://bepo.fr/

Regards,
-- 
Aeris
Individual crypto-terrorist group self-radicalized on the digital Internet
https://imirhil.fr/

Protect your privacy, encrypt your communications
GPG : EFB74277 ECE4E222
OTR : 5769616D 2D3DAC72
https://café-vie-privée.fr/

signature.asc
Description: This is a digitally signed message part.

Bug#825573: [kde-runtime] Compose key not working or not correctly

[Maximiliano Curia]

Control: retitle -1 "Compose key can't generate multiple characters"
Control: reassign -1 src:qtbase-opensource-src

On Saturday, 25 June 2016 21:53:49 CEST Aeris wrote:
> On Sat, 28 May 2016 11:27:22 +0200 Maximiliano Curia
>  wrote:
> > How do you produce the  so that Compose processes it again?

> "«" and "»" alone never exist in French, always with non breaking space
> before or after, so no need to produce them.

I don't have a guillemotleft guillemotright key in my keyboard, and as 
mentioned I'm generating it through Compose with Multikey < <. But the 
generated guillemotleft/right is not being processed again by Compose, so the 
rules:
 : "« "
 : " »"

Are unreachable for me (in X/gtk/qt4 and qt5 apps), so I wanted to know how 
you manage to send a  event to Compose. Do you have a guillemot 
key in your keyboard?

In any case a simpler version:
   : "Blah"

Produces "Blah" in xterm, but "B" in qt applications, so I guess that's the 
same issue.

> > > Environments variables set :
> > >   QT_IM_MODULE=xim
> > >   GTK_IM_MODULE=xim
> > >   QT4_IM_MODULE=xim

> > I think these variables play no role here.

> Seems xim is involved somewhere in compose process.

Sure, only that the behavior for this particular issue is the same having 
these variable set or not.

Happy hacking,
-- 
"Don't let what you cannot do interfere with what you can do."
-- Wooden's Rule
Saludos /\/\ /\ >< `/


signature.asc
Description: This is a digitally signed message part.

Bug#825573: [kde-runtime] Compose key not working or not correctly

[Aeris]

On Sat, 28 May 2016 11:27:22 +0200 Maximiliano Curia  
wrote:

¡ Hello too !

> How do you produce the  so that Compose processes it again?

"«" and "»" alone never exist in French, always with non breaking space before 
or after, so no need to produce them.

> > Environments variables set :
> > QT_IM_MODULE=xim 
> > GTK_IM_MODULE=xim 
> > QT4_IM_MODULE=xim
> 
> I think these variables play no role here.

Seems xim is involved somewhere in compose process.
See here (sorry, it’s in french :'()
https://bepo.fr/wiki/Compose#M.C3.A9thode_g.C3.A9n.C3.A9rique
And somebody asks me for those variables on #debian IRC channel when helping 
me for my problem.

Regards,
-- 
Aeris
Individual crypto-terrorist group self-radicalized on the digital Internet
https://imirhil.fr/

Protect your privacy, encrypt your communications
GPG : EFB74277 ECE4E222
OTR : 5769616D 2D3DAC72
https://café-vie-privée.fr/

signature.asc
Description: This is a digitally signed message part.

Bug#825573: [kde-runtime] Compose key not working or not correctly

[Maximiliano Curia]

Control: tag -1 + confirmed upstream

The question is, who is upstream for this.

¡Hola Aeris!

El 2016-05-28 a las 00:18 +0200, Aeris escribió:
Package: kde-runtime 
Severity: normal



Compose key has strange behavior in some KDE apps.


For example, I have in my ~/.XCompose 
	 : "« " 
	 : " »" 
	  : "←" U2190 
	   : "ℕ" U2115


I've never used the compose key this way, but I'm partially able to reproduce 
the issue.


To test this bug I've added a ~/.XCompose that reads:
include "%L"

 : "« "
  : "←"


Using the first two, only the first character was printed ("«" or "  ").


I'm using  < < to produce a «, and that is not matched by the 
 rule. So I can't reproduce this problem and the behaviour is 
the same in qt, gtk, x11, etc.


How do you produce the  so that Compose processes it again?

On the 3rd, nothing happens, but the compose key seems loaded and trigger 
strange behaviour on the next key. For example, "Compose" then "↑", nothing 
printed, but pressing "e" after that prints a "∉". And pressing "a" after 
compose sequance prints nothing, and pressing "a" again prints "å".


This one is easily reproduceable, and it seems that the arrow keys are not 
being processed by Compose in qt apps. For instance in kwrite,  
left-arrow a a, starts processing a compose sequence, moves the cursor to the 
left, and then uses a a to complete the compose sequence.


This behavior is only observed in some KDE apps (konversation, choqok, 
kwrite), not on others (kmail) and not on pure QT app (psi, cutecom) or GTK 
app (firefox, pidgin).


I'm seeing the same behaviour in qterminal, (qt5 only), but I see the "←" in 
juk (kde4 based), so I think it's more related to the particular widget being 
used on the qt side of things.



Environments variables set :
	QT_IM_MODULE=xim 
	GTK_IM_MODULE=xim 
	QT4_IM_MODULE=xim


I think these variables play no role here.

Happy hacking,
--
"If it ain't broke, don't fix it" -- Bert Lance
"If we can't fix it, it ain't broke" -- Lieutenant Colonel Walt Weir
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#825573: [kde-runtime] Compose key not working or not correctly

[Aeris]

Package: kde-runtime
Severity: normal

--- Please enter the report below this line. ---

Dear maintainers,

Compose key has strange behavior in some KDE apps.

For example, I have in my ~/.XCompose
 : "« "
 : " »"
  : "←" U2190
   : "ℕ" U2115

Using the first two, only the first character was printed ("«" or "  ").

On the 3rd, nothing happens, but the compose key seems loaded and trigger 
strange behaviour on the next key. For example, "Compose" then "↑", nothing 
printed, but pressing "e" after that prints a "∉". And pressing "a" after 
compose sequance prints nothing, and pressing "a" again prints "å".

Last compose command works as expected.

This behavior is only observed in some KDE apps (konversation, choqok, 
kwrite), not on others (kmail) and not on pure QT app (psi, cutecom) or GTK 
app (firefox, pidgin).

Environments variables set :
QT_IM_MODULE=xim
GTK_IM_MODULE=xim
QT4_IM_MODULE=xim

Regards,

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.5.0-2-amd64

Debian Release: stretch/sid
  990 testing http.debian.net 
  990 testing deb.torproject.org 
  990 stable  deb.torproject.org 
  500 jessie-backports mozilla.debian.net 
  400 unstabledeb.torproject.org 

--- Package information. ---
Depends(Version) | Installed
-+-===
kde-runtime  (>> 4:4.10) | 4:15.08.3-1+b1
libc6  (>= 2.14) | 
libkdecore5  (>= 4:4.11) | 
libkdeui5(>= 4:4.11) | 
libkfile4(>= 4:4.11) | 
libkio5  (>= 4:4.11) | 
libkparts4   (>= 4:4.11) | 
libqt4-dbus (>= 4:4.5.3) | 
libqt4-xml  (>= 4:4.5.3) | 
libqtcore4(>= 4:4.7.0~beta1) | 
libqtgui4   (>= 4:4.8.0) | 
libstdc++6(>= 4.4.0) | 
libx11-6 | 


Package's Recommends field is empty.

Package's Suggests field is empty.
-- 
Aeris
Groupe crypto-terroriste individuel auto-radicalisé sur l’Internet digital
https://imirhil.fr/

Protégez votre vie privée, chiffrez vos communications
GPG : EFB74277 ECE4E222
OTR : 5769616D 2D3DAC72
https://café-vie-privée.fr/

signature.asc
Description: This is a digitally signed message part.