I agree with Chris 100%. When I took a look at the http://typeface.neocracy.org/ project and code, I was surprised at all the work they had put in to it. One problem with this approach is that it is so temporary -- as soon as @font-face becomes more widely supported, their solution will be largely obsolete. The other and bigger problem, as Chris pointed out, is there is no support for complex text layout. So they have all of this nicely written code with complete workarounds for both CANVAS and VML, and perhaps one year from now it will remain largely unused.
- Ed On Sat, Nov 1, 2008 at 12:19 PM, Christopher Fynn <[EMAIL PROTECTED]> wrote: > Dave Crossland wrote: > > > Do you think _not_ supporting things like that .js will help speed > > @font-face adoption? > > As much as possible, I'd like to see efforts *focused* on getting > widespread support for @font-face. > > As I see it partial solutions can remove some of the pressure for a more > comprehensive solution. > > I'm also not very keen on any font linking and embedding method that > doesn't support the needs of users of non-latin scripts - and in > particular the needs of users of complex (e.g. arabic & indic) scripts. > IMO, in this day and age, any font architecture which doesn't take > account of complex scripts is broken. > > > - Chris > > > > > > > _______________________________________________ > Openfontlibrary mailing list > Openfontlibrary@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/openfontlibrary >
_______________________________________________ Openfontlibrary mailing list Openfontlibrary@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/openfontlibrary
