View Single Post
Old 08-05-2024, 10:13 AM   #36
ruychi
Junior Member
ruychi began at the beginning.
 
ruychi's Avatar
 
Posts: 1
Karma: 10
Join Date: Aug 2024
Location: Portugal, Europe
Device: Kindle Scribe, Kindle Oasis
Changing Code to (optionally) support <aside>

Hi,
I have been using this plugin, it is fantastic, but there are ate least on my perspective two caveats.

1. It allows a style to be defined for the FOOTNOTE, if it is placed in the current xhtml section, BUT, in case the option is to place it in a new xhtml section, that style (class name for footnote heading) is not respected. We end up with a new xhtml section with a heading not respecting what is defined in the CSS ?!!

My simple suggestion: allow for different heading styles selection (and footnote/endnote heading names) in case of selecting "current xhtml" or "new xhtml".

2. Following what [QUOTE=WiseGuru;4392512] mentioned, in what respects having in ePUB3 with pop-up footnote using the <aside> element, I would also suggest to change the way the footnote is built, or a selectable option for having footnotes built with the the <aside> element.

Code:
<!-- Footnote content with appropriate headers for aside.-->
<aside epub:type="footnote" id="fn2">
  <p><a href="9780061807145_Chapter_1_split_000.xhtml#fn_2">↩</a>This is the content of the footnote. </p>
</aside>
Please note that for my own use of the plugin, I just modified the python script at line 689 for the following, and it works perfectly:

Code:
FootNote='<aside id="'+self.prefs['FootnoteID'] + Ref +'"'+self.eTypeFootnote+'><p class="'+self.prefs['FootnoteClass']+'"><a href="../' + self.textCurrentSection +'#'+self.prefs['HyperlinkID']+Ref+'">'+self.entryPrefixFooter.get() + insertRef+self.entrySuffixFooter.get()+'</a>' + " " +FN+'</p></aside>'
In my humble opinion, it would be just including an option in "Advanced Options" to have "ePub3 Pop-Up via <aside> element".

Cheers.
ruychi is offline   Reply With Quote