[Script] Koboify Fonts - Page 4

sherman · 10-17-2015, 07:34 PM

Hi folks,

Version 0.3.1 has been released. The batch file has been fixed, and I've now notified that the script should be called using

Code:

fontforge -script KoboifyFonts-0.3.1.py [OPTIONS]

instead of calling ffpython directly.

GERGE · 10-18-2015, 02:22 AM

I wasn't aware of this usage. Works with OS X too. But you still need the CLI version.

sherman · 10-18-2015, 02:52 AM

Quote:

Originally Posted by GERGE

I wasn't aware of this usage. Works with OS X too. But you still need the CLI version.

I didn't know about it at first either.

Makes things a bit simpler, especially on linux.

JSWolf · 10-18-2015, 06:44 PM

This program removes hints when that is not always a good idea. The problem is not with hinting, but rather incorrect hinting. Could this program be modified to run ttfautohint and put in correct hinting in TTF fonts. This would give a possibly better looking font on screen.

sherman · 10-18-2015, 08:39 PM

Quote:

Originally Posted by JSWolf

This program removes hints when that is not always a good idea. The problem is not with hinting, but rather incorrect hinting. Could this program be modified to run ttfautohint and put in correct hinting in TTF fonts. This would give a possibly better looking font on screen.

The script allows the user to choose whether or not they wish to remove hinting, or keep the original. (At least, it should.)

Autohinting may be a feature included in a future version.

JSWolf · 10-19-2015, 05:40 PM

Quote:

Originally Posted by sherman

The script allows the user to choose whether or not they wish to remove hinting, or keep the original. (At least, it should.)

Autohinting may be a feature included in a future version.

The problem is you won't know if the hinting is bad or not if there is hinting. So using ttfautohint to replace the hinting would solve the possible hinting problem.

sherman · 10-19-2015, 05:49 PM

Quote:

Originally Posted by JSWolf

The problem is you won't know if the hinting is bad or not if there is hinting. So using ttfautohint to replace the hinting would solve the possible hinting problem.

As I said, I may visit this in the future. If a person discovers an issue with the hinting, there is nothing stopping them from regenerating fonts if they have hinting issues.

Also, it is also conceivable (although unlikely) that a font is designed for e-ink screens, in which case you may not want to be messing with stuff like hinting.

JSWolf · 10-19-2015, 07:35 PM

Quote:

Originally Posted by sherman

As I said, I may visit this in the future. If a person discovers an issue with the hinting, there is nothing stopping them from regenerating fonts if they have hinting issues.

Also, it is also conceivable (although unlikely) that a font is designed for e-ink screens, in which case you may not want to be messing with stuff like hinting.

Most fonts are not designed for eInk screens. It's not messing with hinting. It's putting in proper hinting because some hinting is not correct and either needs to be removed or replaced. I do think Charis SIL looks better properly hinted than without hinting. This is on my H2O.

sherman · 10-19-2015, 07:51 PM

Jon,

You will be happy to know that I have added autohinting as an option in my upcoming successor to this script.

I will not be implementing any new features in this script however, including autohinting.

Now, can we put this issue to bed please?

Thank you.

JSWolf · 10-19-2015, 08:11 PM

Quote:

Originally Posted by sherman

Jon,

You will be happy to know that I have added autohinting as an option in my upcoming successor to this script.

I will not be implementing any new features in this script however, including autohinting.

Now, can we put this issue to bed please?

Thank you.

What's new in the upcoming successor? I had a thought that can go to the successor. If the original font is OTF, give an options to to save as TTF since that will work with the Advanced Font Control (if the patch to enable in in place).

dmapr · 10-19-2015, 11:42 PM

Quote:

Originally Posted by JSWolf

What's new in the upcoming successor? I had a thought that can go to the successor. If the original font is OTF, give an options to to save as TTF since that will work with the Advanced Font Control (if the patch to enable in in place).

It is saving as TTF even if few original is OTF. Have you seen the script save something as OTF?

sherman · 10-20-2015, 12:02 AM

Quote:

Originally Posted by JSWolf

What's new in the upcoming successor? I had a thought that can go to the successor. If the original font is OTF, give an options to to save as TTF since that will work with the Advanced Font Control (if the patch to enable in in place).

