Workaround: open in a text editor (or use Perl or whatever), to do find/replace on > . Replace every > with > + carriage return. Save, then open in Oxygen. Note: this *may* cause whitespace issues for you, but should get rid of the Oxygen difficulties. If you control the originating system/code, make adjustments to insert LF/CR (vel sim) after closing tags (or more selectively to control whitespace). Hope this helps, Tom Tom Elliott, Ph.D. (tom_elliott@unc.edu) Director, Ancient World Mapping Center http://www.unc.edu/awmc CB#8110, 5010 Davis Library University of North Carolina Chapel Hill, NC 27599-8110 U.S.A. -----Original Message----- From: oxygen-user-bounces@oxygenxml.com [mailto:oxygen-user-bounces@oxygenxml.com] On Behalf Of Chris Ryland Sent: Friday, May 21, 2004 8:38 AM To: Peter Charles Cc: oxygen-user@oxygenxml.com Subject: Re: [oXygen-user] File Crashes Oxygen 680K all on one physical line--also makes gnu emacs pretty slow. ;-) On May 20, 2004, at 8:03 PM, Peter Charles wrote:
Why does this file crash oxygen 3.0? It just cycles using 99% CPU Opens fine in text editor and IE/Mozilla
-----<CDE/>----- Center for Document Engineering University of California, Berkeley cde.berkeley.edu
<ds12dc00an.b.xml>_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user
Cheers! --Chris Ryland / Em Software, Inc. / www.emsoftware.com _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user