Pop-up footnotes - Page 2

davidfor · 12-04-2013, 07:33 AM

Quote:

Originally Posted by tshering

I cannot see that davidfor says this. I take his statement as implying that he first had a certain suspicion in this direction. and did not found supporting evidence.

No, I was just eliminating possibilities.

Quote:

If the problem were related to the font, one would rather expect to see squares or question marks or empty spaces.

How can this explain that anacreon (Aura HD, FW ?), davidfor (Glo, FW 3.1.0) and I (Touch, FW 2.6.1) see the correctly interpreted characters, whereras fxp33 (Glo, FW ?) and I (Touch, FW 3.0.1) see the underlying UTF-8 code. As an additional information: fxp33's test file contains also a Chinese character that cannot be produced by combining characters.

I myself don't have any clue what might prevent the utf8 decoding on fxp33's and my reader.Maybe it is a side-effect of some entry in the configuration file?

It didn't work on my Touch with FW 3.0.1. So, I installed 3.1.0. It worked. That probably means a bug in the display code in 3.0.1 that was fixed in 3.1.0.

DNSB · 12-05-2013, 01:09 PM

Quote:

Originally Posted by tshering

I cannot see that davidfor says this. I take his statement as implying that he first had a certain suspicion in this direction. and did not found supporting evidence. If the problem were related to the font, one would rather expect to see squares or question marks or empty spaces.

The ACCESS renderer seems to look for missing characters in other installed fonts. The issue being is that they tend to be shown at a very small font size. This is different from the RMSDK renderer which will use the squares (blank, X or ?).

When I tried François' test kepub.epub and removed the extraneous toc.ncx entry, the display looked fine with 3.1.0 but the Chinese character showed up as 1/3 the size of the other characters until I switched the font to a font that supported that character (Code2000, Ryumin, Gothic).

Regards,
David

fxp33 · 12-05-2013, 01:39 PM

Hi,

@DNSB: if it is a simple corrupt toc, you are bringing me the best news of the week

Not sure if I changed some settings in Sigil about the table of contents. I will make a few test tomorrow.

@DavidFor: And of course, I will upgrade too

@Tshering: thanks for the support, glad not to be the only one

@Leonatus: Happy to see that you don't have this problem and thanks again for taking time to check for special characters

Regards

François

DNSB · 12-05-2013, 04:03 PM

Quote:

Originally Posted by fxp33

Hi,

@DNSB: if it is a simple corrupt toc, you are bringing me the best news of the week

Not sure if I changed some settings in Sigil about the table of contents. I will make a few test tomorrow.

I noticed that due to my habit of error checking before I transfer an ebook to my Kobo. In the case of your sample, the first entry in the TOC was to a non-existent file. I doubt that would have caused an issue with the pop-up footnotes.

Regards,
David

tshering · 12-05-2013, 04:51 PM

Quote:

Originally Posted by DNSB

The ACCESS renderer seems to look for missing characters in other installed fonts. The issue being is that they tend to be shown at a very small font size.

Right, I should have added "or characters taken from another font, provided one of the installed fonts contains them." The point however I wanted to make was that the display of utf8-code instead of interpreted unicode characters can hardly be related to a problem with fonts.

tshering · 12-05-2013, 04:55 PM

Quote:

Originally Posted by fxp33

Hi,
@DNSB: if it is a simple corrupt toc, you are bringing me the best news of the week

I don't want to prevent your from producing valid formed epubs. However, this problem is definitely a bug of FW 3.0.1.

george.talusan · 12-05-2013, 09:22 PM

Hi guys,

The bug was fixed with 3.1.0 because I read this thread.

Hopefully y'all can take your detective hats off now..

davidfor · 12-05-2013, 11:17 PM

George: I think I'll bookmark your post as proof that Kobo do visit and pay at least a little attention to what we say

tshering · 12-06-2013, 03:52 AM

Quote:

Originally Posted by george.talusan

The bug was fixed with 3.1.0 because I read this thread.

Thank you very much!

fxp33 · 12-06-2013, 06:56 AM

Quote:

Originally Posted by george.talusan

Hi guys,

The bug was fixed with 3.1.0 because I read this thread.

Hopefully y'all can take your detective hats off now..

