Pretty Print erases file
Posted: Thu Feb 10, 2005 5:01 am
Hi,
I started using oXygen 5.0 a month ago and upgraded to 5.1 a week ago. I work on a Dell Xeon with XP. At the moment I'm cutting and pasting a bunch of text from html files into an XML file, so I click Pretty Print regularly. Every half hour or so, when I click Pretty Print, it takes forever, and then, instead of pretty printing, it erases all but the first line of code and I get an error message: "premature end of file." I can usually revert to the last saved version of the file, close the program, reopen, and continue. But that's hardly ideal.
Plus, one time, when I saw that the program was getting hung up on pretty printing, I tried to just close it. It asked if I wanted to save. I said yes because the entire 8000+ lines of the file were visible at that point. But what got saved was just that first line!
Has anyone else had this problem/anything similar? I think the problem started when I upgraded to 5.1, but I'm not sure. Before that the program would just get slower and slower, until I had to close and reopen after 3-4 hours.
I started using oXygen 5.0 a month ago and upgraded to 5.1 a week ago. I work on a Dell Xeon with XP. At the moment I'm cutting and pasting a bunch of text from html files into an XML file, so I click Pretty Print regularly. Every half hour or so, when I click Pretty Print, it takes forever, and then, instead of pretty printing, it erases all but the first line of code and I get an error message: "premature end of file." I can usually revert to the last saved version of the file, close the program, reopen, and continue. But that's hardly ideal.
Plus, one time, when I saw that the program was getting hung up on pretty printing, I tried to just close it. It asked if I wanted to save. I said yes because the entire 8000+ lines of the file were visible at that point. But what got saved was just that first line!
Has anyone else had this problem/anything similar? I think the problem started when I upgraded to 5.1, but I'm not sure. Before that the program would just get slower and slower, until I had to close and reopen after 3-4 hours.