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,–).
Working on generating an OpenType PS font. Been troubleshooting this for over a week. Tried deleting all the classes and features then generating an OpenType PS font. It still gives me, "ERROR: There was a problem while compiling OpenType font. Final .otf font is not saved. Please, check OpenType features definition for errors." Reading through the manual, but still sure of the best way to proceed with troubleshooting – not clear on what to check or where the problem might lie. Thank you for any help.
The Font Testing Page is a tool primarily intended for type designers and independent foundries. It can also be used by art directors, graphic designers, teachers and students interested in seeing how a typeface works on the web.
There is a short video at:
Operation is simple:
- First, you must accept the request from the browser.
- Then drag the font you want to try to the upper area of the Testing Page.
Below you will find 8 buttons: Headlines, Text, Lowercase Only, Adhesion Only, Caps, All Caps, Layout and Kern.
- Headlines: Displays examples: 72, 60, 48, 36 and 30 to 12.
- Text: Displays text blocks, from 20 to 10.
- Lowercase only: Displays examples of 72, 60, 48, 36, 30, 24, 18 and 16 to 10.
In my current font project (a cursive conscript*), I have added the OpenType features [aalt], [init], [medi], [fina] and [liga] (along with the usual [kern]). These features compile without any errors and appear to work properly in the OpenType Features tab of the Preview panel (they don't preview properly on the Preview tab, but I've read on the FontLab forums that [init], [medi] and [fina] don't preview at all in FontLab Studio, but still work in applications), but when I generate the font (as a .ttf), none of them work in the applications I use this font in (Photoshop and Word '07-'10). It's as if they're not there. However, they appear in the relevant tabs when I open the .ttf in Studio, exactly as they are in my project file.
Some languages have problems with f-ligatures. One example is German, where ligatures across Wortfugen can be a source of confusion; another is Turkish, in which the dotless ı requires special treatment.
Have there been any efforts to identify (and compile a list of) such problems, and is it considered good practice to code those exceptions as language-specific OpenType alternates? Say, "ligatures for dflt, no ligatures for german"? Or would that go against users' expecations? How well are such features implemented in software at all?
Another solution, of course, is a Linotype ("Sabon") f, but you know, I do have a thing for nice fi and fl ligatures :)
I've been designing a few caps features for one of my text typefaces. Think of the Van Krimpen hyphen, and of course height-adjusted parens, middots, endash and emdash (with hopes of making cap-specific tabular numerals too — one day!). Question is, how do I go about naming them? hyphen.alt is too vague and might clash at some point. hyphen.caps? I was looking for examples, but after ten minutes in the Adobe specification site, I threw in the towel. Is there a convention?
Edited title to reflect proper nomenclature; post left intact to keep the thread sensible.
[Cross-posted with the UAFDKOML group]
I'm starting to receive some questions about features not working in InDesign CS5 when a non-Latin language or "No Language" is selected. And this is happening with fonts that worked fine in CS3 and CS4.
From the cases I've seen, the bugs were in the fonts. More specifically, the feature file code lacked languagesystem declarations. Regarding InDesign CS5, what I can tell you is that this version is more strict than CS3 and CS4 were in terms of dealing with language and script tags. So if the fonts don't have lookups for all the necessary languagesystems, ID CS5 will just stick to what's in the font rather than creating them on-the-fly, like CS3 and CS4 used to do.
Hello, i'm a new FontLab user. I made an opentype font with features but some of these aren't compatible with InDesign (for example: fina). There is a features list compatible with InDesign?? Or i'm in mistake? Someone can tell me what's the problem? thanks for the answers!