Connoisseur
Posts: 68
Karma: 152
Join Date: Jun 2015
Device: Kobo Glo HD
|
Quote:
Originally Posted by GeoffR
It is probably because the KePub reader can't hande the low line spacing settings. Try increasing your line spacing a bit and see of that fixes it.
If you only read KePubs then you might want to edit the `My 15 line spacing values` patch to remove some of the low line spacing values and add some more high ones. There is a note at the end of the patch about this.
|
Increasing the line spacing didn't help.
On 3.18 i did not have this problem, yet i used your 15 line patch without any changes:
Code:
<Patch>
patch_name = `My 15 line spacing values`
patch_enable = `yes`
# load val1 from new table
replace_bytes = 5E80CC, 00 23 00 22 C3 F6 F0 73, 00 46 40 A3 D3 E9 00 23
# load val5 from new table
replace_bytes = 5E8124, 43 F2 33 33 4F F0 33 32, 2C A3 D3 E9 00 23 00 46
replace_bytes = 5E812C, C3 F6 F3 73, 00 46 00 46
# load val7 from new table
replace_bytes = 5E8152, 00 23 00 22 C3 F6 F8 73, 00 46 22 A3 D3 E9 00 23
# load val10 from new table
replace_bytes = 5E8190, 00 22 4F F0 80 43, 15 A3 D3 E9 00 23
# load val11-val14 from old table in a loop to make room for new table
replace_bytes = 5E81A4, 48 A3 D3 E9 00 23 07 F1, 48 A7 00 26 D7 E9 00 23
replace_bytes = 5E81AC, 80 01 20 46 61 E9 0A 23, 20 A9 31 44 61 E9 0A 23
replace_bytes = 5E81B4, 11 F6 5C EF 45 A3 D3 E9, 20 46 11 F6 5C EF 08 36
replace_bytes = 5E81BC, 00 23 07 F1 80 01 20 46, 08 37 20 2E F2 D1 00 AF
# load val15 from new table, jump over new table
replace_bytes = 5E81C4, 61 E9 08 23 11 F6 52 EF, 0A A3 D3 E9 00 23 17 E0
# new table, inial values 1.0, 1.2, 1.5, 2.0, 3.0
replace_bytes = 5E81D0, 00 23 07 F1 80 01 20 46, 00 00 00 00 00 00 F0 3F
replace_bytes = 5E81D8, 61 E9 06 23 11 F6 48 EF, 33 33 33 33 33 33 F3 3F
replace_bytes = 5E81E0, 3F A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F8 3F
replace_bytes = 5E81E8, 80 01 20 46 61 E9 04 23, 00 00 00 00 00 00 00 40
replace_bytes = 5E81F0, 11 F6 3E EF 00 23 00 22, 00 00 00 00 00 00 08 40
#
# 15 values for replacement:
replace_float = 5E81D0, 1.0, 0.9
replace_float = 5E8298, 1.05, 0.95
replace_float = 5E82A0, 1.07, 1.0
replace_float = 5E82A8, 1.1, 1.05
replace_float = 5E81D8, 1.2, 1.1
replace_float = 5E82B0, 1.35, 1.05
replace_float = 5E81E0, 1.5, 1.1
replace_float = 5E82B8, 1.7, 1.15
replace_float = 5E82C0, 1.8, 1.2
replace_float = 5E81E8, 2.0, 1.25
replace_float = 5E82C8, 2.2, 1.30
replace_float = 5E82D0, 2.4, 1.35
replace_float = 5E82D8, 2.6, 1.4
replace_float = 5E82E0, 2.8, 1.45
replace_float = 5E81F0, 3.0, 1.5
#
# The 15 line spacing values above should allow the line spacing to be adjusted
# in increments of one pixel when using a medium sized font on a high resolution
# device. If you use a small font size and/or a lower resolution device you may
# find that increasing the slider one step at a time doesn't always result in a
# line spacing change at each step. In that case, you might want to use 15
# replacement values that are not quite so close together. For example:
# 0.7 0.75 0.8 0.825 0.85 0.875 0.9 0.925 0.95 0.975 1.0 1.05 1.1 1.15 1.2
#
</Patch>
On 3.19 the values are:
Code:
Patch>
patch_name = `My 15 line spacing values`
patch_enable = `yes`
# load val1 from new table
replace_bytes = 616124, 00 23 00 22 C3 F6 F0 73, 00 46 40 A3 D3 E9 00 23
# load val5 from new table
replace_bytes = 61617C, 43 F2 33 33 4F F0 33 32, 2C A3 D3 E9 00 23 00 46
replace_bytes = 616184, C3 F6 F3 73, 00 46 00 46
# load val7 from new table
replace_bytes = 6161AA, 00 23 00 22 C3 F6 F8 73, 00 46 22 A3 D3 E9 00 23
# load val10 from new table
replace_bytes = 6161E8, 00 22 4F F0 80 43, 15 A3 D3 E9 00 23
# load val11-val14 from old table in a loop to make room for new table
replace_bytes = 6161FC, 48 A3 D3 E9 00 23 07 F1, 48 A7 00 26 D7 E9 00 23
replace_bytes = 616204, 80 01 20 46 61 E9 0A 23, 20 A9 31 44 61 E9 0A 23
replace_bytes = 61620C, FC F5 46 EC 45 A3 D3 E9, 20 46 FC F5 46 EC 08 36
replace_bytes = 616214, 00 23 07 F1 80 01 20 46, 08 37 20 2E F2 D1 00 AF
# load val15 from new table, jump over new table
replace_bytes = 61621C, 61 E9 08 23 FC F5 3C EC, 0A A3 D3 E9 00 23 17 E0
# new table, inial values 1.0, 1.2, 1.5, 2.0, 3.0
replace_bytes = 616228, 00 23 07 F1 80 01 20 46, 00 00 00 00 00 00 F0 3F
replace_bytes = 616230, 61 E9 06 23 FC F5 32 EC, 33 33 33 33 33 33 F3 3F
replace_bytes = 616238, 3F A3 D3 E9 00 23 07 F1, 00 00 00 00 00 00 F8 3F
replace_bytes = 616240, 80 01 20 46 61 E9 04 23, 00 00 00 00 00 00 00 40
replace_bytes = 616248, FC F5 28 EC 00 23 00 22, 00 00 00 00 00 00 08 40
#
# 15 values for replacement, change these to suit:
replace_float = 616228, 1.0, 0.7
replace_float = 6162F0, 1.05, 0.75
replace_float = 6162F8, 1.07, 0.8
replace_float = 616300, 1.1, 0.82
replace_float = 616230, 1.2, 0.84
replace_float = 616308, 1.35, 0.86
replace_float = 616238, 1.5, 0.88
replace_float = 616310, 1.7, 0.9
replace_float = 616318, 1.8, 0.92
replace_float = 616240, 2.0, 0.94
replace_float = 616320, 2.2, 0.96
replace_float = 616328, 2.4, 0.98
replace_float = 616330, 2.6, 1.0
replace_float = 616338, 2.8, 1.05
replace_float = 616248, 3.0, 1.1
#
# The 15 line spacing values above should allow the line spacing to be adjusted
# in increments of one pixel when using a medium sized font on a high resolution
# device. If you use a small font size and/or a lower resolution device you may
# find that increasing the slider one step at a time doesn't always result in a
# line spacing change at each step. In that case, you might want to use 15
# replacement values that are not quite so close together. For example:
#
# 0.7 0.75 0.8 0.825 0.85 0.875 0.9 0.925 0.95 0.975 1.0 1.05 1.1 1.15 1.2
#
# Also note that the KEPUB reader has problems when the line spacing value is
# set too low, depending on the font used. Most of the built-in fonts are okay
# down to about 0.9. If you only read KePub books then you might want to remove
# some of the lower values and add some more of the higher ones. For example:
#
# 0.9 0.925 0.95 0.975 1.0 1.025 1.05 1.075 1.1 1.15 1.2 1.25 1.3 1.35 1.4
#
</Patch>
Let me see if you changed anything in those value's from 3.18 to 3.19..
..apparently you did, ill change the values back as they were in your 3.18 patch and see if that fixes it.
/edit: now i think about it, i [s]might[/s] have changed those values myself in your 3.18 patch.
/edit 2: editting the values to slightly higher ones did fix the problem. Cheers!
Last edited by outlandos; 12-09-2015 at 01:03 PM.
|