Hi,
On 19 July 2010 15:34, Mark Rogers mark@quarella.co.uk wrote:
On 19/07/10 15:12, Srdjan Todorovic wrote:
Which styles file is this? the one in the ODT or some kind of system style? The ODT style file is some 18000 characters long, and splitting it into lines and checking things will take far too long.
I'm a bit confused, in that I thought you were unable to save the .odt with the problem therefore looking at the styles.xml would be problematic. Was the file saving but then erroring, or are you talking about the styles in the original document (pre-problem)?
The ODT file operated on was pre-problem. This was copied to /tmp and extracted. The original ODT file then developed the problem of not being able to be open by OOo.
Since reboot, the original ODT file can and has been opened by OOo without problems.
If in doubt I tend to view .xml files in something like Firefox that will tell me if it doesn't parse correctly and tell me where it went wrong. (I'm sure there are better tools, I rarely do XML.)
Yes, but Murphy's Law would dictate that Firefox would be taken out ;)
I tried a reboot only, and OOo works fine now. Thanks for helping.
All the more odd! Did you have OOo open for the duration of your tests (eg with other files open)? I don't expect problems to persist between separate program invocations on Linux but still be solved by a reboot. Maybe an update in the background had caused some OOo files to be patched, although restarting OOo should still have been enough.
I had OOo open for the duration of some of the tests. At one point, I had closed all of OOo before finding out that the files still could not be saved.
I don't know about updates - should have warned me about any updates.
Thanks, Srdjan