[davidfor]

Originally Posted by Muttly

No, it has to do with your denial that the Aura One software is very buggy.

Since 'very buggy' would generally be a somewhat relative statement I simply pointed out that I was relating the Kobo to the Kindle, of which I have had several, and on which the only bug I have found if that the reading speed is wrong and inconsistent to a bizarre extent. On the Kobo, however, I can cite a long list of bugs the I have personally found, leading me to the conclusion that this software is buggy and 'unfinished'.

You are right, saying "buggy compared to Kindle" is valid. But, once you have said that, any further reference to that in this particular thread is actually off-topic. I to can list a lot of bugs in the Kobo firmware, and I would bet that my list is longer than yours.

That's gobbledegook in this context. The Kobo rendered two books perfectly well using Bookerly correctly. Then it refused to use the Bookerly regular font and rendered everything in Bookerly bold.

The problem with calling it gobbledegook, is that I bet you cannot reproduce the behaviour. I bet that if you try to get those fonts working again, you wouldn't be able to. Of course, that would require you doing a factory reset, putting the same books on it, adding the fonts in the same way and then reading the same books.

Correct. The fonts are valid. The Kobo is just not handling them correctly.

No, it demonstrates that Kobo is handling differently to the other OSes and applications.

Sorry, I didn't realise how little you know about software.

:r ofl::rof l:

Considering how much my boss is paying me as a software engineer, he is going to be upset when he finds that out.

But, you are telling me that there are absolutely no applications out there that depend on particular file names for their configuration? Particularly their default configuration. And there are no applications that create a bunch of files with particular file names and extensions so that they are grouped together and the application knows they are to be processed together. Or that parse the file name to work out the purpose of the file. Maybe it is lazy, old code or something else, but there are plenty of applications in the real world that do this.

Please, I beg you, do not use calibre with the Kobo devices.

Yes, of course individual files have significant names. What no decent software does is try and tie multiple instance header containing file contents with their names. There is absolutely no point in doing that. The name of the typeface is the name in the header file.

Yes, it is probably better not to do this. But, the fact is that the Kobo firmware works that way. NOTHING you can do will change that. If you do not put the fonts on the device in the way the firmware expects them, THEY WILL NOT WORK.

I said: (P #758)

"Well, yes, the format is obviously important, but it's well defined and the files work perfectly well in Window's application. 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."

And I say, who cares about how the Windows application works. The Kobo firmware has requirements about the files that are sideloaded to it for it to use. If those requirements are not met, then you cannot expect things to work correctly

I said: (P #733)

"Secondly, it seems to have 'lost' a font. I loaded Bookerly, and used it quite happily to read a couple of books, then, when I started the next, the whole thing displayed in bold. I assumed it was a problem with the book, and soldiered on, but when I finished it, I discovered that all books displayed in bold only, and had to change typeface to get a normal weight."

As you seem to be having problems, let me guide you through it in simple steps. Then you may understand why I am all but certain it is not a problem with the font files:

1) USB loaded fonts onto Kobo
2) Ejected Kobo
3) Kobo says it is processing
4) New fonts appeared correctly
5) Read two books with new font with no problems whatsoever
6) Without any intervening connection to a computer, started a new book
7) New book displayed in bold
8) All books, including the two I had already successfully read now display in bold.
9) Did a hard restart
10 ) Problem remained.
11) Deleted one of the books I'd read successfully.
12) Current situation, ALL books display in bold when using Bookerly. (To spell it out, yes, that includes the one that initially displayed correctly.)

Good. We know the order of events that happened and what is still happening. It is always nice to have it concisely summarised like this after the discussion that has taken place. But...

Are the font files named properly on the device? Are they in the correct directory?

No, because all you are doing is demonstrating that you don't really understand the intricacies of a file system - or where the file system is used and where main memory is used.

Well, I have never claimed to have a great understanding of the intricacies of file systems. These are things I like to leave alone unless something goes wrong and I need to recover files. Then I dig up the tools I need, check my memory and maybe read a bit, or walk over to a colleague who thinks these things are fun and ask for help.

But, I will claim to know a lot about how the Kobo devices work, how they use the internal storage, how they use the memory, how they read and process the various files that we put on the device. I don't claim to know everything, as I don't have access to the source code or design documents. But, if I stated that I know more about how they work than most posters here,

But, I am answering your question. You stated:

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 gave you a list of things I either know are happening or can guess that are. Several of those things could cause a problem like you describe. But, they would be unlikely to survive a restart. Which is why I asked earlier if you had restarted the device at appropriate times. And of course, if the software finds a problem processing a file, it could of course move/rename/delete it to prevent reprocessing the file later and having exactly the same problem later. I have no idea if this is the case, but it is a possibility.

Let me restate my last paragraph from my last post:

I am not denying you are seeing a problem. All my posts have been about working out what that problem is. The issue to me is that you are the ONLY one reporting the problem. That makes it hard to work out what is actually going wrong. So I have been trying to understand what is happening ON YOUR DEVICE. With a clear understanding of that, maybe someone else can reproduce the problem, and we can see if there is a suitable workaround until the bug is fixed. And, you can make a clear report of the bug to Kobo so they can fix it.

So, to make clear what I want to know:

- Are the font files on the device correctly named? And contain what they supposed to contain?
- Have you tried reinstalling the font files? This is to check that the files on the device haven't been corrupted somehow.

And most importantly of all:

- Have you reported this to Kobo so that they can fix the problem?