August 13, 2012
This is a brief summary of my experiences as an attendee at this year’s TypeCon in Milwaukee.
My arrival to Milwaukee on Wednesday night was followed by immediate degustation of Milwaukee brats and beer; which is a promising start for any type conference. It is a great idea to start the main conference with a keynote in the evening because it gives people a chance to do some sightseeing and squeeze in some type-related activities before the events kick off. Continue reading…
November 4, 2011
Even though InDesign’s linguistic support is reasonably extensive, it covers only a few dozen of the world’s languages. Out of the box you’ll find support for most Western languages, from Bulgarian to Ukrainian, and if you happen to be using a Middle-Eastern (ME) version, you’ll also have support for Arabic, Farsi and Hebrew.
List of the languages supported out of the box by InDesign CS5.5
But what about other Arabic languages such as Urdu and Uyghur? Or Indian languages such as Hindi or Tamil? Or even other European languages such as Gaelic? Is it possible to enable those? The answer is yes, and there are two ways of doing it.
August 29, 2009
Finally. Yesterday, Friday, August 28th, 2009 is significant, at least for me, in that it represents the release date for Mac OS X Version 10.6 (aka, Snow Leopard). What is important about Snow Leopard is that it is the first OS that provides built-in support for IVSes (Ideographic Variation Sequences). Up until now, IVSes had been supported in specific Adobe products, such as Acrobat Version 9.0 and Adobe Reader Version 9.0 in the context of Forms, Flash Player Version 10, and InDesign CS4.
For those who are unaware of IVSes, they represent standardized Unicode behavior that allows otherwise unencoded variants of CJK Unified Ideographs to be represented using “plain text” that survives conditions that would cause rich text to fail. IVSes are registered via IVD (Ideographic Variation Database) Collections. The first IVD Collection to be registered at the end of 2007, was Adobe-Japan1, and is currently aligned with the Adobe-Japan1-6 character collection. See: http://www.unicode.org/ivd/
OpenType Japanese fonts can be IVS-enabled by building a Format 14 ‘cmap’ subtable. The AFDKO tools (in particular, MakeOTF and spot) are IVS-savvy, as well as DTL OTMaster (and the Light version).
May 8, 2008
Periodically somebody asks how InDesign prioritizes fonts whose names conflict, or what consistutes a conflict, and nobody knows. Recently David Blatner (InDesignSecrets.com, co-author of Real World InDesign, Real World QuarkXPress, etc.) asked the same question, and sparked me to pull together the answers.
There are three kinds of name conflicts in InDesign that cause fonts to potentially not show up in the font menu.
1) Duplicate PostScript FontName
2) Duplicate menu name (as shown in InDesign)
3) Multiple “regular”-like styles in a single family
The third case is a bit different, so we’ll take it separately.
April 3, 2007
Adobe InDesign® CS3 has a ton of new features, many of which can be seen on its Web site. But there are also many features that aren’t quite big enough to be seen on that august location. I thought I’d mention a few of them that are of particular interest to my fellow font geeks.