Re: [Bug?] Text rendering under Cocoa
Re: [Bug?] Text rendering under Cocoa
- Subject: Re: [Bug?] Text rendering under Cocoa
- From: Stéphane Sudre <email@hidden>
- Date: Wed, 13 Nov 2002 18:40:10 +0100
On mercredi, nov 13, 2002, at 02:02 Europe/Paris, Bill Northcott wrote:
When I try here (10.1.5), I get both J's exactly the same; only with
Lucida Grande there seems to be a metric problem, which causes the
left
edge of the J to be somewhat into the letter, actually. Just try that,
try
also to place a space (or even better a letter, say, 'a') before the
first
J, and also try to select the J.
I don't think this is a bug. I think it is a result of the optical
H&J in
10.2.
In your example it looks silly. But then you are using nonsense text.
For
the run of real text, it looks better to have some characters project
slightly beyond the nominal margin while others are inset. The
Character
is not truncated as you can see by moving in the left margin. Optimal
typesetting is NOT fitting to exact geometric margins. It is what
looks
best.
Try having the next line start with a lower case y or t. You will see
it
is set slightly in from the geometric margin. This is actually
extremely
sophisticated typesetting and best left to experts.
Yep, but:
Lucida Grande is the System Font and it should be possible to draw a
text using the System Font without having to spend 2,000 lines of code
to take into account the potential fact that a glyph of the font is not
going to be fully drawn when you use drawAtPoint
With Mac OS 9, we were used to have a 4 pixels margin
(left,top,right,bottom) before the text was drawn. This is the reason
of my thinking.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.