Modifications for bad eyes

[truemarine]

Originally Posted by tshering

Since an new FW is supposed to appear very soon, I will wait the next FW.

Thanks and will wait for it.

[questerymj]

Tested 3.17 and worked well in my bland new kobo glo HD.

But I would like to know if I can change the system font a bit smaller, like the size of book name in library book list. Can I modify it in patcher and pack the file to update?

[tshering]

Originally Posted by questerymj

Tested 3.17 and worked well in my bland new kobo glo HD.

I am glad it works for you!

Originally Posted by questerymj

But I would like to know if I can change the system font a bit smaller, like the size of book name in library book list. Can I modify it in patcher and pack the file to update?

Yes, it is possible to modify the patch. The files to edit are located in the folder 3.17.0_source, and have the extension ".txt". You can change everything behind "newdata=" and behind "newpart=". For some details see this post. You might be surprised when you open the patch files!
Since FW 3.17.0 has already been replaced by 3.17.3, it might not be worth spending much time in modifying the patch for 3.17.0 however.

[questerymj]

Originally Posted by tshering

I am glad it works for you!

Yes, it is possible to modify the patch. The files to edit are located in the folder 3.17.0_source, and have the extension ".txt". You can change everything behind "newdata=" and behind "newpart=". For some details see this post. You might be surprised when you open the patch files!
Since FW 3.17.0 has already been replaced by 3.17.3, it might not be worth spending much time in modifying the patch for 3.17.0 however.

Thank you for replying! I'm a big fan of your patch and keep using it in my Kobo Glo, and now Glo HD. Always thank you for making it for us.

Yes I know 17.3 is released, but rather than keep pursuing latest patch, I would like to have a stable customed patch that best for me. XD Thanks for the information, I will try to trim the font size for myself.

[tshering]

Originally Posted by questerymj

Thank you for replying! I'm a big fan of your patch and keep using it in my Kobo Glo, and now Glo HD. Always thank you for making it for us.

Yes I know 17.3 is released, but rather than keep pursuing latest patch, I would like to have a stable customed patch that best for me. XD Thanks for the information, I will try to trim the font size for myself.

If you only need a slightly enlarged font size. Have a look at this thread. For me, this is for the most part sufficient. For my personal use, I think I will only keep the changes relating to the dictionary and the menu of the "modification for bad eyes", maybe some others.

[questerymj]

Originally Posted by tshering

If you only need a slightly enlarged font size. Have a look at this thread. For me, this is for the most part sufficient. For my personal use, I think I will only keep the changes relating to the dictionary and the menu of the "modification for bad eyes", maybe some others.

Thanks for your suggestion again!

I just try it and find the menu/book name list txts are still too large for me, maybe because my kobo is glo HD so it didn't works. Could you tell me which lines are related to menu texts? Thanks in advanced!

[tshering]

Originally Posted by questerymj

Thanks for your suggestion again!

I just try it and find the menu/book name list txts are still too large for me, maybe because my kobo is glo HD so it didn't works.

Did you revert/remove the modifications for bad eyes before you applied the "Non-italic book titles and so on, access to Japanese keyboard" modification? If both are applied, the effect is the combined results of both.

Originally Posted by questerymj

Could you tell me which lines are related to menu texts? Thanks in advanced!

The very first patch in the file nickel.txt. It is located in line 20, directly after

// -------------------------------------------------- Menu

[tshering]

Same rules, limitations ... as in the last versions.


For those who want more control:

Spoiler:

This time I added some files in the folder "plus" in order to help those who want to have more control over the large amount of unclassified patches. In these files I replaced the values for font-size of the "new parts" with symbols. An example:

<patch>
name=?
enabled=true
action=replace_string
position=B7F508
oldpart=* {\n\ttext-decoration: underline;\n\tfont: 13px Avenir;\n\ttext-transform: uppercase;\n\ttext-decoration: underline;\n\tpadding-left: 2px;\n\tpadding-right: 2px;\n}\n\n
oldpart=*[qApp_deviceIsPhoenix="true"]      { font-size: 16px; }\n
oldpart=*[qApp_deviceIsDragon="true"]       { font-size: 21px; }\n
oldpart=*[qApp_deviceIsAlyssum="true"]      { font-size: 23px; }\n
oldpart=*[qApp_localeName="ja_JP"]   {font-family: Sans-SerifJP; text-transform: none; }
newpart=* {\n\ttext-decoration: underline;\n\tfont: <<13px>> Avenir;\n\ttext-transform: uppercase;\n\ttext-decoration: underline;\n\tpadding-left: 2px;\n\tpadding-right: 2px;\n}\n\n
newpart=*[qApp_deviceIsPhoenix="true"]      { font-size: <<16px>>; }\n
newpart=*[qApp_deviceIsDragon="true"]       { font-size: <<21px>>; }\n
newpart=*[qApp_deviceIsAlyssum="true"]      { font-size: <<23px>>; }\n
newpart=*[qApp_localeName="ja_JP"]   {font-family: Sans-SerifJP; text-transform: none; }
combineparts
</patch>

