PageEdit-0.8.0 Released

[KevinH]

I really can not give you red underlines in Preview in Sigil without duplicating every possible dictionary as QtWebEngine uses its own binary dictionary format that does not support ignore, or personal word lists. So until Qt adds those feature, it makes no sense.

There are javascript spellcheck interfaces but they typically use web based dictionaries and hugely mark up the underlying code with extraneous span tags and extra css classes.

As for keeping track of externally changed files you use Sigil's FileWatcher interface. So for the opf being sent out, we would have to enable FileWatching for each file in the spine.

So no ignore or ignore all for either Preview or PageEdit until that capability comes to QtWebEngine which embeds its own spellcheck solutions deep inside.

[BetterRed]

Kevin, the redlining in Preview was a thow-away line - maybe 'tin foil hat' doesn't translate

The lack of Ignore, … etc, make it less attractive, one the reasons I like the list based spell checkers is that I can deal with proper names - e.g. Pavlovna - by ignoring them, or adding them to a book specific dictionary.

I tend to treat the opf file as a black-box. Given my druthers I rather select a content file (text, image, etc) and get the corresponding folder in the Open With program - but I also recall you want to make Sigil's folder structure optional.

BR

[Springbok]

Originally Posted by KevinH

No promises but .... we are thinking about allowing PageEdit to accept on launch an opf or a simple sorted list of file paths in spine order as xml. Then have PageEdit dynamically build a navigation menu, and forward and back keys, so that a user of Sigil could use PageEdit to more easily visually proof and spellcheck the xhtml documents in the spine in sequence without having to go back to Sigil to just load the next chapter.

If a PageEdit user makes any change and then hits forward or back arrows, the user will be prompted to save or discard, and the next file on the list will be loaded automatically (with wraparound at each end of the list).

Would you use a feature like that? With it and the current spellcheck PageEdit has built in it should make final proofing and very very minor edits easier.

Is this worth chasing?

I would support this line of development, it is worth an effort in my opinion.

I basically use PageEdit for final chceck of the edited book i.e. spellcheck and layout (line breaks, line spacing etc.). So this "book preview" feature via PageEdit would be useful and same me some time.

[LorieD]

In theory that should work but there are situations where it's just easier to be able to do the edits in Book View as I see something. For example, I set things up in InDesign to create page/xhtml splits based on chapters but there are often items at the front/back of the book that I want split to new pages/xhtml as well and it's exponentially faster for me to be able to insert the page splits in Book View as I see them rather than having to look for the specific spots in the coding.

I'm looking at Preview now though and see where it may allow some of that since it places me in the coding wherever I click on in the preview. When I've got the time to try out working via Preview, I'll do so but for now I may need to stick with what I know just for time's sake.

[DiapDealer]

I honestly can't think of anything more risky than inserting split markers in Book View. I wasn't even aware someone could do that. If BV were still around, I'd be making changes so splitting at cursor, or inserting split markers didn't work in BV.

And for clarity, are you saying you've never even seen/used Preview before now?

[KevinH]

Actually PageEdit will insert Sigil Split markers but will not split. This gives the user a chance to verify their location via the Inspector, or when back in Sigil CodeView before the split is done.

[st_albert]

Originally Posted by KevinH

No promises but .... we are thinking about allowing PageEdit to accept on launch an opf or a simple sorted list of file paths in spine order as xml. Then have PageEdit dynamically build a navigation menu, and forward and back keys, so that a user of Sigil could use PageEdit to more easily visually proof and spellcheck the xhtml documents in the spine in sequence without having to go back to Sigil to just load the next chapter.

If a PageEdit user makes any change and then hits forward or back arrows, the user will be prompted to save or discard, and the next file on the list will be loaded automatically (with wraparound at each end of the list).

Would you use a feature like that? With it and the current spellcheck PageEdit has built in it should make final proofing and very very minor edits easier.

Is this worth chasing?

I would like to see this as well. It would be great for using Sigil as an e-reader to proof-read books and be able to correct typos on the fly. If I understand correctly.

Albert

[Tex2002ans]

Originally Posted by DiapDealer

