Bookerly font woes

[Skydog]

I've spent the last two days reading older posts here on the Bookerly saga. In order to "fix" it for use with Kepubs, what steps exactly (as in Dummy 101) are required in FontForge? I've tried numerous times and end up with errors generated along with the new files. Do I need to change anything other than the first field "Fontname"?

Errors include: Self Intersecting; Missing Points at Extrema

I'm using v1.020 of Bookerly and attempting the naming convention from posts long ago and mentioned again in this thread:

Bookerly-Regular -> Bookerly-a.ttf
Bookerly-Italic -> Bookerly-b.ttf
Bookerly-Bold -> Bookerly-c.ttf
Bookerly-BoldItalic -> Bookerly-d.ttf

Any help would be greatly appreciated before I go bald from pulling my hair out!

[Flaviocc]

Originally Posted by Skydog

I've spent the last two days reading older posts here on the Bookerly saga. In order to "fix" it for use with Kepubs, what steps exactly (as in Dummy 101) are required in FontForge? I've tried numerous times and end up with errors generated along with the new files. Do I need to change anything other than the first field "Fontname"?

Errors include: Self Intersecting; Missing Points at Extrema

I'm using v1.020 of Bookerly and attempting the naming convention from posts long ago and mentioned again in this thread:

Bookerly-Regular -> Bookerly-a.ttf
Bookerly-Italic -> Bookerly-b.ttf
Bookerly-Bold -> Bookerly-c.ttf
Bookerly-BoldItalic -> Bookerly-d.ttf

Any help would be greatly appreciated before I go bald from pulling my hair out!

Here the steps - https://www.mobileread.com/forums/sh...81&postcount=9

I have the correct files here.

If you want, sent me a PM.

[NiLuJe]

