Writer gets very slow when typing footnotes. I need to wait an average of one to two seconds for each letter to appear as I type. The situation gets worse when I type in Chinese and use Zotero to add citations.
Typing in the main document section does not present the same problem.
Can you please provide us with the version of libreoffice that you are running and possibly a sample document where you see this behaviour happening.
Created attachment 102329 [details]
Sample of document on which problem occurs. The original document is 13 pages with 39 footnotes.
I am using Liberoffice ver 22.214.171.124
I didnt notice any problems typing english, but noticed some slowness typing arabic in the footnote. But then i opened a new document and typed in arabic there and also noticed the typing was slow. So is the typing slow even when not in the footnote?
At was reasonably faster when typing on the main document. I would not ssay that was 'slow', but the lag was tolerable.
Also, the full-width punctations in Chinese do not align properly, which makes the document look ugly. I don't know whether this is apparent in Arabic as well.
Will be filing another bug report for this issue.
Did some more testing and i see that whenever i press space bar, there is a delay to show the next word's letters. Tested it on Windows as well and it has the same issue, as i thought it might only be Linux only. Also thought it might be font related but it was the same when i used Tahoma or Droid Arabic Nask. Also thought it was AutoSpellcheck related, but disabling that didnt change it.
Steps to reproduce:
1) open writer
2) switch to arabic or asian keyboards
3) type random words quickly
@suokunlong: can you check if this happens with you as well in chinese.
Yes, it does.
Forgot to mention that if i type in arabic on libreoffice which doesnt have the arabic dictionary, it will type quickly, but if the dictionary is available it is slow. But from what i can see, there is no chinese dictionary, so i dont know why this would be effecting CJK typing.
*** Bug 74248 has been marked as a duplicate of this bug. ***
Added the font issue Bug 81272 as see also.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)
If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword
Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa
Thank you for your help!
-- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20
I assume the report was closed because the issue is gone.
Adjusting status to WORKSFORME, since the commit fixing the issue is unknown.