Hi 
You might find much better guidance about all this on the international translators list. They tend to speak/write English almost all the time. I think their address is
L10n@Global.LibreOffice.Org
If you think you have found the cause and that makes it awkward for you then perhaps start a fresh new document and try your theory out. If it makes the new document unable to save and even crashes it then the L10n team might have some better work-around. If it doesn't then chalk it up to "some weirdness" and carry on as before = in which case keep saving fairly often to avoid having to retype hours worth of work.
I tend to find that something that took hours to write first time seldom takes more than 15-20mins because i already know which wrong turns to avoid, which decisions i took and what problems i encountered. Generally i don't directly remember but my fingers seem to know all by themselves.
Regards from
Tom
On Wed, 9 Oct 2013 03:53:14 +0100 (BST)
Tom Davies <tomdavies04@yahoo.co.uk> dijo:
Hi
I am not sure what the problem is but might be able to shed some light
on the error message.
If you create a copy of the file and rename the file-name's ending
from .odt to .zip and then double-click on the .zip then the file
opens in your archive manager. (Ok, so in Xubuntu and most other
Gnu&Linuxes (Linii?) that can be done without renaming the
file-ending. Just right-click and choose "Open With" - "Archive
Manager")
You will now see several .xml files and several folders (such as
"images") inside your file. The number 1 most crucial file is the
"contents.xml", which you can open with a text-editor such as Leafpad.
Somewhere in Leafpad it tells you that the file is open as a "Plain
text" file. Click on that and a drop-down should appear allowing you
to choose different languages and hopefully one of those is "xml". If
you choose "xml" then Leafpad cleverly figures out all the different
bits of xml-coding and colour codes them allowing you to more easily
spot the real text you typed in buried in amongst all the xml coding.
My guess is that somehow Writer managed to get in a muddle and
stuffed-up it's coding somehow. Perhaps a coding bracket didn't get
closed or something else weird. I think i vaguely remember something
like this happening once before in the last 3 years but it's a tad
rare.
Thanks for the explanation. If it happens again I'll try File Roller or
something.
In the meantime, I think I know what caused it. I had been typing in
Greek and suddenly needed a gave accent over an iota. Silly me, I am
new to Greek keyboards and did not realize that the Greek (Simple)
keyboard I was using did not have polytonic diacritics. Being in a
hurry I just used Insert Character and placed a gave accent on the iota
as a combining diacritic. It was shortly thereafter that I discovered
that I could not save the document.
Now, I have been using combining diacritics with LibreOffice and
formerly with OpenOffice.org for many years, and there has never been a
problem. I work in linguistics where I need several dozen different
diacritics that compose keys never heard of. Ctrl-Shift-u is ingrained
into my fingers and I keep a list of the code points at hand. I use a
*lot* of combining diacritics, so if I say there has never been a
problem, I mean the system has always been rock solid. I am a bit
worried that this experience might mean that something has changed and
a bug has been introduced.
And speaking of Ctrl-Shift-u, it doesn't work when the Greek keyboard
is selected. Nor does Ctrl-Shift-upsilon (the u key actually produces
a theta). I had to use Insert Character instead to add my combining
diacritic. I suppose I need to find a Linux help page for Greek users
in order to learn what the equivalent key combination is on a Greek
keyboard. Except I'm just beginning Greek and the instructions would be,
umm ... Greek to me.
![[TEST] Document Foundation Community](https://communitytest.documentfoundation.org/images/discourse-logo-sketch.png){kind=logo}