PageEdit-0.8.0 Released
 

PageEdit-0.8.0

For the impatient, the binary files (and source) can be found as assets at the bottom of the PageEdit Github Release page.

PageEdit-0.8.0 is is primarily a new features release.

The major new features include the addition of Find and Spellchecking. In addition, the user now can set Preferences to determine how they would like to handle how PageEdit handles sequences of whitespace by either injecting non-breaking spaces (the default) or setting styles to use white-space:pre-wap.

In addition by setting the environment variable "PAGEEDIT_ENABLE_WORD_PASTE_CLEANUP" to 1 will enable extra cleanup code during Save that will remove much of the cruft leftover when pasting formatted text from Microsoft Word into PageEdit. This feature is experimental and can remove both xhtml comments and remove any style tags used in the body (not head!).

Here is a more complete list of the changes:

New Features

• add user preferences to control use of white-space:pre-wrap vs nbsp chars
• add user preferences to set spellchecking dictionary
• add SpellChecking capability for QWebEngine Dictionaries
  (.bdic modified version of Hunspell dictionaries)
• add Find capability (no replace just as in BookView)
• allow cleanup after paste from Word during Save using
  environment variable:PAGEEDIT_ENABLE_WORD_PASTE_CLEANUP
  Note: risky since it removes style tags that are in the body and all xhtml comments

Bug Fixes

• remove spurious newlines in injected user stylesheets and controls (Thanks BeckyDTP!)
• actually compare source to detect all changes
• fix macOS specific bug that allowed multiple Dockwidget MainWindows to become tabs

How to install additional spellcheck dictionaries
 

PageEdit only comes with spellcheck dictionaries for English, French, German and Spanish.

To install additional PageEdit spellcheck dictionaries:

1. Close all PageEdit instances and visit the Chromium hunspell_dictionaries website.

2. Download the .bdic dictionary file for the language that you want to install. For example, it-IT-3-0.bdic for Italian.

3. Copy it to the PageEdit qtwebengine_dictionaries folder.

Well done. This spellcheck function in PageEdit is really nice.

Now, one can limit spellcheck to single file level if required (this option is missing in Sigil as browsing though the codeview window for spell errors is not the same).

It would be even more beatiful if there was a functionality to extend these installed dictionaries with user defined words. Such thing may be not that important for english speaking users but when you often deal with translated ebooks than it becomes very handy. Just a small wish for future...

Where can I read what is PageEdit and what is it for?

Have you tried looking at the main readme for the PageEdit github repo linked to in all of the PageEdit release notices? https://github.com/Sigil-Ebook/PageEdit

No, I looked at the link given in the first post (https://github.com/Sigil-Ebook/PageE...ases/tag/0.8.0).

Any chance that Page Edit will automatically refresh when changes are made in the coding? I don't see a function anywhere in page edit to allow me to refresh.

Also - it would be helpful if there weren't a delay when I try to open Page Edit and if opening each new xhtml file didn't require opening another new window. I've got way too many windows open already on multiple screens so adding more windows to my workflow is really not helpful.

I've been using Sigil for years now - I'm a book designer who does ebook conversion CORRECTLY. I actually do know HTML and use it to clean up what InDesign does. I specialize in making beautiful and functional ebooks to match the print books that I produce for clients.

So I'm not afraid of the coding. I really love it, but I am a visual person and really need to be able to verify quickly that my coding adjustments have rendered the desired results.

For now I'm reverting back to 9.14 since I can't afford to slow down my workflow. Hoping that Page Edit will continue to get better and that I'll be able to make the shift eventually though. I'll keep checking back.

Have you tried coding in xhtml and using Sigil's built in Preview window to visually see what you have changed in real time?

I agree. If you're primarily using Code View to make your edits. Just use Preview to see the live changes. No need to use Book View or PageEdit for that sort of thing. Just park Preview on a second monitor and visualize to your heart's content. Book View and Preview are both primarily for people who want/need to edit in a wysiwyg environment.

Viz:

Attachment 172908

I never used BookView, because I don't use button bars I never 'got' why it even existed for the first few years I used Sigil.

The best thing about Page Edit is that it now shows any misspelt words via red underline (I wish Preview had that) - it also gives me a resizable window I can play around with, without disturbing my editing layout.

BR

BR - do you have a 2nd monitor setup?? I have been undocking the preview window and putting it there....it provides a resizable window AND allows more landscape for code-view.

Spelling - Is that what all those red lines are for?!?!?!?!?:eek::eek::eek:

My second monitor does far more important things that piss-farting around with epub editor windows, like watching stock prices soar one day and tumble the next, but even more important than that - watching the Aussies whitewash the Poms in the Ashes :rofl:

Added: my main monitor is 24" 2560x1440, apart from video I never have anything full screen, don't like editing in wide windows.

I'll only break out to PageEdit intermittently for a short periods to get an inkling of what something looks like in a small window when I have text flow around tables and pictures etc. Because it's new its a bit of a novelty; so I'm probably doing it more than I ought. I like the red underlining of misspellings, which is something I've long yearned for in Preview (hint, hint to all epub editor developers).

BR

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?

Thinking about it from a non-Sigil dependant epub developer tool, if someone unzipped an epub and navigated PageEdit to the opf, it should be able to build up its own ordered list of xhtml file paths in spine order quite easily using a QXmlStreamReader like we do in Sigil.

So having this capability in PageEdit makes sense in the long run anyway.

I think you'd need to add Ignore, Ignore all, and Add to dictionary to the misspelling context menu.

Some users prefer to have a list of misspellings - there's a thread somewhere in which it was discussed, a consequence of which was that Toxaris developed something similar to Sigil's spell checker for his Word Add-in.

This maybe germane:

Attachment 172940

The Bowpad and Notepad++ instances were started by Sigil's Open With.

FWIW the tree in Bowpad can be turned on an off a'la Sigil's Book Browser, its a bit more awkward in Notepad++, you have to open the folder, rather than a file in the folder.

There maybe reasons, other than proofreading, that would make the ability to PageEdit multiple files in the same instance attractive.

Curious - how would Sigil keep track of which files PageEdit changed. At the moment if I open chapter01.xhtml in Bowpad, make changes, save, then open chapter02.xhtml, make changes and save, and then exit Bowpad; Sigil will only pick-up the changes I make to Chapter01.xhtml. That's okay, 'cause that's what's written on the tin - but if there's to be a multi-file PageEdit, why not multi-file any Open With?

I'd rather have red underlines in Preview https://www.mobileread.com/forums/pi...pictureid=6872

BR