Created attachment 111412 [details] sanitized writer file which exhibits problem. I am unable to extend my file if I place the cursor after the last character in the file. LO complains that the document is read-only, however if I move my cursor along the line one char it allows inserting of chars. I have attached a sanitized file, however the issue is slightly different in that the Number of characters seems to vary from the end of file to where we can start inserting into. This file may have been reviewed with Word, and the reviewer or word I am not sure placed 'ticks' at certain places, which is part of the wingding font.
Hi Rohinton, thanks for the report and the test file! When I open the file in 4.4.0.1 on Ubuntu, do Ctrl+End, I can simply type any text. So if that is what you try too, I cannot confirm. Best, Cor
Hi Cor, I do have some images in the original maybe removing those changed the structure? And yes I see that I can extend that test file too, however when cleaning it still had the problem. However the issue still exists in the original. Here is what I can do. I can mail you the file in question. If you can generate the test case and keep it sanitized you are welcome to use it. If you cannot then you will delete it. Or give me instructions on what to extract from the file/zip and I can post them here. Regards, Rohinton.
Hi Rohinton, So it looks as if you solved the problem, but do not know how ;) There seems to be some content in the original file, that prevents editing at the very last position... It would be good to check with e.g. the Navigator for (read only)sections, or maybe there is a 'locked' image? If you want to have further support, may I suggest that you first try the user support options listed here? http://www.libreoffice.org/get-help/community-support/ You may also send me the file - I can have a quick look. I tend to resolve this issue as WorksForMe, but wait a little more.. Thanks, Cor
Hi Rohinton, Thanks for sending. Indeed there is some Wingdings character at the very end that has "read only" as comment at the status bar. Honestly I would not know how that can be inserted there using Writer, other then cut&paste from else? If you have any idea where it comes from, maybe that helps to find the origin of the problem. But it's definitely not a usual situation. HTH, Cor
(In reply to Cor Nouws from comment #4) > Indeed there is some Wingdings character at the very end that has "read > only" as comment at the status bar. > Honestly I would not know how that can be inserted there using Writer, other > then cut&paste from else? Sounds like that last piece is the important part. What happens in these cases: 1) Delete all of the document content except the last wingdings character? 2) Copy the last wingdings character into a new document? Can you still reproduce the problem in those cases? (if so, please upload a test document) Status -> NEEDINFO
Hi, I tried to reduce this down to single character(s) file. The result did not show the error. I wonder if the xml structure(s) can be verified? I am guessing that the way this got introduced is that my tutor uses word for windows to review my work with that. He highlights valid points with a tick, which is the wingding character being used. I can help with small things however I don't have time until after Feb to put in serious effort.
(In reply to Rohinton from comment #6) > Hi, > > I tried to reduce this down to single character(s) file. The result > did not show the error. Okay, that's useful information. I suggest that you start by taking about half of the items out of the document and saving it as document-name_1, then test it. If you can still repro, then remove half more and save it as document-name_2, retest, and then try again. If at any step your test document does not reproduce the problem, go back one level and remove fewer items/remove items from a different part of the file. Hopefully that will get you to document that you feel is pared-down enough to upload here.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.