View Single Post
Old 11-25-2008, 08:40 AM   #9
gwynevans
Wizzard
gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.
 
gwynevans's Avatar
 
Posts: 1,402
Karma: 2000000
Join Date: Nov 2007
Location: UK
Device: iPad 2, iPhone 6s, Kindle Voyage & Kindle PaperWhite
Quote:
Originally Posted by Valloric View Post
For the life of me I can't figure out why this is happening, or why is it happening for some users and not for others. Changing fonts shouldn't impact the device's connectivity in any way.
Just wondering if there's some sort of 'scan-on-disconnect' process going on that's using some particular property of the fonts that's not quite correct on the error cases? Are there any 'known OK', 'public domain' fonts that could be uploaded as 'reference fonts' to try & rule that variable out?
gwynevans is offline   Reply With Quote