Quote:
Originally Posted by PeterT
Don't you understand.... In order to tie into the STANDARD Adobe DRM infrastructure you HAVE TO USE RMSDK.
|
First I would like to point out that I have bolded the text in your quotes that is coming across rude. If that was not the purpose then I am sorry for bringing it up but on appearance you seem to be aggravated at the fact I am pointing out flaws of Kobo's firmware and Aura device. I am not bringing up these issues to aggravate anyone but to just get them out there and discuss them. There is zero need for the discussion to be heated or for you to be (what appears to be) talking down to me by using rude phrasing and unnecessary capitalized text.
In direct response to your first quote, have you considered that it is not mandatory to use Adobe's DRM infrastructure? If Adobe is unable to offer an acceptable experience with their engine the maybe it is Kobo's job to look to alternatives for providing a better .epub reading experience for it's customers, you know... because Kobo is the one charging consumers for what is to date an inadequate product.
Quote:
Originally Posted by PeterT
Yes I have and again with NO issues.
Why on earth do you think I was asking for as much info as you could supply about where you see the problem. The ONLY hope that exists to tracking down an issue is to supply as MUCH data as possible about HOW to reproduce it.
|
Like I said all I have is an Aura and other devices may not experience said bug. All I know is the every retail .kepub I own has cut off F's and italics with every stock font when justified on the lowest margin setting. This is stock firmware with zero patches with directly downloaded eBooks from the Kobo store. I have already provided pictures in the bug thread and others have also confirmed their existence. So I would say you are lucky to not be experiencing them on your device but all the same, the issue should have been addressed months ago or better yet never made it to a stable release let alone stable release after stable release.