If we could, what one bug would you like to see fixed?

[DNSB]

Originally Posted by treadlightly

And that's why I'm calling it a bug. If the database was corrupted while on a week long trip, my reader would be toast unless I had access to wi-fi or my computer. I would not be pleased.

Hmmmm... given that the last trip I went on, there was WiFi in virtually every restaurant, coffee shop, hotel/motel and even some rest stops, I'm not sure if having to redo my setup over WiFi is that big a deal. Since I keep all my non-Kobo synchronizable content on an external uSD card, the big worry is the time it takes for the bleeping database to be rebuilt once it starts reading the external card.

The other point is that when I am away from home, I don't play as much with my ereader which is what has triggered most, if not all, of my database issues.

At home in the Vancouver area, it's even easier since I registered my Aura HD with Shaw and Shaw Open hot spots are popping up all over -- oddly, in a local Starbucks, the Shaw Open connection to the Vietnamese restaurant 2 doors down gives me much better speeds than the Starbucks connection (4Mbps download vs. 240Kbps download the last time I was in there and tested it -- 3 times since I couldn't believe the original results).

Regards,

David

[DNSB]

Originally Posted by Alastair_S

The bookmark/annotation crashing bug is certainly the most disruptive bug so should be the one that is tackled first.

I'm not so sure about that. The last pass at fixing that bug resulted in remove bookmark/dogear and crash your ereader.

Regards,

David

[davidfor]

Originally Posted by DNSB

I'm not so sure about that. The last pass at fixing that bug resulted in remove bookmark/dogear and crash your ereader.

That's the bug I though Alastair_S was referring to. I can't think of another annotation/bookmark but that was crashing the device in recent firmware. And Kobo have said they have fixed this one.

[DNSB]

Originally Posted by davidfor

That's the bug I though Alastair_S was referring to. I can't think of another annotation/bookmark bug that was crashing the device in recent firmware. And Kobo have said they have fixed this one.

I agree that is the bug he was discussing. I should have written "the last attempt at fixing the annotations bugs resulted in".

The problem, for me, is that annotations have gone from not showing chapters properly for epubs and a fruitless search for methods of removing the AnnotationSortOrder=random directive to crashing when I remove a bookmark. I'm not certain my ereader will survive the next "fix". Things can always get worse.

Regards,

David

[Anak]

Originally Posted by DNSB

My three choices would be:

1. Annotations bug. They seem to work okay with .kepub so fix them with .epub.

2. Fewer regression errors -- the one where they fix a bug and then another bug fix/code change resurrects the older bug. OTOH, I spent much of the Windows 95 beta complaining about the same thing. Some things just don't change.

3. Fewer reproducible bugs surviving through multiple firmware revisions.

Regards,

David

I agree, but would like to add

• font (sub) families bug (embedded fonts). It seems to be fixed in fw 3.8.0 for kepubs. But Gothic and Ryumin for epubs are still 'broken' (on Glo). Kobo is almost there.

[jackie_w]

Originally Posted by Anak

I agree, but would like to add

• font (sub) families bug (embedded fonts). It seems to be fixed in fw 3.8.0 for kepubs. But Gothic and Ryumin for epubs are still 'broken' (on Glo). Kobo is almost there.

Perhaps I'm misunderstanding you, but the firmware has only ever contained the Regular .otf file for both Ryumin and Gothic. So how is this a bug. Surely it could only be 'fixed' by adding the 3 missing .otf files and that's only if they actually exist.

ETA: Those 2 fonts are also an order of magnitude larger than the other built-ins. Maybe this is why the rest of the font family files are missing.

[Anak]

Originally Posted by jackie_w

Perhaps I'm misunderstanding you, but the firmware has only ever contained the Regular .otf file for both Ryumin and Gothic. So how is this a bug. Surely it could only be 'fixed' by adding the 3 missing .otf files and that's only if they actually exist.

ETA: Those 2 fonts are also an order of magnitude larger than the other built-ins. Maybe this is why the rest of the font family files are missing.

FYI, before I posted my previous message I did a recheck.
With kepubs the Ryumin and Gothic fonts displays: reguar, italics, bold and bolditalic. Epubs: only the regular font.

[DNSB]

Originally Posted by jackie_w

Perhaps I'm misunderstanding you, but the firmware has only ever contained the Regular .otf file for both Ryumin and Gothic. So how is this a bug. Surely it could only be 'fixed' by adding the 3 missing .otf files and that's only if they actually exist.

ETA: Those 2 fonts are also an order of magnitude larger than the other built-ins. Maybe this is why the rest of the font family files are missing.

OTF fonts can include bold, italic, bold-italic, smallcaps and much else inside the single file. As far as I can tell, the Gothic and Ryumin fonts also contain a lot more glyphs than the TTF fonts supplied in the firmware making them useful for displaying non-Latin languages. Unfortunately since they are obfuscated, it's not simple to determine exactly what features are included.

Even more sadly, many of the .OTF fonts you find on the Internet are simply renamed .ttf files and not true OTF fonts thogh strictly speaking an OTF font can be in a file with the ttf filetype.

And here I'd better stop before I get into a riff on cubic vs. quadratic Bezier splines and similar items of interest to a very small group.

Regards,

David

[jackie_w]

Originally Posted by Anak

FYI, before I posted my previous message I did a recheck.
With kepubs the Ryumin and Gothic fonts displays: reguar, italics, bold and bolditalic. Epubs: only the regular font.

Well I wonder where they are stored, then? I'm looking in
usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/fonts
and I see only Ryumin.otf and Gothic MB 101.otf. All the other font families have 4 files (even the 2 dyslexic fonts).

ETA: Sorry didn't see DNSB's post before writing this.