New Buggins Firmware - 20100716

[Dave_S]

Originally Posted by Spiffy

Its a Unicode issue, right? Whatever text editor you use has to be able to save that way.

Actually, I had Notepad++ set for UNIX and ANSI, so the text was not in a Unicode like UTF-8 or Windows-1252. ANSI is basically just ASCII character codes, but what I think caused all my problems in getting the script to work was the line endings. Windows text ends all lines with a Carriage Return Line Feed sequence, while Linux/UNIX text ends all lines with just a Line Feed. I believe Mac text ends all lines with just a Carriage Return, but I am not really familiar with Mac text formating. In any case, if the line ending is wrong then the shell parser just gets confused and the command ends up not being executed. Of course, on the PocketPRO you can not see when the shell emits an error message, so I had to try for quite a while to get that simple script to work. But now it works great for me, and now I can easily clear the cache if it gets corrupted.

[dkarale]

Does this latest version release fixed the coolreader's Unicode display issue (Asian text scripts)? Is there a way for the Coolreader to display Unicode properly? Thanks.

[Dave_S]

Originally Posted by dkarale

Does this latest version release fixed the coolreader's Unicode display issue (Asian text scripts)? Is there a way for the Coolreader to display Unicode properly? Thanks.

CoolReader seems to work fine with UTF-8 Unicode, but if your text is using something other than UTF-8 Unicode then there may be a problem?

[booknut]

I give up, I tried all kinds of variations, but the file just won't work for me, I guess there may be minute variations with different PPs even though we are using the same Lbook firmware - maybe someone else with more skills can check this out because this is a nifty little utility!

[Dave_S]

Originally Posted by booknut

I give up, I tried all kinds of variations, but the file just won't work for me, I guess there may be minute variations with different PPs even though we are using the same Lbook firmware - maybe someone else with more skills can check this out because this is a nifty little utility!

I am sorry that the script has been causing you so much frustration, booknut! Now I am wondering if it worked for anyone else but me. On the Lbook V3:CoolReader thread on the-ebook.org I saw that some people seemed to have problems using a cache clearing script too, but then others were saying that it worked fine. BUT, even a few that had problems eventually got it to work. Since I was using Google translate for the Russian language I may have missed some finer points, but I did eventually get it to work fine for me. Now, I can't get it to not work, but I admit that I did not try very hard for that.

[Solicitous]

Originally Posted by Dave_S

I am sorry that the script has been causing you so much frustration, booknut! Now I am wondering if it worked for anyone else but me. On the Lbook V3:CoolReader thread on the-ebook.org I saw that some people seemed to have problems using a cache clearing script too, but then others were saying that it worked fine. BUT, even a few that had problems eventually got it to work. Since I was using Google translate for the Russian language I may have missed some finer points, but I did eventually get it to work fine for me. Now, I can't get it to not work, but I admit that I did not try very hard for that.

I just had a look at the script (I haven't run it myself).

Are the paths correct? IIRC with reading a book in CR and look at the About, it shows the file path (from memory) to be /root/abook/ for the memory card, and /home/ for the internal memory (this is with the latest LBook firmware btw).

So that being the case the script should be;

#!/bin/sh
rm -rf /root/abook/crengine/.cache/*
rm -rf /home/crengine/.cache/*

You always have the option of running;

#!/bin/sh
rm -rf /root/abook/crengine/.cache
rm -rf /home/crengine/.cache

and just delete the .cache folder.

[booknut]

That's what I thought earlier as well, but it makes no difference, I saved either script (and some more I pulled off the Russian forum) and saved them as Unicode, Unicode 7 and 8, without CR and LF, only with CR and a few other variations. I suspect my problem is Windows 7 (when nothing else, blame Windows) ...

[Dave_S]

Originally Posted by Solicitous

I just had a look at the script (I haven't run it myself).

Are the paths correct? IIRC with reading a book in CR and look at the About, it shows the file path (from memory) to be /root/abook/ for the memory card, and /home/ for the internal memory (this is with the latest LBook firmware btw).

The whole thing about the cache clearing script started with this post from Buggins:

Lay remake is not necessary. The script should be called with the extension. Exe.fb2 - then he kulriderom start. 

clear_cr3_cache.sh.exe.fb2 
Code:

#! / Bin / sh 
rm-rf / home / crengine / cache 
rm-rf / root / abook / crengine / cache 


(Do not remember the exact path)
_________________
Best regards, 
Buggins

As you can see, even Buggins thought the SD path had "abook" in the path string, but he was not sure, and he turned out to be wrong. You can view the whole series of posts in the Russian language ( I used Google translate ) starting about half way down on page 234 here:
http://www.the-ebook.org/forum/viewt...asc&start=4660
Eventually jotas came to the rescue, sort of, and provided additional clarification. All I can say is the the script that I posted here is working fine for me. Lately I have been reading from the SD card, and just switch from the 6" reader at home to the 5" reader when I am away from home. I use the cache clearing script when ever I switch readers to avoid any possible confusion, and the script on both can clear the cache OK. The only "gotcha" is that I can use the DJVU extension on the 6" reader but I must use the FB2 extension on the 5" PocketPRO.

[jotas]

Hello,

You should use and write as discussed here:

http://www.the-ebook.org/forum/viewt...=421403#421403

[jotas]

Originally Posted by Dave_S

Eventually jotas came to the rescue, sort of, and provided additional clarification.

Crossed in-time replies and information :

[Dave_S]

Originally Posted by jotas

Crossed in-time replies and information

You are very welcome to join in because I am getting worried about why the script does not work for booknut. It was your information that helped me get the script working for my own use, so thank you very much!

[booknut]

Yeah, I was going over that section of the forum as well and Google translations are ok to get the gist but the details evade me. I just thought that such a little script is very useful since I frequently open several books in a row to decide what I want to read next and always feel the reader slows down after doing that for a while. It just irks me that I am unable to get this to work (I am not all that competitive, just "gadget-driven"). Once I have a bit more time, I'll fiddle with this some more and should I manage to get it to work, I'll post the details.

[jotas]

Originally Posted by booknut

I frequently open several books in a row to decide what I want to read next and always feel the reader slows down after doing that for a while.

This can happen if you use "old" or "classic" CoolReader, if opening books directly from CR or for recent books lists, or you change font typeface frequently. It had some small memory leaks (loading and unloading fonts, loading hyphenation patterns...) so the memory eventually starts to fill up and moving over books even over pages starts to slow a bit.

Better and simple solution: exit CR, to bookshelf, then reload book with new and personal settings. Will start to work fast again.

For new CoolReader Buggins fixed many of this, it is quite stable from weeks ago (if not using very latest, new and days-ago features), but... the new fast reopening book and cache design gives great options and a lot of speed, but continous compressing/uncompressing, saving/loadading to/from SD memory, and cache code, is not always 100% safe ... this is because the small, useful and commented script will clear all these problems, save you life and reading if away from a computer, and it takes no more than one or two seconds.

[booknut]

I am running Buggins very latest firmware from two days ago (19 July) and I am using EditPadPro, where I set the txt file to save as UNIX and converted end of lines to wraps - I'll live if I cannot make this work but will feel oh so deprived :-)

[jotas]

Originally Posted by booknut

I am running Buggins very latest firmware from two days ago (19 July) and I am using EditPadPro, where I set the txt file to save as UNIX and converted end of lines to wraps - I'll live if I cannot make this work but will feel oh so deprived :-)

Menu -> Convert -> To UNIX (LF only)