Paperwhite & footnote pop-ups

[eFTy]

Here is a direct copy paste from one of the books:

prologue.xhtml:

  <p>Sfârşitul culesului vaniliei atrage întotdeauna o mulţime de vizitatori. Sunt negustorii, apoi reprezentanţii reginei, bineînţeles, care vin să stabilească preţurile, dar mai sunt şi cei care vin să vadă zburătorii. Copacul a fost ales, doborât şi aşezat în piaţa oraşului, iar preoţii de toate confesiunile şi-au spus rugăciunile asupra lui, l-au tămâiat şi l-au stropit cu sânge de pui. Funiile au fost încercate şi ultimele amănunte, adăugate la pelerinele cu pene şi bonete. Dorm prost zilele astea şi m-am trezit de dimineaţă înainte de răsărit, bântuită de cântecul îndrăzneţ, singuratic al unui caporal <sup><a href="../Text/footnotes.xhtml#note-1" id="note-1-loc">1</a></sup> , care exersa la flaut sus, pe platforma sa, aplecat sub greutatea cerului şi a vânturilor.</p>

footnotes.xhtml:

  <p class="fn"><a href="../Text/prologue.xhtml#note-1-loc" id="note-1">1</a> - Şef de echipă – în lb. sp. în orig. (n. tr.).</p>

style0001.css:

.fn {page-break-after:always}

If I remove the pagebreak, I get all the footnotes (starting with the linked one) jumbled into the pop-up.

P.S. The language is Romanian, in case anyone's curious.

[Hitch]

Originally Posted by eFTy

Here is a direct copy paste from one of the books:

prologue.xhtml:

  <p>Sfârşitul culesului vaniliei atrage întotdeauna o mulţime de vizitatori. Sunt negustorii, apoi reprezentanţii reginei, bineînţeles, care vin să stabilească preţurile, dar mai sunt şi cei care vin să vadă zburătorii. Copacul a fost ales, doborât şi aşezat în piaţa oraşului, iar preoţii de toate confesiunile şi-au spus rugăciunile asupra lui, l-au tămâiat şi l-au stropit cu sânge de pui. Funiile au fost încercate şi ultimele amănunte, adăugate la pelerinele cu pene şi bonete. Dorm prost zilele astea şi m-am trezit de dimineaţă înainte de răsărit, bântuită de cântecul îndrăzneţ, singuratic al unui caporal <sup><a href="../Text/footnotes.xhtml#note-1" id="note-1-loc">1</a></sup> , care exersa la flaut sus, pe platforma sa, aplecat sub greutatea cerului şi a vânturilor.</p>

footnotes.xhtml:

  <p class="fn"><a href="../Text/prologue.xhtml#note-1-loc" id="note-1">1</a> - Şef de echipă – în lb. sp. în orig. (n. tr.).</p>

style0001.css:

.fn {page-break-after:always}

If I remove the pagebreak, I get all the footnotes (starting with the linked one) jumbled into the pop-up.

P.S. The language is Romanian, in case anyone's curious.

Well...

You got me. Anyone else see anything? Anything not the same as what my company is doing? Or...I wonder. eFTy, have you tried styling the footnote with the same indents we use? Just out of curiosity?

(Oddly enough, I recognized the language; we did a book in Romanian, a while back. I kid thee not!)

Hitch

[eFTy]

Hm, why not? I'll try it on the next book I'm working on right now and post the result, today or on Monday.

[eFTy]

Hitch, I love you.

I don't understand why, but that indent code worked...

Now I have to go through the 50 other books I made and change it.

[Hitch]

Originally Posted by eFTy

Hitch, I love you.

Gosh. I'm glad.

I don't understand why, but that indent code worked...

Hell, I'd rather be lucky than good any day.

Now I have to go through the 50 other books I made and change it.

Oh, dear. Um...on a bright note, it works??????

Hitch

[eFTy]

Yeah, it took less than a day to go through all of them, and definitely less time than I'd spent trying to solve the damned issue.

Now I have a new one - it's about the '&' symbol. If I use & or & I get no errors but the symbol simply doesn't show in the pop-up. If I use &amp;, in the pop-up it doesn't show AND it creates errors on every end tag (like </i> and </p>): ERR: expected: / . Both types of code work we

Any ideas? Right now all I can think of is replacing it with 'and'.

edit: And while I'm at it - I found I can't make pop-ups work if the footnote link is inside a header tag. Any ideas on that?

[kentmatt]

One thing I noticed that hasn't been mentioned in this thread - the difference in behaviour between kf8 (AZW3) and mobi.

I was trying to get the blasted things to work following this thread with no luck. As soon as I converted the file to mobi instead of kf8, it worked fine.

Anyone know if the feature works in kf8/AZW3? If so, how?

[Hitch]

Originally Posted by kentmatt

