Cool Reader for Kobo

[trekk]

I should have tested more accurately. You can use margins with a higher value greater than 30, but not every value is saved, after closing CoolReader.

These values worked for me (left margin/right margin):

30/30
40/40
50/50
60/60
80/80
100/100

You can make combinations like 30/50. These will also be saved.

35, 45, 55, 65, 70, 90 didn't work for me.

When I mixed a working value with a non working (e.g. 30/75), I was not able to start CoolReader again, even after correcting the value in the cr3.ini manually.

[parkher]

Another issue - the font size used for file names in the internal file browser and in the recent book list.
The font size currently is huge. For me, impossible to read. I need 3 times smaller letters to be able to read them comfortably.
For comparison, for book text I am using Amasis size=32 which corresponds to size=20 in the native Kobo reader or in CR on PRS-T2.
If only the size of letters were the same or even a bit smaller - that would be perfect.
Besides, with smaller letters most of file names would fit on the screen without the need for horizontal scrolling.

Because probably there are people who want larger letters, and because a different size is perhaps needed for Aura HD than for other devices, clearly a way to choose the size of that font is needed. Either in settings or at least in cr3.ini file

[parkher]

trekk

Better and better. I was lucky I did not run so far into such values preventing CR to start.
That might explain why some other people can not start CR sometimes until re-installing it.
But still, if you correct it in cr3.ini and it is not enough, then what? Clearing the cache?
Because clearly after that the remaining files are the same as after re-installing.

Unless the font - perhaps it is not the same which font is used? And perhaps its size?
I am using custom added Amasis30 @ 32 (corresponds to regular size 20)
And which book is opened on start and at which position and with what CR style options.
Yes, there are some other factors that go away after re-installing.
Or after removing cr3hist.bmk and cache files.

[trekk]

Originally Posted by parkher

trekk
But still, if you correct it in cr3.ini and it is not enough, then what? Clearing the cache?

Honestly, I have no idea. I corrected the cr3.ini manually, shutdown the device, rebooted, but CoolReader refused to start. So I reinstalled and everything was ok then.

BTW I didn't loose my fonts, nor my settings.

[parkher]

Depends on how you reinstalled.
It is recommended to delete the whole KoboLauncher folder before reinstalling.
But I think reinstalling was not needed: it should be enough to delete cache and cr3hist.bmk and perhaps cr3.ini too.
Actually, we could determine which of those exactly needs to be deleted by trying one at a time.

[trekk]

Originally Posted by parkher

Depends on how you reinstalled.
It is recommended to delete the whole KoboLauncher folder before reinstalling.

I never do what's recommended. It takes the fun out of hacking Actually I just copied the KoboRoot.tgz into the .kobo folder and everything was fine again, settings and fonts included.

Originally Posted by parkher

Depends on how you reinstalled.
But I think reinstalling was not needed: it should be enough to delete cache and cr3hist.bmk and perhaps cr3.ini too.
Actually, we could determine which of those exactly needs to be deleted by trying one at a time.

I deleted cache at first - CR won't start, then cr3hist.bkm - CR won't start, then cr3.ini, CR still won't start. I reinstalled via KoboRoot.tgz and everything was good again...

[parkher]

This is very strange.
So what you could do next: to save cr3hist.bkm, cr3.ini and cache on your PC and then deliberately cause that problem and try to replace back one-by-one. But probably will not help either.

Backup the whole installation. The whole KoboLauncher directory?
And then replace back bit-by-bit. Or just compare what changed. Nothing likely changed outside the cr3 directory...

Interesting - when you install cr3 - is there an initial cr3.ini generated or is it created only when you run CR? I assume - only when you run CR. Therefore it is a mystery what happened.
I don't think changes are made directly in cr3 elf itself. But it can be checked. Because we are running out of options.

Maybe access rights of some crucial file were somehow modified?
I mean - file permissions.

[trekk]

Originally Posted by parkher

Interesting - when you install cr3 - is there an initial cr3.ini generated or is it created only when you run CR? I assume - only when you run CR.

Yes, usually the cr3.ini is generated the first time you start CR.

Originally Posted by parkher

Maybe access rights of some crucial file were somehow modified?
I mean - file permissions.

Not that I can see.

I hope we can solve this mystery. But not today. It' time for some "Breaking Bad" and some sleep afterwards. Have a nice evening!

[parkher]

Originally Posted by trekk

It' time for some "Breaking Bad" and some sleep afterwards. Have a nice evening!

I am a few seasons behind but I have blurays so I am joining you

[pkbo]

Originally Posted by trekk

These values worked for me (left margin/right margin):

Supported values are:

0, 1, 2, 3, 4, 5, 8, 10, 12, 14, 15, 16, 20, 25, 30, 40, 50, 60, 80, 100, 130, 150, 200, 300

[parkher]

Originally Posted by pkbo

Supported values are:

0, 1, 2, 3, 4, 5, 8, 10, 12, 14, 15, 16, 20, 25, 30, 40, 50, 60, 80, 100, 130, 150, 200, 300

I was able to increase values only to 100, they do not go any further.
If I write larger values directly to cr3.ini they probably would be reset when CR3 is launched. But maybe not?
Maybe worth trying.

In portrait, 80 is pretty good, on Aura HD it gives me about 8 mm + 87 mm + 8 mm.
87 mm text width is similar to what you find in most mass market paperbacks and 8 mm margin is comfortable enough. Going below 7 mm is not pleasant to me.

In landscape I would need margins to increase the text length further, let's say from 90 mm - so the required margins are up to 250 to ensure there is no big gap between the text width in portrait and landscape.

[pkbo]

Originally Posted by parkher

I was able to increase values only to 100, they do not go any further.

So, this should be GUI limitation. The engine contains values I've listed.

Originally Posted by parkher

If I write larger values directly to cr3.ini they probably would be reset when CR3 is launched. But maybe not?

They shouldn't. The engine checks if setting value is in predefined set when it reads ini file. If it is not, it uses default value. If you will specify in the ini file one of above values they should work. The GUI limitation just doesn't allow you to enter the value it doesn't validate values stored in the ini file.

[parkher]

Ok, thanks
But why there are those specific sets?
Actually I tried values = 75, they gave me 7 mm margin and 88 mm text - the seemed to work,
at least those values were allowed to be set and they were working.
Previously I was using = 64 - also was working.

OFF TOPIC:

To English speakers:
I just invented this English sentence, is it correct?

No, do go to do so to Jo!

I guess, there are a couple of dubious things,
No, do go do it to Jo!
would be safer but where is the fun in that?

[jlynton]

Originally Posted by parkher

OFF TOPIC:

To English speakers:
I just invented this English sentence, is it correct?

No, do go to do so to Jo!

I guess, there are a couple of dubious things,
No, do go do it to Jo!
would be safer but where is fun in that?

No, do go to do so to Jo! Seems correct to me.

No, do go do it to Jo! You can not "go do...", to be coorect you should say "go and do..."

[parkher]

I think you can: "go do" is a shortcut for "go, do" as in
Go, do it!
Go do it! is usually used instead.
But for my purposes much better is "go to do"