[XeTeX] Strangeness with Minion Pro Opticals Small Caps

[Jonathan Kew]

On 20 Aug 2006, at 11:42 pm, Peter Heslin wrote:

> Ralf Stubner
> <ralf.stubner at physik.uni-erlangen.de> writes:
>
>> $ otfinfo -v MinionPro-*.otf
>> MinionPro-BoldIt.otf:Version 2.015;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.7.9032
>> MinionPro-Bold.otf:Version 2.015;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.7.9032
>> MinionPro-It.otf:Version 2.015;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.7.9032
>> MinionPro-Regular.otf:Version 2.015;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.7.9032
>>
>> as well as
>>
>> $ otfinfo -v MinionPro-*.otf
>> MinionPro-BoldIt.otf:Version 2.012;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.6.6565
>> MinionPro-Bold.otf:Version 2.012;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.6.6565
>> MinionPro-It.otf:Version 2.012;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.6.6565
>> MinionPro-Regular.otf:Version 2.012;PS 002.000;Core  
>> 1.0.38;makeotf.lib1.6.6565
>>
>> The former came with my AR 7.0.8 installation. The latter came  
>> with some
>> previous version. None of them shows such problems here, though.  
>> Would
>> be interesting to know which version Peter got from AR.
>
> The AR font that gave me the bad output looks to be the same as your
> previous version:
>
> MinionPro-BoldIt.otf:Version 2.012;PS 002.000;Core  
> 1.0.38;makeotf.lib1.6.6565
> MinionPro-Bold.otf:Version 2.012;PS 002.000;Core  
> 1.0.38;makeotf.lib1.6.6565
> MinionPro-It.otf:Version 2.012;PS 002.000;Core  
> 1.0.38;makeotf.lib1.6.6565
> MinionPro-Regular.otf:Version 2.012;PS 002.000;Core  
> 1.0.38;makeotf.lib1.6.6565
>
> I'm puzzled that these give me bad results with small caps, while the
> same fonts work for Ralf.

So am I.

How about if you each create an MD5 checksum of your "MinionPro- 
Regular.otf:Version 2.012" fonts, so we can see whether they really  
are identical, or if there's some internal difference despite the  
matching version info?

You're running on Windows, Peter - right? Any chance you can find a  
Linux or Mac OS machine to try the "problem" version of the font, so  
we can check whether it behaves the same on all platforms? (It  
should, but this is strange enough that I don't know what to suspect.)

(And if you're installing the fonts, rather than using the new  
"[filename.otf]" method to load them directly from a known location,  
then please double- and triple-check to make absolutely sure there's  
no other copy installed somewhere, so that we're not necessarily  
testing the version we think!)

JK