One thing I noticed that hasn't been mentioned in this thread - the difference in behaviour between kf8 (AZW3) and mobi.

I was trying to get the blasted things to work following this thread with no luck. As soon as I converted the file to mobi instead of kf8, it worked fine.

Anyone know if the feature works in kf8/AZW3? If so, how?

Kent,

I'm sorry--what do you mean? How were you converting a book to "KF8?" Do you mean Calibre?

Hitch

[kentmatt]

Originally Posted by Hitch

Kent,

I'm sorry--what do you mean? How were you converting a book to "KF8?" Do you mean Calibre?

Hitch

Yes - with Calibre. And I examined the coding in the resulting kf8/AZW3 file, and it still seems to follow the above conventions. But conversion from the epub to mobi via Calibre works fine, as I said

[kentmatt]

For reference, here is the original epub code:

^{<a href="9780465004980_Part17.xhtml#lp_B1" id="p_A1">1</a>}</span></p>

Target:

<p><a href="9780465004980_Part11.xhtml#p_A1" id="lp_B1">1</a> Footnote Text Here</p>

And here is the resulting AZW3 code (which fails to work):

<sup class="calibre12"><a class="calibre3" href="part0017.html#lp_B1" id="p_A1">1</a></sup>

<p class="calibre10"><a class="calibre3" href="part0010.html#p_A1" id="lp_B1">1</a> Footnote Text Here</p>

[Hitch]

Originally Posted by kentmatt

Yes - with Calibre. And I examined the coding in the resulting kf8/AZW3 file, and it still seems to follow the above conventions. But conversion from the epub to mobi via Calibre works fine, as I said

Works fine....except your footnotes don't work?

{sigh}. What's the CSS for the classes Calibre12, Calibre3, Calibre10?

Hitch

[kentmatt]

Originally Posted by Hitch

Works fine....except your footnotes don't work?

What's the CSS for the classes Calibre12, Calibre3, Calibre10?

Works fine as in converting the epub to mobi, the footnotes do the 'preview'. Converting the same epub to azw3, the footnotes take me to the footnotes section at the end of the book.

.calibre3 {
text-decoration: none
}

.calibre10 {
display: block;
font-size: 1em;
line-height: 1;
text-align: left;
text-indent: 1.5em;
margin: 0
}

.calibre12 {
font-size: 0.75em;
line-height: 1;
vertical-align: super
}

I removed the classes from the footnote (used just plain <a href> and plain <p> tags - no difference.

I have another book that the footnotes preview works in AZW3 has this formatting:

<a class="hlink" href="part0019.html#c03-nts1" id="c03-nts1a"><sup class="frac">1</sup></a>

<p class="footnote" id="c01-nts1"><a class="hlink" href="part0007.html#c01-nts1a">**1.</a> footnote text here</p>

.frac {
font-size: 0.7em;
line-height: normal;
vertical-align: 4px
}

.footnote {
display: block;
text-align: left;
text-indent: -1.5em;
margin: 0.3em 0 0.3em 1.5em
}

the only difference that sticks out is:

the link has the <a href> tag outside the <sup> tag - not inside, as previously recommended. However, I tried that with the other book, and it did not change the footnotes behaviour.

[Hitch]

Sorry:

I don't use Calibre for MOBI conversions, so I'm not the person to help you. I wouldn't know an AZW3 if it ran over my foot. You might try asking about this on the Calibre forum.

Have you considered simply converting your ePUB with KindleGen? And seeing if your output performs properly? I assume you're doing this for yourself, to have footnotes you can read, as AZW3 is only viable for Calibre and sideloaded MOBIs?

Hitch

[kentmatt]

Originally Posted by Hitch

Have you considered simply converting your ePUB with KindleGen? And seeing if your output performs properly? I assume you're doing this for yourself, to have footnotes you can read, as AZW3 is only viable for Calibre and sideloaded MOBIs?

Gave that a try - same behaviour (ie footnotes don't 'preview').

It would be nice if amazon would document how it needs to be coded in their publishing guidelines!
http://kindlegen.s3.amazonaws.com/Am...Guidelines.pdf

I'll play with the resulting azw file when I have some time and see if I can figure out what exactly it's looking for in order to work.

[Hitch]

Originally Posted by kentmatt

Gave that a try - same behaviour (ie footnotes don't 'preview').

It would be nice if amazon would document how it needs to be coded in their publishing guidelines!
http://kindlegen.s3.amazonaws.com/Am...Guidelines.pdf

I'll play with the resulting azw file when I have some time and see if I can figure out what exactly it's looking for in order to work.

Sorry, I honestly don't know what to tell you. Ours have always popped up, as long as the feature has been available. I don't know why yours wouldn't assuming you're using the exact same formatting that's been discussed in this thread--including the indent.

Hitch