I actually used Affinity Photo/Designer on Mountain Lion a few years ago sometimes, but not for typography. I don't remember having had serious problems with Type 1 on Mountain Lion. I could check that out but it will unlikely be any better than on El Capitan. I still have a bootable USB stick with a clone of my old drive upgraded to Sierra, incl. Plus, you should fix the spacing, and use kerning classes, and the issue will probably go away.Ĭan you easily test pre-Mojave and/or Mojave and some earlier Adobe app behavior so that we could determine if there is some definite point when kerning support for Type 1 has ceased on macOS? Yes, it should probably work, but it is not likely this will get developer attention because it is such an odd case.
Recommend you watch it, and apply the concepts that she is teaching.Ĭonclusion: ADesigner has a problem with the kerning code. The sound is kinda bad, but she is master font developer who is definitely one to listen to and to emulate.
#Fontforge kerning how to
Laura Worthington (an expert designer of script fonts) has a video on YouTube on how to create script fonts that fit properly. Typically with monoline handwriting fonts all, or most, of the lowercase fits together in any order with no kerning at all. If everything has to be kerned, something is wrong with the basic character widths. This leads me to believe there may be some conflicting duplicates in there.Īll the tools are for managing kerning classes, not a bunch of sub-tables.įinally, and this is more font design best practices, kerning should not be used to compensate for bad spacing. Technically it should probably work, but it is a bit odd, and obviously the Affinity apps don't like it.įontCreator shows 1,197 kerning pairs FontLab shows 1,160. You have zero classes, and 48 sub-tables. Larger fonts may have many kerning classes (80 or more in a larger font with 5-6 times more glyphs than yours),Īnd then really large fonts may have multiple sub-tables to help organize things even more. Typically simple smaller fonts will have a number of kerning classes, and all of those are in one subtable. Why it only affects the OTF file I do not know. Second, yes, I can see the kerning issue with the OTF font when testing in APub.Īnd I think this is due to the odd way the kerning is done is confusing APub, or Designer. You should have one source file and output the different formats.īut I did not see any glaring differences which would explain the issue. There are a few issues.įirst, the two fonts do not have the same glyphs, which is a bit odd. Thank you so much for your took a look at the fonts. Is this a bug or are there more specific settings? Only in the whole affinity family (photo, publisher, designer) has a problem Sunting 3: Jadi, untuk memperjelas, versi OpenType TT (.ttf) berbeda kerns (benar?) Dari versi OpenType CFF (.otf). Sunting 2: Saya menduga hal semacam itu yang Anda maksud, karena file font lain yang Anda berikan terlihat seperti ini di Designer: Salah satu tes yang saya lakukan adalah dengan pasangan karakter cj, misalnya, yang menurut program desain font saya, Anda telah menentukan agar terlihat seperti ini:ĭan yang terlihat seperti ini di Designer: Sunting: Saya mungkin mengerti maksud Anda, tapi ingin lebih banyak umpan balik. otf dari font tersebut tampaknya berfungsi untuk saya, jadi memiliki hal tertentu untuk dilihat akan membantu. Bisakah Anda lebih spesifik tentang sesuatu yang tidak berhasil? Dari pengujian cepat, kerning dalam versi.
0 kommentar(er)
