Re: 'fi' ligatures [solved]
Re: 'fi' ligatures [solved]
- Subject: Re: 'fi' ligatures [solved]
- From: Dave Rehring <email@hidden>
- Date: Tue, 03 May 2005 21:54:46 -0700
On 5/2/05 5:02 AM, Jonathon Mah at email@hidden wrote:
> On 2 May 2005, at 00:42, Andrew Thompson wrote:
>
>> Ah, now that makes sense. I can see why you wouldn't want ligatures
>> in plain monospaced text.
>> I don't think it's a bug with variable width fonts, because whether
>> the glyphs are rendered with ligatures or not has no bearing on the
>> plain old character data in the plain text file. But, of course,
>> with a monospaced font it'd be a disaster, since the whole point is
>> the look of the glyphs.
>
> Hmm, I have the same problem. I use ProFont (which is monospaced) and
> in TextEdit it seems ligatures are enabled by default. (For example,
> 'file' becomes three glyphs, taking up the width of three glyphs.) I
> can turn this off with Format > Font > Ligature > Use None. Perhaps
> there should be an option to make this the default for plain text files?
>
Thanks. This was driving me nuts in Terminal, as I like using ProFont for
that as well. It would combine some characters with a '/', which would
totally screw up viewing a bunch of common paths.
Tracking down the ligatures panel, and disabling that option seems to have
fixed the problem for me with Terminal.
Later,
--
David Rehring Psychos do not explode when light hits
VP of Research and Development them, no matter how crazy they are...
Atimi Software, Inc.
www.atimi.com And totally insane guy!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden