|
|
#16 |
|
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,486
Karma: 21099999
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
FWIW:
I agree with KevinH that you should be making the changes in the book for semantic/accessibility reasons. I rarely make changes directly to the ToC file when it is strictly a visual change and I’m too lazy to add the title="" to the <h> tag as I should. For example when the <h> tag has: Thirteen - A Chapter Title That is Too Long I might change it in the ToC to: 13. A Chapter Title That is Too Long The better fix, especially if you plan additional future edits, would be to add the title="" in the tag and let the auto ToC do its job: <h3 title="13. A Chapter Title That is Too Long">Thirteen - A Chapter Title That is Too Long</h3> |
|
|
|
|
|
#17 |
|
Zealot
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 144
Karma: 2000
Join Date: Nov 2025
Device: none
|
It is indeed a better way and good deed to do, sir, but I just don't have the time and effort to do this when I just want to read some random things. I keep high standards on my own project, but it's just not doable for me to be the ultimate hero to correct everything one the Internet, sorry.
|
|
|
|
| Advert | |
|
|
|
|
#18 |
|
Zealot
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 144
Karma: 2000
Join Date: Nov 2025
Device: none
|
Just found out Calibre can do exact what I said. With some minor difference though.
|
|
|
|
|
|
#19 |
|
Zealot
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 144
Karma: 2000
Join Date: Nov 2025
Device: none
|
@KevinH
So do Sigil devs want to look into this? |
|
|
|
|
|
#20 |
|
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 9,676
Karma: 6774048
Join Date: Nov 2009
Device: many
|
Not now, as we are close to making a new release and are just waiting for language translators to have a chance to update their final translations.
But to be clear, I can not see it as something most users would need or want. Plus making the changes in the xhtml source using regex and then regenerating the TOC from the headers is generally the right thing for producing epubs for Accessibility and semantics. So I am not personally in favour of adding that feature. That said, once we reopen a new Sigil thread on new feature suggestions after this next release, feel free to add it there and see if others feel as you so. If more people think that feature has merit, the we will consider it. |
|
|
|
| Advert | |
|
|
|
|
#21 |
|
Zealot
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 144
Karma: 2000
Join Date: Nov 2025
Device: none
|
sure, I will submmit it then
|
|
|
|
![]() |
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Multiple entries of same file | gemgoa | Library Management | 12 | 08-21-2015 12:00 AM |
| TOC Editor: indenting multiple entries | Katsunami | Calibre | 11 | 02-23-2014 01:56 PM |
| TOC Entries from PDF | HamsterRage | Calibre | 2 | 07-12-2010 11:57 AM |
| Bug: entries with multiple formats trigger multiple conversions | flinx1 | Calibre | 12 | 05-21-2010 06:23 AM |