Mon ebook

[Michel Berger]

Bonjour

J'ai téléchargé PageEdit de Sigil

J'ai mon Ebook en PDF et en Epub

J'ai converti l'ebook Epub en HTML, et il s'affiche n'importe comment.

J'ai besoin d'aide

Cordialement

Michel

[pdurrant]

Google Translate:

I downloaded Sigil's PageEdit.
I have my ebook in PDF and EPUB.
I converted the EPUB ebook to HTML, and it displays incorrectly.
I need help.

Ignore the PDF. PDF isn't intended to be edited.

Open the Epub directly with Sigil.
You don't need PageEdit to edit an Epub, only Sigil.

[DiapDealer]

And even if you did wish to edit the epub with PageEdit, there is no need to "convert" it to html (whatever that might entail) first. Unzip the epub and open the opf with PageEdit. Or set Sigil's External xHTML Editor to PageEdit and launch the external editor from Sigil's menu.

[BetterRed]

I configured Sigil's Book browser->Open with feature to hook Page Edit to OPF files, viz:



I find that easier to access from the keyboard. It's also close what I do in a file manager to open a file in a non-default program - e.g. open a JPG in Paint.

BR

[DiapDealer]

Originally Posted by BetterRed

I configured Sigil's Book browser->Open with feature to hook Page Edit to OPF files, viz:

Attachment 217212

I find that easier to access from the keyboard. It's also close what I do in a file manager to open a file in a non-default program - e.g. open a JPG in Paint.

BR

Does the External Xhtml editor menu item not have a keyboard shortcut (I just checked and it does)? That method does not require setting the filetype (opf) like Open With does. Configure it for the PageEdit binary in the prefs, and hit the shortcut (or menu button), and PageEdit opens with all Xhtml files available for editing. It also opens to the xhtml tab that is currently open in Code View. If the versions of Sigil/PageEdit are new enough, an attempt to place the cursor in the same position is made.

[BetterRed]

Originally Posted by DiapDealer

Does the External Xhtml editor menu item not have a keyboard shortcut (I just checked and it does)? That method does not require setting the filetype (opf) like Open With does. Configure it for the PageEdit binary in the prefs, and hit the shortcut (or menu button), and PageEdit opens with all Xhtml files available for editing. It also opens to the xhtml tab that is currently open in Code View. If the versions of Sigil/PageEdit are new enough, an attempt to place the cursor in the same position is made.

My understanding is that approach was implemented to cater to the users of Book View. Because I never used Book View, I don't use Page Edit as a replacement for Book View. I use PE when copy-editing, proof-reading etc and I only start it from the OPF.

I have two external editors configured for OPF files, PE and the calibre viewer; four for text files (Firefox, Notepad++. Bowpad, and Notepad); three for images; and three for video.

Book browser Open with is perfect for me, I access all 12 variants in exactly the same way… and the only shortcut I have to remember is the one for "Focus on Book browser" - which I have set to Ctrl+Shift+B.

BR

[DiapDealer]

I guess I don't see the difference. Starting PageEdit from the opf in Book View has no advantage to opening it via the the External Editor button/shortcut. You get to exactly same place where you can copy-edit and proofread regardless of the path taken. Just because you never used Book View for anything has no bearing on the fact that you are essentially using PageEdit in the exact same capacity as those who can't live without Book View.

Don't get me wrong... if it's just muscle-memory at this point--I get it. But regardless of who things were implemented for, there is literally no difference in how you're doing it to using the external editor shortcut. The result is identical. Except for the fact that the latter will work without having to make sure Book Browser has focus first.

[philja]

Originally Posted by DiapDealer

I guess I don't see the difference. Starting PageEdit from the opf in Book View has no advantage to opening it via the the External Editor button/shortcut. You get to exactly same place where you can copy-edit and proofread regardless of the path taken. Just because you never used Book View for anything has no bearing on the fact that you are essentially using PageEdit in the exact same capacity as those who can't live without Book View.

Don't get me wrong... if it's just muscle-memory at this point--I get it. But regardless of who things were implemented for, there is literally no difference in how you're doing it to using the external editor shortcut. The result is identical. Except for the fact that the latter will work without having to make sure Book Browser has focus first.

