FS#44939 - [texstudio] The zero-width non-joiner (ZWNJ) character cannot be inserted when compiled with Qt5

Attached to Project: Community Packages
Opened by Behnam Momeni (sbmomeni) - Tuesday, 12 May 2015, 05:09 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 13 February 2016, 14:23 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
In Persian keyboard, shift+space key inserts zero-width non-joiner (ZWNJ) character.
This works correctly till the texstudio-2.9.0-1 package, in which the texstudio is compiled with Qt 4.8.6.
But since texstudio-2.9.0-2 package, in which texstudio is compiled with Qt 5.4.1, shift+space key does nothing.
BTW, it is possible to copy/paste existing ZWNJ characters in the editor.

All next versions are compiled with Qt5 too and has the same bug.
You can compile texstudio with Qt4 as a workaround.

Additional info:
* package version(s)
Any texstudio version which is compiled with Qt5 is affected. This starts by texstudio-2.9.0-2 package.

Steps to reproduce:
1. Open texstudio and write at least two Persian characters (e.g. لل)
3. Place cursor between joined characters and press shift+space
Expected result (characters must become separated): ل‌ل
Current result (no change at all): لل
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Saturday, 13 February 2016, 14:23 GMT
Reason for closing:  Upstream
Additional comments about closing:  Seems like there's nothing we can do and I don't see any patch either. We're going to have to wait on upstream for this one. No use tracking it, I guess.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 27 May 2015, 10:53 GMT
Can you report an upstream bug against Qt5 and post it here please?
Comment by Behnam Momeni (sbmomeni) - Monday, 01 June 2015, 11:19 GMT
It is reported at <https://bugreports.qt.io/browse/QTBUG-42074>.

Loading...