I honestly can't think of anything more risky than inserting split markers in Book View. I wasn't even aware someone could do that. If BV were still around, I'd be making changes so splitting at cursor, or inserting split markers didn't work in BV.

I use/d it all the time (in Book View) when working on collections of HTML articles, or when let's say an entire book is in a single HTML file.

It's easier to scroll, spot a chapter heading, click + Ctrl+Enter.

Side Note: When working on HTML imported from a website, you get who knows what kind of HTML mess along for the ride, which makes it sometimes easier to do some steps in purely visual mode, instead of directly in code.

[Turtle91]

hmmm...maybe they could make an app for the iPad/iPhone so I could proofread on the fly there too!!!

[DiapDealer]

Originally Posted by Tex2002ans

I use/d it all the time (in Book View) when working on collections of HTML articles, or when let's say an entire book is in a single HTML file.

It's easier to scroll, spot a chapter heading, click + Ctrl+Enter.

Side Note: When working on HTML imported from a website, you get who knows what kind of HTML mess along for the ride, which makes it sometimes easier to do some steps in purely visual mode, instead of directly in code.

I would never split without checking that the split point was in a sane, wise position within the markup first. And since that involves actually perusing Code View to be sure, there was/is no reason in the world for me to split (or insert split markers) in BV or PageEdit. Of course I very rarely deal with garbage markup (by choice), so "reading" the html is no real hardship for me. *shrug*

[BetterRed]

If I want to split in a WYSIWIG manner, I use the calibre editor Preview tool.

[theducks]

Originally Posted by BetterRed

If I want to split in a WYSIWIG manner, I use the calibre editor Preview tool.

↑ ↑ ↑ ✔


FWIW I used to REGEX S&R the Sigil marker into the book, with Preview pane visible. It draws a HR at the point of impact.
I can also search and COUNT the number of them in place before pressing F6 (some books are so poorly crafted that it takes multiple search terms to find all (most. I seem to always find 1 I missed while reading) of the places needed.

[KevinH]

I have now pushed our first attempt at implementing all this to PageEdit master.

So if you build your own, you can pull from master on PageEdit.

To test it you will need to take an epub and unzip it someplace and then open PageEdit and navigate to the OPF file inside the epub folder.

** IT WILL NOT YET WORK WITH OPF Files via Sigil **

If this change seems to be a real improvement for users when proofing/fixing files, we will then modify Sigil so that an OPF can be used with OpenWith in Sigil and that Sigil will properly set all of the file watchers for all of the files in the spine on launch so all changes made are caught.

FYI: It may have have rough edges since it was thrown together very quickly.
Treat it as Beta software

Also, if this works and we integrate it with Sigil, I can then enable intra-epub links in PageEdit (that go to other xhtml files in that spine).

Feedback Welcome! from those who can build PageEdit on their own and use an unzipped epub with it.

If in the end, people feel it really does not add much value to PageEdit, we can easily revert this change.

KevinH

Originally Posted by KevinH

No promises but .... we are thinking about allowing PageEdit to accept on launch an opf or a simple sorted list of file paths in spine order as xml. Then have PageEdit dynamically build a navigation menu, and forward and back keys, so that a user of Sigil could use PageEdit to more easily visually proof and spellcheck the xhtml documents in the spine in sequence without having to go back to Sigil to just load the next chapter.

If a PageEdit user makes any change and then hits forward or back arrows, the user will be prompted to save or discard, and the next file on the list will be loaded automatically (with wraparound at each end of the list).

Would you use a feature like that? With it and the current spellcheck PageEdit has built in it should make final proofing and very very minor edits easier.

Is this worth chasing?

[BeckyEbook]

Opening OPF file works for me and it's nice option.
Selected files XHTML from drop down list are loading OK.

But... opening of individual xhtml files (from the explorer or from Sigil) has stopped working (blank page).

[KevinH]

Thanks for the feedback. I as focused on the opf approach so I probably broke something. I will look into it.

KevinH

Originally Posted by BeckyEbook

Opening OPF file works for me and it's nice option.
Selected files XHTML from drop down list are loading OK.

But... opening of individual xhtml files (from the explorer or from Sigil) has stopped working (blank page).