Thanks a lot George, great, indeed, my popup footnotes works fine after upgrade,

Regards

François

Leonatus · 12-06-2013, 09:36 AM

Quote:

Originally Posted by george.talusan

The bug was fixed with 3.1.0 because I read this thread.

Is this a Kobo Touch specific upgrade? I can't find it anywhere.

Thanks anyway!

tshering · 12-06-2013, 10:00 AM

Quote:

Originally Posted by Leonatus

Is this a Kobo Touch specific upgrade? I can't find it anywhere.

Thanks anyway!

You can find it on the FW thread. I installed it on my Touch, and the foot note bug was gone, however my Touch was no longer able to connect via USB to the pc. This happened twice to me. Davidfor reports that he installed 3.1.0 without problems on Touch.

PeterT · 12-06-2013, 10:04 AM

I seem to recall that one difference between the builds for the different models of Kobo's (old Touch, New Touch for instance) was the driver included for the USB. Is there a possibility that you have an original or B model Touch, and installed the f/w listed for the C modem?

And yes... I realize there is no listed download for the rev 3 f/w.

tshering · 12-06-2013, 10:41 AM

Quote:

Originally Posted by PeterT

Is there a possibility that you have an original or B model Touch, and installed the f/w listed for the C modem?

I installed it on a C model, once only the tgz, once the full package. Davidfor reports that he installed 3.0.1 tgz on N905 and N905B successfully. Jvolbrecht, however, reports the same problem with a C model.

Leonatus · 12-06-2013, 11:52 AM

Quote:

Originally Posted by tshering

You can find it on the FW thread. I installed it on my Touch, and the foot note bug was gone, however my Touch was no longer able to connect via USB to the pc. This happened twice to me. Davidfor reports that he installed 3.1.0 without problems on Touch.

I have here an old Touch (N905), so it should work regularly. But what did you do when connection to PC failed with USB?

I just see that the fw. 3.1.0 is meant for the Glo, but not for the Touch (except, perhaps, for the N905C- mark 4). This has been the reason I didn't find the update for my reader. I think for the N905 it should be mark 3.

12-05-2013, 11:17 PM	#23
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	George: I think I'll bookmark your post as proof that Kobo do visit and pay at least a little attention to what we say Last edited by davidfor; 12-06-2013 at 12:06 AM. Reason: I can't spell

12-06-2013, 10:04 AM	#28
PeterT Grand Sorcerer Posts: 13,530 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	I seem to recall that one difference between the builds for the different models of Kobo's (old Touch, New Touch for instance) was the driver included for the USB. Is there a possibility that you have an original or B model Touch, and installed the f/w listed for the C modem? And yes... I realize there is no listed download for the rev 3 f/w. Last edited by PeterT; 12-06-2013 at 10:12 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Pop-up dictionaries on K4	rebane	Amazon Kindle	6	04-25-2012 11:25 PM
PRS-T1 Keyboard does not pop up for Gmail	ReatTrash	Sony Reader Dev Corner	3	03-08-2012 03:21 AM
How To Create A Pop Star	obs20	Lounge	14	04-07-2011 10:14 AM
Really annoying pop-up ad	RCR	Lounge	3	01-25-2011 06:56 PM
pop up windows	pedz	ePub	7	03-31-2010 12:47 PM

12-05-2013, 01:39 PM	#18
fxp33 Addict Posts: 262 Karma: 110864 Join Date: Mar 2013 Location: Bordeaux, France Device: Kobo Glo, Aura HD, kindle paperwhite	Hi, @DNSB: if it is a simple corrupt toc, you are bringing me the best news of the week Not sure if I changed some settings in Sigil about the table of contents. I will make a few test tomorrow. @DavidFor: And of course, I will upgrade too @Tshering: thanks for the support, glad not to be the only one @Leonatus: Happy to see that you don't have this problem and thanks again for taking time to check for special characters Regards François

12-05-2013, 09:22 PM	#22
george.talusan Kobo Developer Intern Posts: 84 Karma: 253043 Join Date: Apr 2010 Location: Toronto, ON Device: Kobo Touch, Kobo Mini, Kobo Glo	Hi guys, The bug was fixed with 3.1.0 because I read this thread. Hopefully y'all can take your detective hats off now..