![]() |
#1 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
|
Text semantic in Sigil 2.5.2
So, I'm running into a weird issue here. My ePub has somehow marked chapter 61 with the Text semantic (it shows up in the content.opf at the bottom under guide), but when I right-click my prologue and pick Add Semantics, there is no Text option. Obviously I can edit the guide manually, but how do I do it using Sigil's UI? The Text semantic used to appear in the Add Semantics list.
Some users are reporting their ePubs go to chapter 61 upon first opening the book. Less than ideal... |
![]() |
![]() |
![]() |
#2 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 839
Karma: 2657572
Join Date: Jan 2017
Location: Poland
Device: Various
|
My guess: your EPUB is version 3.0, and the guide is from EPUB2. Just remove the entry with "Text" manually from the guide section.
Or menu Tools > Epub3 Tools > Remove the NCX and Guide |
![]() |
![]() |
![]() |
#3 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
|
Ahh. I see. Yeah, it's an epub3...I have no idea why the guide is even in there. (It was exported from InDesign.) Is there any downside whatsoever to removing the NCX and Guide? Such as compatibility with older readers.
|
![]() |
![]() |
![]() |
#4 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 28,569
Karma: 204127028
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
But if the epub3 in question uses a lot of epub3-only features, there's no real reason to try and maintain backward-compatibility. Last edited by DiapDealer; 07-07-2025 at 01:53 PM. |
|
![]() |
![]() |
![]() |
#5 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
|
Thanks. The ePub itself is pretty vanilla, so maintaining backward compatibility seems worthwhile. I'll see what happens when I remove the NCX and Guide and re-add them using the adjacent menu item.
|
![]() |
![]() |
![]() |
#6 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,760
Karma: 5706256
Join Date: Nov 2009
Device: many
|
Just go to Sigil's epub3 tools and regenerate the NCX and Guide based on the current nav.
|
![]() |
![]() |
![]() |
#7 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
|
Okay, so, what I have determined is that if there are multiple files in the ePub that have the "bodymatter" semantic, the NCX/Guide regenerator takes the last one of these and gives it the Text semantic in the guide. Would it not make more sense to take the first bodymatter item instead of the last one? Or, is it considered best practice to have only one item labeled bodymatter in the ePub file? (Currently, the prologue and all of the chapters are labeled bodymatter.)
|
![]() |
![]() |
![]() |
#8 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,760
Karma: 5706256
Join Date: Nov 2009
Device: many
|
There should be only one place where the body starts. Thus one bodymatter.
|
![]() |
![]() |
![]() |
#9 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,760
Karma: 5706256
Join Date: Nov 2009
Device: many
|
In general you use other semantics for front matter like "Prologue" or something less specific like "Front Matter". Typically a landmark semantic is placed on a specific single file. Some files may get assigned more than one landmark but each should target a separate specific id in that file where that landmark starts.
Things like marking Chapters is unneeded in Landmarks as the TOC lists those and aria-sections can label them if need be. Landmarks are the epub3 equivalent to epub2 guide items where semantic meaning is attached to specific files of interest to the user but those not normally included in a table of contents. Thus enabling a user to easily navigate to them too. Last edited by KevinH; 07-07-2025 at 03:26 PM. |
![]() |
![]() |
![]() |
#10 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 80
Karma: 500000
Join Date: Oct 2011
Location: Utah
Device: iPad
|
Thank you for clearing that up. I'll pass it along.
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Feature request: Semantic italics/spans | noteon | Sigil | 14 | 03-08-2024 02:26 AM |
Semantic markup question! | graycyn | Workshop | 79 | 04-13-2023 05:08 PM |
Typo in Set Semantic ? | Bertrand | Editor | 1 | 04-06-2016 10:24 AM |
text problems Sigil? | ralphiedee | Sigil | 14 | 08-09-2012 04:30 AM |
Semantic formating for simple poetry: any comments on my code? | sourcejedi | ePub | 12 | 04-22-2011 06:28 AM |