Well speaking from the historical perspective I happen to know on the  
windows platform they were identical to the apple offering at the time  
of creation as rendered on the screen, pixel for pixel and width for  
width.

The characters should be formed identically to the apple ones, it  
appears some errors or fudge or issues in converting from the windows  
font files. Mind I do fuzzily recall I had to tweak character  
boundaries in windows 3.0 a decade back to get things just right, that  
might have been an issue in the conversion too.

Somehow could it be too much effort to compare each apple font  
character with the accu font equivalent character and adjust the widths  
and padding to match? Sounds like a interesting programming task.

Plus pick 12, versus 10 since 12 is the default in the apple fonts  
currently...

And does anyone know if the comments found in this method still work.

StrikeFont>>aComment
	"To read Mac font resources.
1) Use ResEdit in the Fonts folder in the System Folder.  Open the file  
of the Font you want.  (A screen font, not a TrueType outline font).
&
readMacFontHex: fileName


On Feb 19, 2004, at 9:43 PM, Duane Maxwell wrote:

> I think it's only a modest effort to get these fonts up to snuff  
> instead of abandoning them because of a few character flaws.  Don't we  
> all have those?
>
> -- Duane
>
>
>
>
>
--
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===