Isn't BetterRed saying that he has his setup that way so that he has a choice of several external editors according to the type of editing he's currently doing?

The external editor shortcut limits use to the same editor unless you re-configure each time. Or have I missed something here?

[DiapDealer]

Originally Posted by philja

Isn't BetterRed saying that he has his setup that way so that he has a choice of several external editors according to the type of editing he's currently doing?

The external editor shortcut limits use to the same editor unless you re-configure each time. Or have I missed something here?

He can keep all of his other external "Open With" editor settings the way they are. No need to change them. Removing the one configured opf editor (leaving the rest intact) and configuring the external editor to be PageEdit would leave him in the exact same position he is now (without needing to make sure BookBrowser has focus before using the external editor shortcut).

There is no advantage/difference to launching PageEdit from the opf using "Open With" over launching the external editor configured to be PageEdit. In fact, there's a couple of quantifiable downsides to the former. It's just a different driveway to the exact same house.

Like I said: if it's a "that's just what I'm used to" thing. I get it. Nothing to explain. But there's no logical justification (or practical for that matter) for continuing to use PageEdit via the Open With feature. Not for the reasons he says he's using PageEdit for anyway.

[BetterRed]

Originally Posted by DiapDealer

He can keep all of his other external "Open With" editor settings the way they are. No need to change them. Removing the one configured opf editor (leaving the rest intact) and configuring the external editor to be PageEdit would leave him in the exact same position he is now (without needing to make sure BookBrowser has focus before using the external editor shortcut).

There is no advantage/difference to launching PageEdit from the opf using "Open With" over launching the external editor configured to be PageEdit. In fact, there's a couple of quantifiable downsides to the former. It's just a different driveway to the exact same house.

Like I said: if it's a "that's just what I'm used to" thing. I get it. Nothing to explain. But there's no logical justification (or practical for that matter) for continuing to use PageEdit via the Open With feature. Not for the reasons he says he's using PageEdit for anyway.

I never argued that 'my way' is better, I presented it as an alternative way of get to the same destination.

If the Book browser isn't shown (for me, it's rarely hidden) then a shortcut (for me, Ctrl+Shift+B) will show it and give it focus.

I'd like to know what the 'quantifiable downsides' are for using Open with for all invocations of external programs on all file types?

There's a Preference setting labelled "Set your preferred external xhtml editor:" — that suggests to me that the feature was never intended to be used on opf files. The corresponding shortcut is labelled "Launch External Xhtml Editor", but I can't see an equivalent in the menu bar drop downs.

Besides which, it doesn't work for me… and I'm pretty sure it never has, just tried again:




When I press F9 with an xhtml file in Codeview nothing happens, i.e. Notepad++ doesn't open. If I select Notepad++ in Open With on the same xhtml file in the Book browser, et voila it opens.

While we're on the topic of Book Browser Open With, there's no way to remove a single program, one can remove all for a type and then re-add the programs you want to keep, or delve into sigil_6.ini and edit it.

BR

[KevinH]

When the external XHTML is set to PageEdit and launched by using the XEditor icon when an xhtml file is being edited in CodeView, it will create a parameter list that specifies a path to the opf file, a spine order number that specifies the xhtml file to be edited, and with the latest versions of Sigil, with add a file cursor position offset to the passed parameters. Sigil then knows to set file watchers on all of the epub's xhtml files so that Sigil knows when and if an xhtml file has been changed by Pagedit and reload them.

PageEdit uses this passed in information to build the list of xhtml files in spine order and identify the specific xhtml file you want to edit. And it will even try to match cursor position from CodeView.

This matching of cursor postion and the setting of file watchers on all xhtml files is only done when using the XEditor, not with Open With. So they do differ.

It does not edit or change the OPF, it just uses it as a way to pass all the paths to the spine's xhtml files including the one currently being edited in CV.

[DiapDealer]

Originally Posted by BetterRed

I'd like to know what the 'quantifiable downsides' are for using Open with for all invocations of external programs on all file types?

