View Single Post
Old 03-22-2014, 03:06 AM   #39
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,960
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by GeoffR View Post
The bug does affect the Glo and Aura, but it would be much more noticeable on the AuraHD. The font size used for the synopsis was 20px for all models, but it should have been 23px for the Glo/Aura and 29px for the AuraHD.



Sorry about that, I didn't test it with kpg.exe and for some reason kpg.exe doesn't like the final \n in the original string. I've fixed this and edited the patches in the post #36 above.

Edit: I think I have figured out the cause of the problem with the patch, the kpg.exe replace string method doesn't accept the \n, \t encoding at all and was treating them literally instead of interpreting them as LF, TAB, etc., so I have edited the patch again to remove these characters from the replacement string too.
Not sure if this is quite legitimate but I patched the patch for myself by using replace_xor_00 instead of replace_string after my first attempt at generating the patch ended in an error message

Regards,
David
DNSB is offline   Reply With Quote