Thread: Kobo Bug thread
View Single Post
Old 03-29-2014, 06:13 AM   #435
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by bobb40 View Post
This EPUB demonstrates SVG's "rotate" and "dy"; it displays normally on most EPUB readers, but demonstrates faults of KoboGlo.
It would be a good idea to describe what you think is wrong. That way when someone tests it, they know what to look for. Or if someone already knows something about the problem, they can respond. And it would be a good idea to mention which epub readers you think work correctly.

I tested this on my Touch. The first page displays two lines of text. One is horizontal in the middle. The other is vertical on the right side. But each letter is reversed. I assume there is a problem with this text, but as you didn't describe it, I don't know what. Is the line in the wrong place? Or should the letters be the other way round? Or???

The second page is a mess. The text is all at the top of the page.

I also opened this with ADE. The rotated text reads correctly, but it isn't vertically centred on the page. The second page looks the same as on the Touch.

And I sideloaded as a kepub. I just added the ".kepub" into the name instead of doing the full conversion. Both pages look how I think you mean for them to look. And they agree with what the calibre viewer displays.

I think this means the problem is in the RMSDK. Which means it will be up to Adobe (or whoever maintains it now) to fix. Maybe it is fixed in RMSDK 10.

And yes, I am being obtuse in my comments. But, as someone who has spent a very large percentage of their career fixing software bugs or other problems with computers, I don't want to hear "It doesn't work". I want to hear how it doesn't work and how it should work. And I want to hear that in excruciating detail.
davidfor is offline   Reply With Quote