We're clearly talking at odds with each other. I've never claimed there are downsides for using Open With for all invocations of external programs on all file types. Only that there are downsides to launching PageEdit on the opf file instead using the External XHtml editor to open PageEdit.

Originally Posted by BetterRed

There's a Preference setting labelled "Set your preferred external xhtml editor:" — that suggests to me that the feature was never intended to be used on opf files.

Neither Open With nor External xHTML editor were intended to be used on OPF files. When you Launch PageEdit on the OPF, it doesn't actually open the OPF, right? It opens PageEdit with all xHTML files available in the drop-down list, to preview, proof-read, copy-edit. That's exactly the same thing that happens when you set PageEdit as the external xhtml editor (by putting the path to the PageEdit binary in the preference setting). Only that way has the advantage of PageEdit opening to the xhtml file that's currently open in Sigil (and with the cursor in the same place it was in the xhtml file open Sigil if you're using Sigil 2.5 or higher).

Originally Posted by BetterRed

The corresponding shortcut is labelled "Launch External Xhtml Editor", but I can't see an equivalent in the menu bar drop downs.

There is no equivalent in the menu dropdowns. It's a toolbar button. I didn't mention it it because you always prefer keyboard shortcuts.

Originally Posted by BetterRed

When I press F9 with an xhtml file in Codeview nothing happens, i.e. Notepad++ doesn't open. If I select Notepad++ in Open With on the same xhtml file in the Book browser, et voila it opens.

What's F9 got to do with it? The default shortcut for launching the configured external xHTML Editor is F2. And if you had the path to the PageEdit binary in the External xHTML Editor box in the Sigil's preference settings, hitting the keyboard shortcut for External xHTML editor would open PageEdit with all the epub's xhtml files available for whatever you want to do with them (with the one already open in Sigil's Code View having the current focus).

But I'm done here. I'm not sure why I'm not being understood, but clearly, nothing I add is helping with that comprehension. So have a nice day. And I'm glad you're satisfied with how things are working for you.

[BetterRed]

Originally Posted by KevinH

When the external XHTML is set to PageEdit and launched by using the XEditor icon when an xhtml file is being edited in CodeView, it will create a parameter list that specifies a path to the opf file, a spine order number that specifies the xhtml file to be edited, and with the latest versions of Sigil, with add a file cursor position offset to the passed parameters. Sigil then knows to set file watchers on all of the epub's xhtml files so that Sigil knows when and if an xhtml file has been changed by Pagedit and reload them.

PageEdit uses this passed in information to build the list of xhtml files in spine order and identify the specific xhtml file you want to edit. And it will even try to match cursor position from CodeView.

This matching of cursor position and the setting of file watchers on all xhtml files is only done when using the XEditor, not with Open With. So they do differ.

It does not edit or change the OPF, it just uses it as a way to pass all the paths to the spine's xhtml files including the one currently being edited in CV.

Thanks Kevin, I get it now.

However - I cannot and never have been able get the external editor to work via a keyboard shortcut (I've tried Windows Safe mode, and nuking Sigil's preferences). And I've tried F9 (because it's next to F8), Ctrl+Alt+E and F2 (after I removed it from Rename**). I'm pretty sure it was yourself or Doug who told me I could the same thing… edit all the text files with Page Edit… by using OpenWith on the OPF file.

I have just discovered I can get the external editor to work with the toolbar button. But I don't make any use of any other toolbars… they're unchecked in View->Toolbars. So I have to ask: Why is there no menu item to do what the button does? IMO: it should be in the Tools menu. Toolbar buttons may be a convenience for abled persons, but the lack of an alternative is an irritant to the rest of us.

BTW: for me F2 for Rename is as ubiquitous as Ctrl+X,C and V are for Cut, Copy and Paste.

BR

[DiapDealer]

To be honest... there is no menu item for launching the external html editor because the toolbar button works for many, and the keyboard shortcut for the external editor seemed to work for everybody else. You are the one and only person I know of who has reported that they can't get the keyboard shortcut for it to work. So it's a bit unfair to suggest we haven't offered an alternative to the toolbar button when we have. The alternative IS the provided configurable keyboard shortcut. I don't know why it won't work for you, but I can assure you that it (the shortcut) works fine for most.