[davidfor]

Originally Posted by Muttly

All I was saying was that, compared with the Kindle, the Kobo is very buggy.

And the fact a Kindle has different bugs to a Kobo has absolutely nothing to do with this thread.

Sorry to say it but that's just daft! The point was I mentioned it before you said I didn't.

And I was pointing out that my phrasing was bad and that you hadn't PREVIOUSLY pointed this out.

Yes, and the fonts were used 'properly' for two entire books.

Or possibly they were not "properly" used but just looked like they were.

Well, yes, the format is obviously important, but it's well defined and the files work perfectly well in Window's application.

And as it is unlikely that the Kobo device shares code with any Windows application, and probably loads and uses the fonts in other ways, then whether it works elsewhere is only important in demonstrating the fonts are probably valid.

And the bit the automatic quoting didn't handle this bit:

[see what I mean about buggy? I've never come across any other piece of software that give a hoot what the file name is (extension, maybe but that is deprecated, now)]

Really, not application that cares about file names? That's BS. I have plenty of applications that care about the file names they are using. Anything that uses a DLL cares. Or the various configuration files.

They also worked perfectly well for two books on the KOBO. Indeed, one of them still works, it's just that it's picking the wrong weight.

Sorry, is the font working or not? Is it working for one of those books or not? Your phrasing doesn't tell me whether the font is working but wit the wrong weight for all books, or for one of the books it initially worked on.

Woops. I missed putting in the negative when I fiddled with some phrasing as I wrote the post.

Of course not, but given that they worked perfectly happily for about 700 pages it looks to me as if there are not any issues with the files. The fault appears to lie with the Kobo.

And as it is unlikely that the Kobo device shares code with any Windows application, and probably loads and uses the fonts in other ways, then whether it works elsewhere is only important in demonstrating the fonts are probably valid. What the Kobo software does, or one of the library it uses

Well, crashing is not 'forcing a restart'. It's the device responding to a BUG from which it cannot recover.

Well, a crash that causes a restart is a "forced restart", but I wasn't really meaning that. I was mainly giving another example of how the file system could get into a dirty state and have to be fixed.

As for holding down the power button (which, incidentally, I did not do), I'm not sure how much you know about software and how it functions, but I would be intrigued to know what you think the Kobo could be doing, internally, for 20 seconds between finishing one book and starting another - that would leave the font files present but somehow stop the device using them properly.

I'm not sure why you ran those two things together as they have nothing to do with each other. The "holding the button down" is about forcing the device off in such way that could cause file system corruption. If you haven't done that, then good as it eliminates a possibility.

As I don't have access to the source code, I have no real idea what the firmware is doing between books. I do know it is updating the database in several ways, it's closing the first book and hopefully clearing memory properly, it's showing you the list of books that you might want to read which means it is either reading the cover image from the "disk" or the cache or generating them (depends on the book type, whether they are on the disk, or in the cache), formatting the list for you, opening the book, formatting the new book...

Should I go on?

Which one of those steps failed, I don't know. But, apparently one did and the fonts are not being used properly.

(BTW, before you suggest it, copying the files OFF the Kobo and installing them on Windows, they work perfectly.

But, are they properly named on the device? If they are you have a bug. If they aren't, you have a different bug.

That's nice to hear.

Let's just hope that all these bugs disappear when the new firmware is released.

Yes, hopefully bugs will be fixed in the next firmware. Have you reported these problems to Kobo? If you don't they won't be able to fix them as they might not know about the bug.

And one thing to be clear about here, I am not saying that bugs do not exist in the Kobo firmware. But, you are describing a bug that NO ONE else has reported here. Lots of people here use sideloaded fonts with no problems. If only you are seeing a problem, that suggests that it is something about your setup that is the problem. Or is important in triggering the bug. It might be the font, the books, or something else I can't think of at the moment. I know I can't reproduce it, but I don't have the same fonts and books.