Red Hat Bugzilla – Bug 619286
[Indic][mail] Backspace is not working if halant [094D] used in TO/CC Field
Last modified: 2013-07-02 21:03:32 EDT
Description of problem:
if write a new mail and put Indic Unicode Characters in To/CC Field (Case where Contact Name is in Unicode (of course Email Address in English)),
Backspace is not working, if halant is in Character.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run evolution in hi_IN locale
2. start write New Mail
3. in TO/CC field type local text or
4. you can copy paste Text (क्पक्ब्न्न)
5. Try to use BackSpace
Text is not deleted completely
it should be removed completely.
Delete is working fine
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Thanks for a bug report. I can reproduce it too, on actual git master, interestingly the gtk-demo's Entry->Entry Completion demo works properly.
Confirming. Reproduced on both RHEL 6 and the latest upstream code.
Fixed upstream in:
Backported to RHEL 6 in evolution-data-server-2.28.3-10.el6.
Hello Matthew, could you please build that package, I'm unable to find it in brew and the latest version in repo is *.3-8.el6.
The fix is in evolution-data-server, not evolution.
status - FIXED
tested package: evolution-data-server-2.28.3-10.el
input for Indic locales working in TO/CC field using halant.
This change has a regression on actual git master, see the upstream bug
Reverting this patch (comment #7) fixes the crash. I cannot test easily with RHEL6, so please test there and reopen if you see the same as I do on git master. Thanks in advance.
(In reply to comment #12)
> This change has a regression on actual git master, see the upstream bug
> Reverting this patch (comment #7) fixes the crash. I cannot test easily with
> RHEL6, so please test there and reopen if you see the same as I do on git
> master. Thanks in advance.
Can you please provide scratch build for this?
(In reply to comment #13)
> Can you please provide scratch build for this?
I meant to test whether the crash from the upstream bugzilla with steps provided there is also reproducible with a package from comment #11. In case it is, then I can scratch-build a package with a patch from the upstream bugzilla.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.