![]() |
#16 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,534
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
|
epub extension uses the Adobe RMSDK based renderer. kepub.epub uses the ACCESS based renderer.
Sent from my Nexus 7 using Tapatalk |
![]() |
![]() |
![]() |
#17 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,786
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Check the font in a font editor to see if something is wrong with the j.
|
![]() |
![]() |
Advert | |
|
![]() |
#18 |
Enthusiast
![]() Posts: 26
Karma: 10
Join Date: Aug 2015
Device: Kobo Libra H20 / Glo HD
|
I don't know what was problem.
But GeoffR sent modified font and it worked for me. Thank you, GeoffR. |
![]() |
![]() |
![]() |
#19 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
I made these changes: * Changed name of ligature tables from 'lig' to 'liga'. * Increased weight of Regular/Italic by 4 em units. * Created Bold/BoldItalic versions with weight increased by 50 em units. * Changed PANOSE weights to book/bold. * Added 'old-style' kern tables. I think the slight change in weight, which causes the glyphs to be re-drawn, was probably what fixed the problem with the 'j'. I just need to change the name of the font to be able to distribute it under the OFL licence, so if anyone wants me to post it here, just think of a new name. Last edited by GeoffR; 04-09-2017 at 07:46 PM. |
|
![]() |
![]() |
![]() |
#20 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,534
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
|
Josarivo in honour of the J?
|
![]() |
![]() |
Advert | |
|
![]() |
#21 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Rojarivo
I changed the name from Rosarivo to Rojarivo, Rosa (pink) to Roja (red) as the new font is slightly heavier, and appears to fix the problem with the 'j'.
It is a nice font and it is a shame to mess with it, maybe someone more knowledgable could take a look at the 'j' glyph in the original font and fix it without changing the weight. Also the bold versions I just created by using the default fontforge parameters, someone else might be able to do a better job. I made these changes: * Changed name of ligature tables from 'lig' to 'liga'. * Increased weight of Regular/Italic by 4 em units. * Created Bold/BoldItalic versions with weight increased by 50 em units. * Changed PANOSE weights to book/bold. * Added 'old-style' kern tables. * Changed font name from Rosarivo to Rojarivo. Edit: I've attached an alternative with the Bold/BoldItalic versions created by increasing the weight by only 36 em units. This is not a full bold, more of a semi-bold I think, but it doesn't distort the shape of the glyphs as much. Last edited by GeoffR; 04-09-2017 at 10:19 PM. Reason: Added semibold version |
![]() |
![]() |
![]() |
#22 | |
Gentleman and scholar
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,479
Karma: 111164374
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara BW; Nook ST w/Glowlight, Paperwhite 3
|
Quote:
|
|
![]() |
![]() |
![]() |
#23 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 977
Karma: 3475832
Join Date: May 2012
Location: France
Device: Elipsa, Sage, Libra 2
|
Thank you Geoff. This is a beautiful font, but I find that it needs a very wide line spacing to avoid the dreaded cut-off lines at the bottom for kepubs (latest F/W), and it looks strange with the line spacing practically as wide as the line itself.
What I find stranger is that when I go back to Palatino linotype without changing the line spacing, the page looks much better. |
![]() |
![]() |
![]() |
#24 | |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
Edit: If anyone wants to have a go at fixing that problem, you can try adjusting the HHead ascent offset and/or HHead descent offset in OS/2 > Metrics, I have a feeling the only way to avoid the KePub cut-off problem is to use settings that increase the overall line spacing though -- either the font's internal spacing, or the spacing in the device/book stylesheet. Last edited by GeoffR; 04-10-2017 at 11:41 PM. Reason: OS/2 > Metrics |
|
![]() |
![]() |
![]() |
#25 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Rojarivo v2
I have made a small change to the font metrics which seems to help with the KePub problem where the page break cuts off the top of the glyphs leaving them on the bottom of the previous page when the line spacing is very narrow.
This doesn't change the line spacing, it just shifts the glyphs downward on the line, so there is more space above and less below. After a little testing on my Glo it seems to avoid the cut-off problem, as long as the line spacing is not so narrow that the ascenders and decenders actually touch. (Edit: If this change works for this font, then I think the same could work for any font with this problem.) The only change from v1 is: * Changed HHead ascent/descent offset to 120/120. Last edited by GeoffR; 04-11-2017 at 05:25 AM. |
![]() |
![]() |
![]() |
#26 |
Guru
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 977
Karma: 3475832
Join Date: May 2012
Location: France
Device: Elipsa, Sage, Libra 2
|
The limit before the cut-off makes a somewhat wider line spacing than I would otherwise choose, but it is much better, and I will read with it. Thank you very much.
|
![]() |
![]() |
![]() |
#28 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Rojarivo v3
This version has been rescaled in an attempt to make it fit in with the default Kobo fonts (Georgia, Avenir). The dark option appears similar in weight to Georgia on my Glo.
It should also work better at narrow line spacings in the KePub reader, On my Glo I can read KePubs with a line spacing setting as low as 0.9 (0.1 lower than the minimum setting on an unpatched device) before lines start to be cut off. I have also added a few missing hyphen, dash, and spacing glyphs. Changes since v2: Spoiler:
Edit: Updated to v3.2, which tries to find a medium between the line split problem which appears in KePubs at narrow line spacings, and the clip problem that appears at larger font sizes. Last edited by GeoffR; 05-22-2017 at 04:37 AM. Reason: Updated to v3.2 |
![]() |
![]() |
![]() |
#29 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
v3.1
I've added v3.1 to the above post. It turns out that trying to avoid one KePub problem just causes another.
* v3 is probably better for those who read KePubs with very narrow line spacing. * v3.1 is probably better for those who read KePubs with a large font size. Either version is fine for reading ePubs. Edit: The only difference between v3 and v3.1 is the HHead ascent/descent offsets. If you want to play with them in fontforge you might be able to find a setting that works better for you. Increasing both offsets improves the split problem and worsens the clip problem, decreasing both offsets does the opposite. Last edited by GeoffR; 05-22-2017 at 12:13 AM. Reason: attached screenshot |
![]() |
![]() |
![]() |
#30 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
v3.2
I've updated the attachments in post #28 to v3.2, which uses HHead ascent/descent offsets of 224/284. I think this version will avoid the KePub clip problem in most cases, but still allow the line spacing to be set a bit lower than in v2.
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sigil/Qt does not display the font but ADE | rubeus | Sigil | 8 | 01-04-2015 09:32 AM |
card symbols don't display properly | asqueue | Conversion | 3 | 05-12-2014 03:19 PM |
Strange display issue with a certain font | bfollowell | Sigil | 4 | 02-15-2014 08:18 AM |
Altering HTML Script To Properly Display Background Images In ADE Ereaders. | Turk.Turkleton | Sigil | 16 | 09-25-2012 12:34 PM |
M92 fonts: why would a font not display? | mSSM | Onyx Boox | 8 | 09-05-2012 03:34 AM |