Cocoa mail archive
Re: Helvetica - International Systems?
FROM : Philip George
DATE : Mon Nov 18 07:36:00 2002
True, but I would rather handle the problem transparently and then
answer questions about it in an FAQ or something like that. Another
thing to keep in mind is that I'm only loading the font for the use of
my app (kFMLocalActivationContext). The rest of the system can't even
see it. It's also unlikely that someone would be able to distinguish
which font this is. It's pretty small in the context I'm using it. It
looks like any one of a dozen other sanserif fonts. And again, any
questions could be easily addressed in an FAQ or support article, for
the extremely rare case that someone would notice, let alone be
bothered by it.
Thanks for the concern. At this point though, I'm probably more
interested in getting advice on the copyright stuff.
- Philip
On Monday, November 18, 2002, at 09:00 AM, Bob Ippolito wrote:
> If I were an advanced font user that intentionally disabled Helvetica
> (if there were ever a legitimate reason to do so), I'd probably be
> more confused (or even frustrated) if the app still rendered Helvetica
> properly rather than erroring out or doing ugly font substitution.
>
> -bob
>
> On Monday, Nov 18, 2002, at 09:51 America/New_York, Philip George
> wrote:
>
>> That's a valid point. I agree with it totally, but there's just
>> something about an app that's resilient in its own right, you know?
>> It's comforting when an app can deal with sticky situations like that
>> transparently, without the user having to even think about it, let
>> alone worry about it.
>>
>> But I see your point, and it's a solid backup if Plan A doesn't work
>> out. :)
>>
>> On Monday, November 18, 2002, at 08:35 AM, Bob Ippolito wrote:
>>
>>> Why don't you just detect the presence of Helvetica and error out,
>>> with a user-friendly error message, if it's not present. The rare
>>> potential user that may do something ridiculous like disable
>>> Helvetica will certainly be familiar with the consequences and know
>>> how to enable the font and restart your application.
>>>
>>> On Monday, Nov 18, 2002, at 09:15 America/New_York, Philip George
>>> wrote:
>>>
>>>>
>>>> For clarification, this app has REALLY tight margins in a few spots
>>>> where the font had to be very carefully chosen/sized/positioned.
>>>> Just letting any old font take its place may or may not work
>>>> (usually not). That's why I'm so nervous about it not being there.
>>>> And now that the code is written and streamlined, I'm finding it
>>>> extra hard to comment it out.
>>>>
>>>
>>> _______________________________________________
>>> MacOSX-dev mailing list
>>> <email_removed>
>>> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>>>
>>
>> _______________________________________________
>> MacOSX-dev mailing list
>> <email_removed>
>> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>
>
DATE : Mon Nov 18 07:36:00 2002
True, but I would rather handle the problem transparently and then
answer questions about it in an FAQ or something like that. Another
thing to keep in mind is that I'm only loading the font for the use of
my app (kFMLocalActivationContext). The rest of the system can't even
see it. It's also unlikely that someone would be able to distinguish
which font this is. It's pretty small in the context I'm using it. It
looks like any one of a dozen other sanserif fonts. And again, any
questions could be easily addressed in an FAQ or support article, for
the extremely rare case that someone would notice, let alone be
bothered by it.
Thanks for the concern. At this point though, I'm probably more
interested in getting advice on the copyright stuff.
- Philip
On Monday, November 18, 2002, at 09:00 AM, Bob Ippolito wrote:
> If I were an advanced font user that intentionally disabled Helvetica
> (if there were ever a legitimate reason to do so), I'd probably be
> more confused (or even frustrated) if the app still rendered Helvetica
> properly rather than erroring out or doing ugly font substitution.
>
> -bob
>
> On Monday, Nov 18, 2002, at 09:51 America/New_York, Philip George
> wrote:
>
>> That's a valid point. I agree with it totally, but there's just
>> something about an app that's resilient in its own right, you know?
>> It's comforting when an app can deal with sticky situations like that
>> transparently, without the user having to even think about it, let
>> alone worry about it.
>>
>> But I see your point, and it's a solid backup if Plan A doesn't work
>> out. :)
>>
>> On Monday, November 18, 2002, at 08:35 AM, Bob Ippolito wrote:
>>
>>> Why don't you just detect the presence of Helvetica and error out,
>>> with a user-friendly error message, if it's not present. The rare
>>> potential user that may do something ridiculous like disable
>>> Helvetica will certainly be familiar with the consequences and know
>>> how to enable the font and restart your application.
>>>
>>> On Monday, Nov 18, 2002, at 09:15 America/New_York, Philip George
>>> wrote:
>>>
>>>>
>>>> For clarification, this app has REALLY tight margins in a few spots
>>>> where the font had to be very carefully chosen/sized/positioned.
>>>> Just letting any old font take its place may or may not work
>>>> (usually not). That's why I'm so nervous about it not being there.
>>>> And now that the code is written and streamlined, I'm finding it
>>>> extra hard to comment it out.
>>>>
>>>
>>> _______________________________________________
>>> MacOSX-dev mailing list
>>> <email_removed>
>>> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>>>
>>
>> _______________________________________________
>> MacOSX-dev mailing list
>> <email_removed>
>> http://www.omnigroup.com/mailman/listinfo/macosx-dev
>
>
