OpenType

I continued working on this handwritten typeface and while I made alternates to replace double vowels before, I would prefer to replace both vowels individually.

So, right now I have the following feature:
sub a a by a_a;

/a_a features two variants on /a that are both different from the default /a. Essentially what I want to do is replace /a /a by /a.alt1 and /a.alt2 instead of /a_a, because I want to maintain the ability to apply tracking to all the letters.

Now, I actually have this feature working with the following code:
sub a' a by a.alt1;
sub a.alt1 a' by a.alt2;

A new version of DTL OTMaster (OTM), the highly sophisticated tool for reviewing, editing, and altering tables and glyphs of fonts with a SFNT-file structure, has become available since today. OTM is a must-have for professional font developers. To quote Adam Twardoch, product and marketing manager at Fontlab Ltd.: ‘OTMaster works with surgical precision: it will only modify the portions of the font that the developer wishes, leaving all other structures unchanged. This makes OTMaster a great companion to any font editor and an indespensable element even in the most complex OpenType font production workflow.

Version 5.0 contains a range of additional functionality, among which:

https://vimeo.com/112368411

interesting to show opentype features physically.

https://vimeo.com/112368411

interesting to show opentype features physically.

I'm currently experimenting with the best position to set anchors in an OpenType font.

Now, when I ask the app Glyphs to place my anchors, it takes the width of the total letter, and set the anchor in the middle of the width.
And it does the same for the punctuation.

But when the punctuation (automatically) is merged on the letter, this default behaviour does not always result in the best combination: some punctuation has to shift to the left, other to the right.

Are there some guidelines for the best placing of the anchors or is it totally up to the taste of the designer? (Read; the designers eye...)

I think I'm getting to grips with OpenType coding - I just birthed my first contextual one-to-many substitution, and am as proud as you'd expect - but I'm still puzzled by one thing and unsure about another.

The puzzle is that when I define-and-run a lookup, the layout engine goes back to the start of the glyph run, as I'd expect. But when I call a lookup, it doesn't, at least in FontLab. Is that just how it is?

The uncertainty is over whether all kinds of lookup types are allowed in all features, or whether it's better to stick to the lookup types specified for features at the Microsoft OT spec site. I know FontLab is liberal, but are all apps?

Thanks very much for any help!
George

