Thread: 0.6.1 bug
View Single Post
Old 12-03-2012, 08:08 AM   #3
meme
Sigil developer
meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.meme ought to be getting tired of karma fortunes by now.
 
Posts: 1,275
Karma: 1101600
Join Date: Jan 2011
Location: UK
Device: Kindle PW, K4 NT, K3, Kobo Touch
Quote:
Originally Posted by mrmikel View Post
Further one additional bug. Handling of badly formed is inconsistent. Loads but says section 19 is not well formed because of bad character. Get red message at top saying showing up to point of error. Go to code view trying to find, don't see so go back, but can't get to book view to see because it is badly formed.

Located 0x1B using open with to Hex Editor and located it...showed as left pointing arrow.
Problem with text solved.
What do you see as a 'bug' or 'inconsistent'? What you describe seems correct.

Open the file (while in Book View). You get the box warning at the top about the error. Switch to Code View is ok. Switch to Book View and you get the prompt warning that you can't switch until you fix the issue. To see the Book View version again, you can close the file's tab, switch to Book View, then re-open the file (or the book).

As a side note, even though you can still save the file, FlightCrew will point out the same error with the character.

Glad to see you were able to find and fix the invalid character using the Open With feature and a hex editor, but you can also just do a search in Code View for \x1B
meme is offline   Reply With Quote