September 10, 2008
We’re looking for some feedback from the font developer community on how you want the AFDKO/FontLab/FontMaster code syntax to work for mark attachment. Please comment! Comments received by Friday September 29th will be most likely to influence our implementation.
In OpenType fonts, mark attachment is the GPOS (glyph positioning) rule which dynamically positions diacritical marks (accents and the like) relative to base characters or other marks.
The currently available version of Adobe’s Font Development Kit for OpenType (AFDKO) does not support OpenType mark attachment. Hence, other tools based on the AFDKO, such as FontLab or DTL FontMaster, do not support it either. We’re currently implementing such support, which will in turn determine the underlying code used by such third party tools. This also means extending the syntax of the AFDKO language to represent mark attachment. However, mark attachment is complicated, and gets even more so when one makes it contextual. The best way to represent it in the same style as other AFDKO code is not entirely clear. Here’s what we’d like your feedback on.
(Special thanks to Read Roberts, AFDKO engineer, for the remainder of this post!)
June 5, 2008
Some folks have been asking, so I thought it would be handy to summarize the language and OpenType layout support in the Flash Player 10 public beta.
June 8, 2007
Very quietly a couple of years ago, with Acrobat 7.05, Adobe shipped Adobe Arabic, an original OpenType typeface commissioned by Adobe with production by Tiro Typeworks, created by type designer Tim Holloway with Fiona Ross and John Hudson. The typeface won recognition from the TDC and has generally been well received.
Tiro recently had inquiries about showing the VOLT source code for Adobe Arabic to a third-party font developer. We’re fine with that, but we thought that to be fair to all developers I should simply post the code here for any interested party. So here you are (73K Zip file).
May 6, 2007
Every couple of years in June there’s this cool typography conference in Thessaloniki, Greece. Well, maybe more tropically warm, but you get the idea. This year, besides the conference and other events June 18-24, there’s a Greek type design contest. Luckily, you don’t even have to do a full typeface, just these words: ένα αναμφισβήτητα ξεχωριστό γεγονός.
The contest has a bunch of categories (text, display, pixel, experiemental) and you’re free to do anything from a traditional font to photography, video, animation or CGI. The deadline is May 31st, and there are valuable prizes. Details here (note the links at the top for all the different sections). Thanks to Eirini Vlachou for the tip!
In related news, the Type Directors Club in NYC is holding the second in a series of “Non-Latin Weekend” type design seminars, Oct 5-7. This time it’s Gerry Leonidas, on Greek type design. This is the same guy who consults for companies such as Adobe and Microsoft to help us get our Greek typefaces looking good. I’m hoping we can send two or three people, because this is sure to be worthwhile for anybody who would like to design Greek typefaces (or typefaces that include Greek, as most of ours do these days).
April 5, 2007
I know, my TypeKey comment authentication set-up wasn’t working. Plus it would have been a bit of a pain even if it was working. So, I’ve turned it off. At least I have more time to cope with the spam now….. :/
January 16, 2007
As a means of dealing with the mountains of spam comments I get, I am (for now) resorting to comment authentication. This means that in order to make a comment, you need to sign in to TypeKey, a free service for such purposes.
I’m sorry for the inconvenience – I don’t like having to do a log-in at another site to post comments, either. But wading through the spam comments is time-consuming, and several times now I have missed a real comment amidst all the spam, which is Not Good. Perhaps we’ll get some more sophisticated automatic system in the future, but for now I’m going to use this.
I gather several other Adobe blogs are going to the same system; at least you’ll only need to sign in once.
November 17, 2006
People may suggest you delete the Adobe font cache files to attempt to fix certain problems – and indeed, under some uncommon circumstances, an Adobe font cache file may get messed up. These font cache files are AdobeFnt*.lst files (where “*” may be nothing, or may be a two-digit number).
However, there are two files with simjilar names, but ending in “.db”, which are not caches, are not subject to any kind of corruption that we know of, and should not be deleted. AdobeFnt.db and and FntNames.db are both static database files used by InDesign. Deleting them, especially FntNames.db, can cause serious problems.
So what are these database files?
May 22, 2006
A few weeks ago, I had reason to record one of my sort of standard demos of OpenType features, for internal use. Today’s post is about why and how I did it, using Captivate.
May 12, 2006
I’m cross-posting this with the OpenType mailing list to try to get a wider cross-section of views.
As has been mentioned here and elsewhere, in new fonts Adobe is moving away from using Unicode Private Use Area (PUA) encodings for glyphs that are alternates or variants of another glyph that is encoded as the default form for a character. About the only thing we’d use PUA for in new fonts would be ornaments or dingbats that really don’t have their own codepoints.
We’re working on a general tune-up of our whole type library, and one of the questions which arose is, should we make such a change in revising already shipping fonts?
December 23, 2005
With Unicode and OpenType, there are specifications about how certain things should be done: particularly encodings and OpenType layout features. But some things are not as well or easily supported in applications, which leads to the temptation for font developers to “lie” about the encoding or alternate glyphs, in order to get something that works more easily. What specific kinds of lies are font developers tempted by, and is this lying a Good Thing or a Bad Thing?
I’ve been talking about this a lot lately in discussions on the public OpenType list and in the Typophile forums, and I thought I should put all my thoughts in one place.