OK, moving from frustrated to mad
Dec. 12th, 2012 07:42 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
hrjI've been getting a lot of use out of doing my daily writing in Quickoffice on the iPad, accessing my files via Dropbox. Mostly it works wonderfully. But every once in a while, something gets corrupted. The current error message is "illegal xml character", which I think has been the message on previous occasions. And then I can't open the file for love or money, not in Quickoffice, not in Word. Peculiarly enough, I can view the entire file without problems using Apple's "spacebar preview" function.** (Thus resulting once in a very annoying session of re-typing an entire file from the preview display.) Oh, and I can open the file in nuts-and-bolts text editors like Text Wrangler -- I just haven't figure out how to use that to identify the problem and repair it. A certain level of safety net is also provided by my regular drag-and-drop backups of my Dropbox contents to my hard disk.
Once, I thought the problem happened because I tried to save and close a file when I was going through a wireless dead zone. (The stretch between the Rockridge and Macarthur stations on BART, for some unknown reason, is totally dead.) So I've learned that if I get a save error, I just save a local copy on the iPad and copy it over to Dropbox later. But this time, the last time I was editing the file, it was on my laptop while at the coffee shop (but not connected to wifi -- just editing the resident copy of the Dropbox file). And I've done that any number of times without having later problems with the file.
Taking a look at the raw code in Text Wrangler, the only thing I've noticed so far (other than the annoying messiness of the seamy xml underbelly of the file) is that some of my apostrophes are ascii characters and some are the xml encoding "'". But both of those should be valid xml characters.
Hmm, and there's something displaying as an o-umlaut when perhaps it should be the xml code for that? But I composed that part through Word, not through Quickoffice. So if it's the problem, then the problem is that Word is saving characters that it later refuses to recognize? Or is all this irrelevant and the invalid character is something else entirely?
In any event, the problem isn't the specific invalid character but the problem that, at unpredictable intervals and for no obvious reason, Very Important Files are becoming corrupted resulting in an annoying amount of work to reconstruct them. And if it's the Quickoffice/Dropbox interface that's causing the problem, then all the workarounds will be annoying. (E.g., do all my active editing on resident files on the iPad and then copy back and forth to edit them on the laptop ... and to back them up.) I've been Googling keywords describing the problem but haven't turned up anything useful yet. (Or any indication that this is a problem other people are having.)
**ETA: Actually, no. I can view up to the next-to-last sentence in chapter 1. And the code immediately following that shows absolutely nothing out of the ordinary. So I'm back to having no clue what the illegal character is. But now between the preview and being able to crack the raw code in Text Wrangler, I've reconstructed the most recent version of the file. Honestly, I'm beginning to wonder whether I should write my working drafts in rtf instead. It would help if I knew where the corruption was coming from.
Once, I thought the problem happened because I tried to save and close a file when I was going through a wireless dead zone. (The stretch between the Rockridge and Macarthur stations on BART, for some unknown reason, is totally dead.) So I've learned that if I get a save error, I just save a local copy on the iPad and copy it over to Dropbox later. But this time, the last time I was editing the file, it was on my laptop while at the coffee shop (but not connected to wifi -- just editing the resident copy of the Dropbox file). And I've done that any number of times without having later problems with the file.
Taking a look at the raw code in Text Wrangler, the only thing I've noticed so far (other than the annoying messiness of the seamy xml underbelly of the file) is that some of my apostrophes are ascii characters and some are the xml encoding "'". But both of those should be valid xml characters.
Hmm, and there's something displaying as an o-umlaut when perhaps it should be the xml code for that? But I composed that part through Word, not through Quickoffice. So if it's the problem, then the problem is that Word is saving characters that it later refuses to recognize? Or is all this irrelevant and the invalid character is something else entirely?
In any event, the problem isn't the specific invalid character but the problem that, at unpredictable intervals and for no obvious reason, Very Important Files are becoming corrupted resulting in an annoying amount of work to reconstruct them. And if it's the Quickoffice/Dropbox interface that's causing the problem, then all the workarounds will be annoying. (E.g., do all my active editing on resident files on the iPad and then copy back and forth to edit them on the laptop ... and to back them up.) I've been Googling keywords describing the problem but haven't turned up anything useful yet. (Or any indication that this is a problem other people are having.)
**ETA: Actually, no. I can view up to the next-to-last sentence in chapter 1. And the code immediately following that shows absolutely nothing out of the ordinary. So I'm back to having no clue what the illegal character is. But now between the preview and being able to crack the raw code in Text Wrangler, I've reconstructed the most recent version of the file. Honestly, I'm beginning to wonder whether I should write my working drafts in rtf instead. It would help if I knew where the corruption was coming from.
