Own fontsuite with standalone ?
gjbalzano at popmail.ucsd.edu
Wed Mar 30 16:04:47 CST 2005
Well, my face is a little red here ... somewhere in the back of my mind
I knew that ".dll" files were associated with Windows, but I suppose I
let wishful thinking get in the way of processing that information
Certainly, on Macs I know I can copy the file to the Fonts folder, but
then one generally needs to relaunch the application to gain access to
the font. I was just looking for a more userly-transparent way to
provide — possibly only temporary — access to a font that I am really
attached to using but which I can't assume will be present on host
computers. The other downside to copying files to people's Fonts
folders is that it seems a tad intrusive, although I suppose other
applications do such things all the time. Dynamic, temporary access to
special fonts was what I was looking for ... oh, well.
On Mar 30, 2005, at 12:06 PM, Ken Ray wrote:
> On 3/30/05 1:21 PM, "Jerry Balzano" <gjbalzano at popmail.ucsd.edu> wrote:
>> But then when I tried
>> • ext_loadFont "/Users/jerry/Desktop/KillerStumps.ttf"
>> I received the familiar "can't find handler" error message.
> Uh, Jerry, take a look at your path. That's an OS X path being used
> for a
> command that only works on Windows.
> Additionally, any external that ends in ".dll" is WIndows only;
> for Mac usually end in ".bundle".
> Soooooo, if you want to try loading fonts on Windows, use ext_loadFont
> a windows path (like "C:/Documents and Settings/All
> Users/Desktop/KillerStumps.ttf"). As to loading fonts on OS X, I would
> assume you can just copy the file to the proper Fonts directory.
More information about the use-livecode