[OS X TeX] Minion Pro and Bickham Pro (problem)

[Richard Seguin]

On Apr 24, 2012, at 12:52 AM, Richard Seguin wrote:

> 
> On Apr 23, 2012, at 11:53 PM, Michael Sharpe wrote:
> 
>> 
>> On Apr 23, 2012, at 8:18 PM, Richard Seguin wrote:
>> 
>>> 
>>> On Apr 15, 2012, at 3:00 PM, Michael Sharpe wrote:
>>> 
>>>> 
>>>> On Apr 15, 2012, at 9:39 AM, Richard Seguin wrote:
>>>> 
>>>>> Thanks for the sample! The sample actually looks pretty good. I opened the attachment in Preview and greatly enlarged it. If anything, it might be slightly too light, but as close to perfect as any other script I've looked at. I looked at the semibold version on the Adobe website and I think it would be too heavy -- more too heavy than the regular weight is too light. It appears to me that the regular version would print well at 9 and 10pt, or at least as well as boondox. (For example, my old ps type 1 Linoscript does not print well at 10pt and below.)
>>>>> 
>>>>> I'm using the very latest TeXLive, I already have TeXFontUtility, FontForge, and the bickram.zip file from ctan. If I were to install this .otf font (changing the tilt angle to 20% as you suggest), what would be my easiest and most idiot proof overall route? I've looked at bickham-doc.pdf and TeXFontUtility.pdf and am a little unsure.
>>>> 
>>>> When you have the otf, you need to convert it to a pfb using cfftot1 that comes with TeXLive. So, open a Terminal window and cd to the folder containing your otf and type
>>>> 
>>>> cfftot1 BickhamScriptPro-Regular.otf BickhamScriptPro-Regular.pfb
>>>> 
>>>> which will create the required  pfb. If you have already installed the bickham package in texmf-local, you need to copy the pfb to the the correct place in that TDS with the command
>>>> 
>>>> sudo cp BickhamScriptPro-Regular.pfb /usr/local/texlive/texmf-local/fonts/type1/adobe/bickhamscript
>>>> 
>>>> followed by
>>>> 
>>>> sudo mktexlsr
>>>> 
>>>> You do of course need to enable bickham.map with
>>>> 
>>>> sudo -H updmap-sys --enable Map=bickham.map
>>>> 
>>>> (The bickham package contains all the virtual fonts, ready and waiting for the physical pfb.)
>>>> 
>>> 
>>> Right now I'm trying to install the Bickham semibold version, and have run into an odd problem, following the same procedure as above. When I cd to the folder containing the .otf version and attempt to run cfftot1, it tells me that the file is not there. But when I do an ls, the terminal lists the file. What could be going on here? Here's the dialogue in the terminal:
>>> 
>>> Richard-Seguins-MacBookPro:~ richardseguin$ cd Desktop/InstallBickham
>>> Richard-Seguins-MacBookPro:InstallBickham richardseguin$ ls
>>> BickhamScriptPro-Semibold.otf
>>> Richard-Seguins-MacBookPro:InstallBickham richardseguin$ cfftot1 BickhamScriptPro-Semibold.otf BickhamScriptPro-Semibold.pfb
>>> cfftot1: BickhamScriptPro-Semibold.otf BickhamScriptPro-Semibold.pfb: No such file or directory
>>> Richard-Seguins-MacBookPro:InstallBickham richardseguin$ ls
>>> BickhamScriptPro-Semibold.otf
>>> Richard-Seguins-MacBookPro:InstallBickham richardseguin$ 
>>> 
>> 
>> Sorry, I don't have anything else to suggest here. II tried it here with result:
>> 
>> $ ls
>> BickhamScriptPro-Semibold.otf
>> $ cfftot1 BickhamScriptPro-Semibold.otf BickhamScriptPro-Semibold.pfb
>> $ ls
>> BickhamScriptPro-Semibold.otf	BickhamScriptPro-Semibold.pfb
>> 
>> Michael
>> 
> 
> The odd thing about this is that this worked fine with the regular weight version. It's time for bed, and maybe if I sleep on it …
> 
> Richard


OK, I finally got this to work. Last night I copied the cfftot1 command from Michael's original email, pasted it into TextEdit, and changed -Regular to -Semibold. Then I copied that string to the terminal to run the cfftot1 command, but cfftot1 kept saying that the file didn't exist. This morning I repeated this, and it worked. The spelling is identical to what I used last night, so I think the string I was pasting into the terminal was corrupted somehow even though it was displaying OK on the screen. Weird. I think in the past and in other contexts I've (rarely) encountered corrupt text strings that nevertheless displayed OK on the screen.

Richard