Thread: Syncing takes forever
View Single Post
Old 08-17-2013, 08:29 PM   #12
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 thepossum View Post
Re: Off-topic: unpredictable dictionary replacements

The 'HEAD' request I'd seen above just tells me that during the sync, the Kobo is probably just looking at datestamps to see if your current file is older than the one being provided by Kobo. If you were somehow able to fudge the datestamp on your sideloaded dictionary, perhaps it will never be replaced?

I know that with Linux you can use a command like:

touch --date="Jan 1 2100" filename

to set the file's datestamp well into the future. There are probably multiple ways of doing the same thing under Windows, Google is your friend ;-)

I think this calls for either a bit of experimentation or a forums search here for people who've already run into this problem here on mobileread?
That might work, but based on other things the firmware does, it is probably checking the date in the database. Changing the "LastModified" timestamp in the "Dictionary" table is probably the way to go.
davidfor is offline   Reply With Quote