The script only generates TTF fonts (and a fontforge sfd file, but I'm thinking of dropping that, or making it optional)

The main "feature" of the successor is a simple GUI wrapper, although the script will still be able to run from the command line, or a batch file.

I also want to investigate autokerning (for fonts with no existing kerning tables), but I don't know how difficult that may be to implement.

JSWolf · 10-20-2015, 03:40 PM

Quote:

Originally Posted by dmapr

It is saving as TTF even if few original is OTF. Have you seen the script save something as OTF?

I've not run the script. I can easily do all the things the script does manually.

Cex · 10-22-2015, 09:26 AM

Hello,
I tried your script with Bookerly font for eInk devices (extracted from PW2 firmware), but I can't get rid of the Italics problem described in this thread:
https://www.mobileread.com/forums/sho...d.php?t=262943.

I have also tried to correct metadata manually, but can't find any error in the fonts. I have also tried all possible font names with same results.

I'm using sideloaded epubs (have not tested with kepubs) on Glo HD, and I always get italic as bold-italic.

Could someone provide some guidelines to correct this issue?

Thank you.

JSWolf · 10-22-2015, 05:28 PM

Stop using the LCD version of Bookerly and pull the eInk version out of the Kindle firmware. I can confirm that the eInk version works no issue and no need to Koboify.

10-17-2015, 07:34 PM	#46
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	V0.3.1 released Hi folks, Version 0.3.1 has been released. The batch file has been fixed, and I've now notified that the script should be called using Code: fontforge -script KoboifyFonts-0.3.1.py [OPTIONS] instead of calling ffpython directly.

10-22-2015, 09:26 AM	#59
Cex Enthusiast Posts: 29 Karma: 13132 Join Date: Jul 2015 Location: Spain Device: Glo; Glo HD; PW2; Voyage	Bookerly font Hello, I tried your script with Bookerly font for eInk devices (extracted from PW2 firmware), but I can't get rid of the Italics problem described in this thread: https://www.mobileread.com/forums/sho...d.php?t=262943. I have also tried to correct metadata manually, but can't find any error in the fonts. I have also tried all possible font names with same results. I'm using sideloaded epubs (have not tested with kepubs) on Glo HD, and I always get italic as bold-italic. Could someone provide some guidelines to correct this issue? Thank you.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
How to add alternate fonts without replacing system fonts.(this time this is a guide)	techiemonkey	Kindle Developer's Corner	17	09-12-2012 05:55 PM
An Observation on Fonts - Improving readability by using bold versions of fonts	nesler	General Discussions	12	06-24-2012 01:33 PM
need the fonts in /usr/java/lib/fonts of kindle touch5.0.0	hanpal	Kindle Developer's Corner	1	02-20-2012 11:40 AM
Troubleshooting need the fonts in /usr/java/lib/fonts of kindle touch5.0.0	hanpal	Amazon Kindle	0	02-20-2012 09:51 AM
Touch Fonts question (special characters in stock and custom fonts)	levil	Kobo Reader	20	09-23-2011 02:51 PM

10-18-2015, 02:22 AM	#47
GERGE Guru Posts: 733 Karma: 5797160 Join Date: Jun 2010 Location: Istanbul Device: Kobo Libra	I wasn't aware of this usage. Works with OS X too. But you still need the CLI version.

10-18-2015, 06:44 PM	#49
JSWolf Resident Curmudgeon Posts: 76,458 Karma: 136564696 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	This program removes hints when that is not always a good idea. The problem is not with hinting, but rather incorrect hinting. Could this program be modified to run ttfautohint and put in correct hinting in TTF fonts. This would give a possibly better looking font on screen.

10-19-2015, 07:51 PM	#54
sherman Guru Posts: 869 Karma: 2676800 Join Date: Sep 2008 Location: Taranaki - NZ Device: Kobo Aura H2O, Kobo Forma	Jon, You will be happy to know that I have added autohinting as an option in my upcoming successor to this script. I will not be implementing any new features in this script however, including autohinting. Now, can we put this issue to bed please? Thank you.

10-22-2015, 05:28 PM	#60
JSWolf Resident Curmudgeon Posts: 76,458 Karma: 136564696 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Stop using the LCD version of Bookerly and pull the eInk version out of the Kindle firmware. I can confirm that the eInk version works no issue and no need to Koboify.

Advert

Advert