John G. Otto
> >> Have Marco or Roozbeh looked at the ATSUI
> >> docs at the Apple dev site? http://developer.apple.com
> >> It's interesting how their approach corresponds to and
> >> differs from that one.
>
http://developer.apple.com/techpubs/macosx/Carbon/text/MultilingualTextEngin
e/Multilingual_Text_Engine/Concepts/Multilingual_Text_Eng-52.html
I don't know ATSUI very well.
When I studied it a little bit, my main goal was to try and understand the
similarities and differences between OpenType, ATSUI and Graphite: probably
the three most important smart font systems now in existence.
Notice that what I had in mind (and perhaps also Roozbeh) is only partially
*alternative* to smart font systems like ATSUI.
On the contrary, the two approaches could well live together, and even
benefit of each other.
The main drawback of ATSUI, in my humble opinion, is that any single font
contains the whole story of how each "complex script" works. This allows for
the greatest flexibility, but also maximizes memory requirements and
occasions for bugs or misinterpretations.
On the other side, the approach that I have in mind is too simplicistic. In
its "pure state" it could only be used to fill very basic rendering needs
(e.g., 2-line LCD displays).
But the two things together could win by coupling the simplicity of a basic
*standard* rendering algorithm, with the flexibility of a complex
typographical system.
_ Marco
This archive was generated by hypermail 2.1.2 : Fri Jul 06 2001 - 00:17:15 EDT