inline ToC via XPath?

[chaot]

Almost right!

But the perfect software we are still waiting for.

Imagine the power/completeness of two 'elephants' unified.

[theducks]

Originally Posted by DiapDealer

Well there you go.

Sorry, but not every feature is going to be mirrored between the two programs. The good news is that one of them does what you want.

Thank you
I like that they do different stuff. I use both.
There was a time when you went into a Retail store and if you did not find your: Style, color, quality level (remember Good, Better and Best), you went to another store (or 2).
Now days it is S O S at every store (or they are just out )

[chaot]

Originally Posted by theducks

A Mini can't haul a basketball team.

Depends! Let them starve long enough and then throw a bone inside. That could help.

So I simply choose to change (using S&R) whatever is the chapter/part title to use H# tags and STYLE those to look exactly the same as they did.

Soon I will show (in another thread) my solution, under the given circumstances, associated with the question for improvements. (what I will do my best that this will hardly be possible). Hope to see you there!

---

Originally Posted by BetterRed

... why don't you ask Kovid where the XPath processing is located in the calibre source, download it, and massage it into a Sigil plugin.

To say it cristal clear (German equivalent: 'Klar wie Kloßbrühe' (engl. 'clear as dumpling broth') - what is very much something else!): You (now) and me know that my specific software skills are rather low - not enabling me to do such a plugin. But: Never say never! I will ask Kovid.

There is no reason why, with due care and forethought, you can't use both editors - as I do.

Of course! As it works out more and more: I have to.

In #9 you say

The Xpath capability found in the calibre editor Toc Editor was created ...

and in #12

I didn't know the calibre editor even did Xpath till the OP indicated it did, ...

Do that fit together!?

---

Originally Posted by theducks

Thank you
I like that they do different stuff.

Even seen from the vantage point of competing suppliers it is advantageous. Also when at least Kovid
enjoy and feel passionate about doing calibre - what I absolute believe him.

Now[a]days it is S O S at every store (or they are just out )

As a mariner I know S O S - most likely you mean something else!?

[Doitsu]

@chaot:
Just to add some background information: some older Calibre versions used non-heading tags and special Calibre classes instead of heading tags to identify epub headings, and if you did epub-to-epub conversions with Calibre heading tags were usually replaced with non-heading tags with special Calibre class attributes.
Since Calibre originally didn't use/support heading tags, it made perfect sense to add XPath support and an excellent, fool-proof XPath wizard for users who are not familiar with XPath queries.
Sigil, however, has always used heading tags to identity headings, which, IMHO, made (and makes) perfect sense.

IMHO, headings should be tagged with h1-h6 heading tags, because that's what heading tags are for and moreover some reading apps for visually impaired readers will use heading tags for navigation purposes. While nothing prevents you from formatting headings with non-heading tags and special class attributes, you'll eventually find out that using heading tags will save you a lot of time when you update a book.

I don't really understand why you want to make your life more difficult by using non-heading tags. Why are you so hell-bent on using non-heading tags and XPath???

[chaot]

I am not anymore 'hell-bent'.

It was just so that I spent some time to figure out that XPath solution. Then starting with sigil (because of the fine inline ToC ID creation there) to get confronted with the non-existence of XPath. That was too much.


Today afternoon I changed already to <hx> tags, got it checked and validated.

@KevinH: Sorry, there is no big MINUS, not even a small one.

[BetterRed]

Originally Posted by chaot

In #9 you say

and in #12

Do that fit together!?

---

Makes perfect sense - on realising I didn't know it existed I went and had a look, and on looking I recollected I'd seen it in the manual, so I went and had a look there.

Then I engaged in some inductive reasoning - Xpath is a feature of Structure Detection in calibre's conversion pipeline- ergo Kovid must have reused it in the editor. I suspect it's also in the separate calibre TOC tool, but I've not looked there - maybe he lifted the whole TOC Tool enchilada into the editor.

Then I posted here - I try to check my facts before I post, habit I picked up as a junior on local paper 50+ years ago, when editors were the gatekeepers over quality, today their role is to push a particular ideology on behalf of their backhander paymasters.

BTW there's a Tutorial on XPath in the calibre manual if your interested.

BR

[Tex2002ans]

Originally Posted by BetterRed

I try to check my facts before I post, habit I picked up as a junior on local paper 50+ years ago, [...]

BTW there's a Tutorial on XPath in the calibre manual if your interested.

Here is a link to that Calibre XPath Tutorial:

https://manual.calibre-ebook.com/xpath.html

PS. I see the local paper 50 years ago taught you nothing. I see you still make the ol' your <-> you're error.

[BetterRed]

Just as you never miss an opportunity to make derision at another's imperfections Ψ²