[mpeg-OTspec] Good news about CFR (aka ISO/IEC 14496-28:2012)

[Ken Lunde]

Suzuki-san,

Apple had the easiest time to support CFR because it was derived from their SplicedFont format. I am not sure to what extent CFR objects, or SplicedFont objects for that matter, were supported in Mac OS X prior to Version 10.8, but what Version 10.8 introduced is the ability to support user-installed CFR objects, and that CFR objects show up in application font menus (at least for applications that are supplied by Apple, such as Text Edit) and in Font Book.

And yes, interoperability with Mac OS X, in terms of recognized font resources, is the greatest motivation to support CFR objects in other OSes and environments.

Regards...

-- Ken

On Jul 28, 2012, at 5:40 AM, suzuki toshiya <mpsuzuki at hiroshima-u.ac.jp> wrote:

> Dear Ken,
> 
> It sounds quite interesting, because the posts from Apple to
> the discussion on CFR were not so frequent. The realization
> of CFR on Mac OS X is very good reason to promote it to open
> source society working with Unix variants, for the interoperability
> of the applications running on Mac OS X.
> 
> I was expecting some open source project around fontconfig
> would be the first implementation of CFR, but it was failed.
> Looking at the response from Android developers, the barrier
> of 64K glyphs is not widely recognized.
> 
> http://lists.freedesktop.org/archives/fontconfig/2012-July/004219.html
> 
> Ken Lunde wrote:
>> All,
>> 
>> Mac OS X Version 10.8 (Mountain Lion) is the first CFR implementation, and thus the first implementation to break the 64K glyph barrier. Many thanks to the folks at Apple for pulling this off. I wrote about it this morning on our CJK Type Blog. See:
>> 
>>  http://blogs.adobe.com/CCJKType/2012/07/cfr-support-in-mountain-lion.html
>> 
>> Regards...
>> 
>> -- Ken
>> 
>> 
>