Quote:
Originally Posted by DiapDealer
I simply don't see how an extraneous '<' in Code View could survive a save and an open (or even retain the ability to switch from CV to BV) without error messages about xhtml not being well-formed being displayed. Same with deleting a necessary '<' and then trying to switch to Book View. Regardless of Clean Source settings. There should have been error messages long before any crash happened.
|
If you add a ">" while in book view - you get ">" in code view.
If you add a ">" while in code view - you get ">A few hours later..." in book view. No errors switching back and fort and no error during save, then exiting. When I reopened the book the ">" had been changed to ">", but still shows as ">" in book view.
I had failed to delete the complete code during a correction, but didn't see it until much later. The extra character had no adverse effect and was seen as just another character.
Quote:
Originally Posted by theducks
Have you tried using File open (from the menu)?
I have been flipping between books using the 'Recent' list and not triggered a crash (W7 pro x64)
|
I will try using the menu instead of the icons. It doesn't always happen right away. It is always after I finish with one book and switch to the next, but not consistently.
Quote:
Originally Posted by KevinH
Hi,
I am betting his original ecoding used a smart quote for "don't" and got mangled in conversions from latin-1 or windows cp1251 to utf-8 resulting in garbage chars. In the unicode standard there are actually many different chars that look exactly like < and > but do not have the same codepoints.
But on the other hand it could be a real < or > and that would confuse the editor but it should not crash.
This crash also could easily be one of the bugs already fixed or worked around in webkit. I think our best thing is to wait for 0.8.3 and see if that fixes the problem. If so, great, if not, we can try to track it down further getting more info from the Windows crash reporter.
KevinH
|
It wasn't the > causing the crashes. That error was just within the last week or so and the program has been crashing since I installed the 0.8.1 version.
Do you want me to continue to add new information (if any is found) or wait until after the next release and continue testing?