You can ignore the Fontforge warnings on open, and the fontforge warnings on font generation (just don't click the wrong button, because a cancel will dismiss the popup, but also cancel the font build ^^).

[Skydog]

Originally Posted by NiLuJe

You can ignore the Fontforge warnings on open, and the fontforge warnings on font generation (just don't click the wrong button, because a cancel will dismiss the popup, but also cancel the font build ^^).

It wasn't the warnings that had me concerned, just the errors generated. I figured I had botched it although a quick preview appeared normal.

Thank you!

[Skydog]

Originally Posted by Flaviocc

Here the steps - https://www.mobileread.com/forums/sh...81&postcount=9

I have the correct files here, but I think it's against the rules post Bookerly to download.

If you want, sent me a PM to give a link to download.

Done, thank you.

[Skydog]

Originally Posted by jackie_w

@Claude_C may be correct about this alternative naming convention. I seem to remember someone else posting the same thing a long time ago. I don't know where that info was originally documented.

I've never tested it myself because it was long after I'd already done the renaming/setting the hard way on the fonts I wanted to use. If it does work and can be done without needing FontForge it could be a good thing.

https://www.mobileread.com/forums/sh...+font+problems

[jackie_w]

Sigh, I just had to get to the bottom of it once and for all. Grit your teeth and read on if you're interested ...

Final conclusion:
If you want a sideloaded font to work correctly with both epub and kepub for all regular/bold/italic/bolditalic sub-families. Do 2 things.

1. Using Bookerly as the example, use the suffix naming convention
   Bookerly-Regular.ttf (or just Bookerly.ttf)
   Bookerly-Italic.ttf
   Bookerly-Bold.ttf
   Bookerly-BoldItalic.ttf
2. If it's faulty, fix the internal Panose Weight metric using some kind of font editor. @Flaviocc provided a link above to my old instructions for how to do it in FontForge

Other findings:
If the font's internal Panose Weight is faulty but it isn't something you're able/prepared to fix then you may still get regular/bold/italic/bolditalic sub-families to work in either kepub or epub, but not both simultaneously.

• Kepub only: use one of the 3 following suffix naming conventions.
  Either (as per Claude_C post)
  regular: Bookerly-a.ttf
  italic: Bookerly-b.ttf
  bold: Bookerly-c.ttf
  bolditalic: Bookerly-d.ttf
  or (ancient Windows convention)
  regular: Bookerly.ttf
  italic: Bookerlyi.ttf
  bold: Bookerlyb.ttf
  bolditalic: Bookerlyz.ttf
  or (as per DNSB post)
  regular: Bookerly.ttf
  italic: Bookerly-i.ttf
  bold: Bookerly-b.ttf
  bolditalic: Bookerly-z.ttf
• Epub only: use this suffix naming convention
  regular: Bookerly-Regular.ttf (or just Bookerly.ttf)
  italic: Bookerly-Italic.ttf
  bold: Bookerly-Bold.ttf
  bolditalic: Bookerly-BoldItalic.ttf

... and finally ...
Whatever method you use, don't forget to reboot the Kobo after updating any sideloaded font files in the fonts subdirectory.

ETA: All info correct at time of going to press, firmware 4.21.15015. No future performance guarantees

[Flaviocc]

... and finally ...
Whatever method you use, don't forget to reboot the Kobo after updating any sideloaded font files in the fonts subdirectory.

This!!! Yesterday I forgot to reboot and ....nothing works LOL

So....reboot and will work.

[Gone]

Originally Posted by jackie_w

Sigh, I just had to get to the bottom of it once and for all. Grit your teeth and read on if you're interested ...

Final conclusion:
If you want a sideloaded font to work correctly with both epub and kepub for all regular/bold/italic/bolditalic sub-families. Do 2 things.

1. Using Bookerly as the example, use the suffix naming convention
   Bookerly-Regular.ttf (or just Bookerly.ttf)
   Bookerly-Italic.ttf
   Bookerly-Bold.ttf
   Bookerly-BoldItalic.ttf
2. If it's faulty, fix the internal Panose Weight metric using some kind of font editor. @Flaviocc provided a link above to my old instructions for how to do it in FontForge

Other findings:
If the font's internal Panose Weight is faulty but it isn't something you're able/prepared to fix then you may still get regular/bold/italic/bolditalic sub-families to work in either kepub or epub, but not both simultaneously.

• Kepub only: use one of the 3 following suffix naming conventions.
  Either (as per Claude_C post)
  regular: Bookerly-a.ttf
  italic: Bookerly-b.ttf
  bold: Bookerly-c.ttf
  bolditalic: Bookerly-d.ttf
  or (ancient Windows convention)
  regular: Bookerly.ttf
  italic: Bookerlyi.ttf
  bold: Bookerlyb.ttf
  bolditalic: Bookerlyz.ttf
  or (as per DNSB post)
  regular: Bookerly.ttf
  italic: Bookerly-i.ttf
  bold: Bookerly-b.ttf
  bolditalic: Bookerly-z.ttf
• Epub only: use this suffix naming convention
  regular: Bookerly-Regular.ttf (or just Bookerly.ttf)
  italic: Bookerly-Italic.ttf
  bold: Bookerly-Bold.ttf
  bolditalic: Bookerly-BoldItalic.ttf

... and finally ...
Whatever method you use, don't forget to reboot the Kobo after updating any sideloaded font files in the fonts subdirectory.

ETA: All info correct at time of going to press, firmware 4.21.15015. No future performance guarantees

I should have mentioned that I only read Kepub.

That’s the convention that worked for me.

Maybe it also depends form where you got the Bookerly fonts, what version*?

[JSWolf]

Originally Posted by MGlitch

Because some of the issues are with how the fonts are named internally, not just their file name. I'm not sure if Bookerly was one such font, but it's been an issue in the past.

Yes, Bookerly is one such font. If I am not mistaken,it might just be the BoldItalic version that has the problem.

Does anyone know of a way to edit a font's metadata without having to save the entire font (in Windows)?

[JSWolf]

Originally Posted by DNSB

The alternate font file naming conversion would be:

Bookerly
Bookerly-i
Bookerly-b
Bookerly-z

The regular version of the font does not need the special naming but I prefer using -Regular just to keep things consistent.

It's a lot easier (IMH) to use the longform filename and a lot easier to know which version of the font it it based on the name.

[JSWolf]

Originally Posted by Skydog

I've spent the last two days reading older posts here on the Bookerly saga. In order to "fix" it for use with Kepubs, what steps exactly (as in Dummy 101) are required in FontForge? I've tried numerous times and end up with errors generated along with the new files. Do I need to change anything other than the first field "Fontname"?

Errors include: Self Intersecting; Missing Points at Extrema

I'm using v1.020 of Bookerly and attempting the naming convention from posts long ago and mentioned again in this thread:

Bookerly-Regular -> Bookerly-a.ttf
Bookerly-Italic -> Bookerly-b.ttf
Bookerly-Bold -> Bookerly-c.ttf
Bookerly-BoldItalic -> Bookerly-d.ttf

Any help would be greatly appreciated before I go bald from pulling my hair out!

Here is a solution that works. Plus, it's more readable and easier to remember.

Bookerly-Regular
Bookerly-Italic
Bookerly-Bold
Bookerly-BoldItalic

[JSWolf]

Originally Posted by Flaviocc

Here the steps - https://www.mobileread.com/forums/sh...81&postcount=9

I have the correct files here, but I think it's against the rules post Bookerly to download.

If you want, sent me a PM to give a link to download.

That link is also not allowed in PM since you mentioned it in public.

[jackie_w]

Originally Posted by JSWolf

Here is a solution that works. Plus, it's more readable and easier to remember.

Bookerly-Regular
Bookerly-Italic
Bookerly-Bold
Bookerly-BoldItalic

But, Jon, the long-form suffixes don't work for kepubs unless the panose weight is also fixed - as I tried to say in my lengthy post #52.

[Flaviocc]

Originally Posted by JSWolf

That link is also not allowed in PM since you mentioned it in public.

Ok Jon,

I edited my post.

So, if you want, edit the quote pls.