Bug 74248 - EDITING: Keyboard entering data low response with Arabic text
Summary: EDITING: Keyboard entering data low response with Arabic text
Status: RESOLVED DUPLICATE of bug 80788
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-30 21:56 UTC by Said Bakr
Modified: 2014-07-11 01:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Said Bakr 2014-01-30 21:56:55 UTC 
Problem description: 
Writing Arabic text leads to jamming of keyboard response on hitting the spacebar. I even tried to stop spell and grammar checking but without any solution for this issue. 
Steps to reproduce:
1. Running Writer to create new document.
2. ALT + Right SHIFT to allow writing in Arabic.
3. CTRL + Right SHIFT to change text direction to be RTL
4. Writing any text quickly.
5. Hitting the spacebar to make space between text.

Current behavior:
The Cursor stop moving and writing and it looks like jammed or stopped for some time (it vary depending on the amount of text entered before hitting the spacebar), after that, spontaneously, it moves again and enter the extra text entered after hitting the spacebar. 
Expected behavior:
It should act like writing the English text.

              
Operating System: Windows 7
Version: 4.1.4.2 release
Comment 1 Yousuf Philips (jay) (retired) 2014-07-11 01:20:17 UTC 
Dear Said,

Thank you for bringing this to our notice. It seems another bug has been reported which is the same and it effects both arabic and asian characters, so i'm closing your bug as a duplicate of that one.

When i investigated the issue, i found out that if i dont install the arabic dictionary, this problem wont arise.

*** This bug has been marked as a duplicate of bug 80788 ***