Former Typophile moderator Zara Vasquez-Evens has written an interesting article on Medium (https://medium.com/@CommandZed/thoughts-on-an-improved-opentype-ui-c6748...), prompted by the recent petition for a better user interface for accessing OpenType features in design software (http://ilovetypography.com/2014/10/22/better-ui-for-better-typography-ad...).

A few selected quotes:

Martin Silvertant's picture

Mapping fists

So, as a sort of oddity I'm adding fists/manicules to my latest typeface and I figured arrows would be handy as well. Now, I have them mapped with the appropriate unicodes as far as possible. To make them more accessible I figured I would create a stylistic set so you can type >> to make an arrow. However, when I add the code and I click on compile OpenType program it tells me it has to abort because of errors.

I must be doing something wrong. How do you usually map these kind of symbols to OT functions, or don't you?

feature ss07 { # Stylistic Set 7
# DEFAULT
sub > > by arrowright;
sub < < by arrowleft;
sub > > > by blackmaniculeright;
sub < < < by blackmaniculeleft;
} ss07;

I'm making a big multilingual sans serif and by default, the "a" and the "g" are double storey. I do include the single story versions available by "salt" because this feature works virtually everywhere, where there is Opentype).

However, I've heard that the Germans mostly use the single story g. I've searched pictures of various street signs in Germany and Austria and I haven't found any double story g's.

Would it be ok to include 'locl' feature for German language to substitute only the g (while leaving the "a" double story)? I do understand that the single story g has its roots in Fraktur. And is it a German-only preference or the neighbour languages like Dutch, Danish, Swedish, etc. look more natural with a single storey g?

Deus Lux's picture

Help with OpenType fractions

If I generate an OTF font, and I have a glyph created for onehalf, will "1 slash 2" automatically be replaced by onehalf, or do I need to build a feature for it?

Tried building a feature, but an "aborting because of errors" error:


feature frac {
lookup frac1 {
sub one slash 2 by onehalf;
} frac1;
lookup frac1;
} frac;

Also, what is the easiest way to code for all "(number) slash (number)" to change into nut fractions? I'd like this to work up into the thousands (333/1028 for example). Creating a "sub" line of code for every possible fraction is obviously impractical.

Hi everybody! I am happy to announce the release of Cavatina: an experimental font for musical notation. It is the result of two years of work in design and programming.

I'm wondering if it's possible to script any advanced features. Primarily I'm looking to solve a specific problem, but more generally I'm curious if more can be done with OT scripting than the standard "sub" script to replace one glyph with an other.

I'm tired of people over-hyphens so I wanted to script a fix for that, so in the standard ligatures I put the following code:
sub comma hyphen by comma_endash;

This replaces the comma followed by a hyphen with a ligature glyph where I have a comma followed by a line which is in between the hyphen and the en dash in length, which is more appropriate for denoting prices ($50,–).

To preface, this is my first post to the forum and I've done a fair amount of digging on the issue, but haven't found any solution to my question. Apologies in advance if it has been answered somewhere else. And I must say, that the community here has been extremely invaluable so far!

I have designed Titling Alternates (labeled titling in OpenType Classes) for the Uppercase (upcs in OpenType Classes) glyphs in my font.

For this, my feature is as follows:

feature titl { sub @upcs by @titling; } titl;

Wallington Typeface

Hey guys! allow me to introduce my first release font.

Wallington is a decorative-serif font embodying vintage and elegant curves with functional structure. Inspired by Old English cultures and their descendants between the mid-5th century and the mid-12th Century. Made up of two styles, Wallington Regular that consists of 491 glyphs and Wallington Small Caps with 365 glyphs. All glyphs are divided into several OpenType features such as Ligature, Contextual Alternates, Old Style Numeric and some astonishing special characters that allows you to mix and match pairs of letters to fit your design.

Find out more : http://ink.creativezeune.com




I'm still working on an upcoming typeface called Melk Sans. I had major issues before which have been fixed, but today I noticed a minor issue and I'm puzzled as to what is the cause. I thought I would start this thread not only to ask for feedback on this issue, but to ask other questions as well.

I have default oldstyle figures and lining figures in a font. Due to its particular constructed nature, the glyphs for 6 and 8 are each identical in both styles. Can anyone think of a reason why I shouldn't leave out six.lnum and eight.lnum altogether, and omit their substitutions from the feature?

From the 1st of July till 21 September the latest edition (3.7) of DTL OTMaster will be offered with a 50% discount on the standard licensing price of €255.

Version 3.7 contains a lot of new functionality. From the import/export of Ideographic Variation Sequences (IVS) to the editing of feature parameters, and from an autohinter for edited or newly added glyphs to support for COLR+CPAL tables. One can read about all details in Karsten Lücke’s wonderful manual.

Hello, i am new to OT features and everything that that means. I need to know if the letter I just typed is the first letter of a 'paragraph', and by so, make a sustitution. Is that possible? Anyone can guide me on some docs I should strongly read?

thank you for your comments,

I want to use Stylistic Alternates on a program without OpenType support; namely, the alternate a and W/w on Raleway.
So I would like to make a copy of Raleway where the a and W/w are their alternates.
Is there a way to do it without expense, or is there another workaround solution?


I’d love to have same feature set in InDesign and Illustrator. I’d love to have the ease of use of Stylistic Sets, Character Variants, OT Dropcaps, Historical Forms, Historical Ligatures, OT Unicase and Nut Fractions. I’ve made this rather raw and quick mockup and I want to share it with you, fellow typophiles. I’m not affiliated with Adobe, these are just my thoughts on how to UI could work.

Maybe you have some other ideas? Firefox Nightly and some other browsers for example, supports almost all OT features by font-feature-settings: "xxxx";. So this support could be done. Maybe it’s possible to convince other software developers to support more OT features?

Hi there

I'm looking to add a simple alternate feature to a font. The font is purely uppercase but in the lowercase glyphs the font has one set of of alternates (also uppercase design).

We're not after any cutting edge attempts at randomisation, just a simple toggle effect, cycling through so every other time you type a letter the alternate displays. So typing "aaaa" will pull out "aAaA" from the glyphs.

I have looked through a lot of posts and articles and have found much useful information, but can't quite pin down the exact code. I understand it's quite simple and I'm almost there I think. I have created two classes - class1 (uppercase) and class2 (lowercase).

Now I believe I just need a simple piece of code to place here in the opentype panel:

feature xxxx {

I'm prototyping a cursive font where, at least on paper, any word with a "t" in it has the crossbar on the t extended to the left and right over letters as long as this fits; verticals in h, l, d, etc. will cut off the bar, so something like:

becomes something like:

I'm not entirely sure how to implement this, though. I was thinking of using many-to-many GSUB rules based on glyph classes, but no matter how I look at it, it turns into needing recursive GSUB behaviour...

1) t [low] ->[t with bar that continues right] [low with left-connecting overbar]

I made a font recently and it worked fine. Then I decided to do the Arabic unicode block, then the Arabic presentations A and B.
Now that I generated the font, Word crashes (but not InDesign) when I copy an arabic text (from Wikipedia) and paste it in a document using my font. I used UnicodeView and the Character Map to see the font and it all works, except when selecting the Arabic block (0600 - 06FF). CharMap crashes and Unicode View fills the screen with error messages saying some dll crashed and a memory segment was violated, blah blah blah.

We have a situation where our identity font is displaying terribly in Microsoft 2010 on Windows 7. The font looks great in InDesign and Illustrator. The font family is OpenType with PostScript outlines, aka CFF. This behavior is consistent for any OpenType font from Adobe, ie Myriad Pro or Adobe Garamond.

I am nearly certain that the Windows font rendering engine is optimized for TrueType outlines and renders PostScript outlines poorly. I also think that Adobe is using a different rendering engine for the Creative Suite applications, perhaps their own. I have not been able to find any specific documentation of these statements.

Does this ring true? Does anyone know of specific documentation of poor font rendering in Windows applications, especially MS Office?

Hi there,

I would like to ask if someone has a recipe for exploring a content of OpenType font. OK, I know, that the Glyph Panel in InDesign is pretty comprehensive — I can filter the Small Caps, I can filter Oldstyle Figures, I can filter Ornaments, or even Ligatures , but I am looking for some way to get a summary like this:

FontName.otf:
This font contains:
Extended Latin A & B
Greek
Discretionary Ligatures
Oldstyle Figures
Small Caps

Thank you.

Syndicate content Syndicate content