[davidfor]

Originally Posted by Muttly

As I have already stated, I mentioned this problem just in case it was a known bug with a work around.

And as I stated it wasn't a known bug, I was trying to get some details to find out if it was a new bug that needed to be worried about.

Anyone with any in depth experience of software development would look at the description of the problem paying particular attention to the worked then didn't work aspect and, noting that it was a one off, would have surmised that it was a random corruption somewhere along the line.

Yes, you stated vaguely what happened (a reasonable first report) and after a while gave explicit steps. That was very helpful in know what was happening. And of course, I knew it was a once off. After all, I am the person who stated that. But I wanted to know if it was really a once off and if it could be fixed.

Which is why I said I was going to wait for the new firmware and start from scratch. Which would have worked perfectly.

When? In the last post before you actually did something?

Had I reported it to Kobo I would not for one minute expect them to try and solve the problem. I would expect them to suggest exactly what I was intending to do. It would be the only sensible response.



The fact that they worked before is extremely important and your failure to grasp that is what made me think you had little understanding of fault diagnosis.

I had complete understanding of the small amount of fault diagnosis you had done. I was really hoping you would spend a few minutes doing some more.

As explained above, given that and the fact that this is NOT a known problem, I assumed corruption and that some level of system refresh would solve the problem - which it did. As it happened it did not even need the factory reset.

I certainly wasn't going to waste time attempting to diagnose something which I had come to believe was caused by some corruption.



Yes. Note: replaced the font files. Not renamed the font files. Not fiddled around with settings.

IF you were trying to be helpful, and IF it is no surprise to you, why did you not suggest simply replacing the files?

You mean the several times I asked that you check on the font files? And of course in post #775 where I explicitly suggested replacing them? Maybe I should have been more explicit earlier, but as you were so adamant that the idea of a corrupted file was ridiculous, I didn't.

The only reason I didn't do it earlier was because I wasn't that bothered. And the fact that I had to spend so much time trying to get it through some apparently very dense skulls that the fact that the fonts initially worked meant that file names and parameter setting were virtually certainly not the problem in this case.

But, as they stopped working, something had to have changed. And I was trying to work out WHAT had changed. Something you obviously didn't understand.

It was virtually certain it was something in the software, because files do not generally corrupt themselves. At least, not unless there is some hardware failure, which didn't seem to be the case here.

You are right files do not corrupt themselves, something had to do it. I made some attempts early on to explain some possibilities so that you could decide if they were likely to have happened. YOU dismissed these out of hand.

Too late, sunshine.

That's how I've loaded about 20 books onto the Kobo with 100% success.

Goody. But, have you worked out why I made that plea?

Look matey, throughout this "conversation" I have been polite and trying to help. I have been impolite on one, maybe two previous occasions. But, you have been rude, argumentative and unwilling to consider any suggestions. You have cast aspersions on everyone who came into the discussion. Including accusing people of exactly what you are demonstrating.