For only slightly increasing the font-size, you could for instance replace all occurrences of "<<16px>>" by "18px" and so on.

At the top of each file, there is a complete list of the used symbols, for instance:
# symbols: <<17px>>, <<19px>>, <<22px>>, <<23px>>, <<26px>>, <<28px>>, <<29px>>, <<30px>>, <<32px>>, <<36px>>, <<38px>>, <<39px>>, <<56px>>, <<64px>>,

You have to replace ALL symbols by real values!
Especially in the case of zlib compressed strings, you will possibly have to manually modify the strings in order to make the new compressed data smaller than or equal in size to the old data. While preparing, use 3.17.3_checkmode.bat instead of 3.17.3.bat. In check mode, a length error will not stop the processing, but continue and the list of errors will be presented at the end.

[surquizu]

Originally Posted by tshering

Same rules, limitations ... as in the last versions.


For those who want more control:

Spoiler:

This time I added some files in the folder "plus" in order to help those who want to have more control over the large amount of unclassified patches. In these files I replaced the values for font-size of the "new parts" with symbols. An example:

<patch>
name=?
enabled=true
action=replace_string
position=B7F508
oldpart=* {\n\ttext-decoration: underline;\n\tfont: 13px Avenir;\n\ttext-transform: uppercase;\n\ttext-decoration: underline;\n\tpadding-left: 2px;\n\tpadding-right: 2px;\n}\n\n
oldpart=*[qApp_deviceIsPhoenix="true"]      { font-size: 16px; }\n
oldpart=*[qApp_deviceIsDragon="true"]       { font-size: 21px; }\n
oldpart=*[qApp_deviceIsAlyssum="true"]      { font-size: 23px; }\n
oldpart=*[qApp_localeName="ja_JP"]   {font-family: Sans-SerifJP; text-transform: none; }
newpart=* {\n\ttext-decoration: underline;\n\tfont: <<13px>> Avenir;\n\ttext-transform: uppercase;\n\ttext-decoration: underline;\n\tpadding-left: 2px;\n\tpadding-right: 2px;\n}\n\n
newpart=*[qApp_deviceIsPhoenix="true"]      { font-size: <<16px>>; }\n
newpart=*[qApp_deviceIsDragon="true"]       { font-size: <<21px>>; }\n
newpart=*[qApp_deviceIsAlyssum="true"]      { font-size: <<23px>>; }\n
newpart=*[qApp_localeName="ja_JP"]   {font-family: Sans-SerifJP; text-transform: none; }
combineparts
</patch>

For only slightly increasing the font-size, you could for instance replace all occurrences of "<<16px>>" by "18px" and so on.

At the top of the file, there is a complete list of the used symbols, for instance:
# symbols: <<17px>>, <<19px>>, <<22px>>, <<23px>>, <<26px>>, <<28px>>, <<29px>>, <<30px>>, <<32px>>, <<36px>>, <<38px>>, <<39px>>, <<56px>>, <<64px>>,

You have to replace ALL symbols by real values!
Especially in the case of zlib compressed strings, you will possibly have to manually modify the strings in order to make the new compressed data smaller than or equal in size to the old data. While preparing, use 3.17.3_checkmode.bat instead of 3.17.3.bat. In check mode, a length error will not stop the processing, but continue and the list of errors will be presented at the end.

[questerymj]

Thanks a lot!!!!

[drjd]

Thank you!

[tshering]

Different from the patch for 3.15.0, this one concerns only nickel. Since nickel is not modified in GeoffR's patch for 3.17.3, you can simply double-click 3.17.3.bat and copy the created KoboRoot.tgz to .kobo of your device.

Originally Posted by truemarine

Thanks and will wait for it.

It took me longer than expected!

[truemarine]

Originally Posted by tshering

Different from the patch for 3.15.0, this one concerns only nickel. Since nickel is not modified in GeoffR's patch for 3.17.3, you can simply double-click 3.17.3.bat and copy the created KoboRoot.tgz to .kobo of your device.


It took me longer than expected!

So grateful! I didn't expect it. Thanks again!

[iplag]

To tshering
Frst of all thanks for the 3.15 patch. It worked nicely in the begining. However when I tried to use an sd card, it could not be recognizzed. After performing factory reset the card worked fine. I tried to patch it again and the card could not be recognizzed. Factory reset again and everything was ok.
I would appreciate any hints on how to solve this.

[tshering]

Originally Posted by iplag

To tshering
Frst of all thanks for the 3.15 patch. It worked nicely in the begining. However when I tried to use an sd card, it could not be recognizzed. After performing factory reset the card worked fine. I tried to patch it again and the card could not be recognizzed. Factory reset again and everything was ok.
I would appreciate any hints on how to solve this.

This might be difficult to hunt the culprit down. You would have to enable and disable each patch block and check whether the sd is working or not. Maybe it is easier to try the patch for one of 3.17.3 and see whether this issue does occur there too.