![]() To get started, open Adobe Illustrator (preferably open your font design file with the characters as objects), and under Windows > Extensions, you’ll see your nifty new tool, Fontself Maker.įrom there, you’ll be able to select each character and assign it a letter, number, etc. Once you download and install the script, Fontself becomes an extension of Adobe Illustrator and/or Photoshop (depending on which package you purchase). All you say is "not here" BUT "the user can give a hint".Now that you’ve gone through the design process of creating your font characters, it’s time to make them fully functioning fonts! There are a few different sources you can use to finalize your fonts…įontself is a purchasable software that works seamlessly with Adobe Illustrator and Adobe Photoshop. There must be somewhere the knowledge how to construct the right lookup style and you are missing to tell us where this should happen. It seems that the other APIs are not that separate at all. But how does this API know which script applies for the call to tKerningValue(l,r,v)? Is there some hidden state, like a call to tActiveScript('ARAB') before? Or the unicode database? They do not justify the change suggested here. ![]() ![]() But all of these are really separate APIs. I'll add some more comments on unified-font-object/ufo-spec#16 with a more interesting examples (punctuation marks).įor script=Common characters, sure, the user can give a hint as to which punctuation and other marks one wants to be included in kern table for each script. And I'm not going to repeat that again :). So when encoding a lookup to be used under 'arab', it encodes the rightGlyph first. The code generating the feature files MUST know that under 'arab' script, first glyph is the rightmost one. Calling tKerningValue("ALEF", "REH", 50) does not help either as it will just result in an kern pair (which is not what we want here) and it will still be adjusting the rsb of the first glyph it sees. The API specifically says that the first argument is leftGlyph, and second argument is rightGlyph.īut there is no way to tell that in this pair will be on the right and will be on the left. How can I kern this pair with the proposed API? Naturally I’d be calling tKerningValue("REH", "ALEF", 50) ![]() Now, lets kern the Arabic (را) pair, here the first glyph in the pair will be but it will end up being the rightmost glyph, and the second is and it will end up being the leftmost glyph. How can I kern this pair with the proposed API? Naturally I’d be calling tKerningValue("REH", "ALEF", 50) but there is no way to tell that in this pair will be on the right and will be on the left. Now, lets kern the Arabic ( را) pair, here the first glyph in the pair will be but it will end up being the rightmost glyph, and the second is and it will end up being the leftmost glyph. Lets say I was to kern the Latin AV pair, here the first glyph in the pair is A which it will be the leftmost glyphs, and the second is V which will be the rightmost glyph, so nothing special is needed and I’ll be calling tKerningValue("A", "V", 50). But the fact that the glyph being adjusted will end up being the rightmost or leftmost glyph in this case is only known at the layout time when the glyph stream is reversed (the font developer knows this beforehand of course because he can tell which glyphs will be used in RTL context). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |