Page 1 of 1

Font Family problem on VISTA

Posted: Mon Feb 22, 2016 4:20 pm
by Mike Thompson
I have prepared a font family of Regular, Bold, Italic and Bold Italic. It works on OSX 10.6.8 but not on VISTA (Home Premium SP2).
On VISTA a word processor will display the Regular ok but for the Bold it displays a faux-Bold based on the medium. Same with the
others. I put a different deliberate mistake into each font. They show the deliberate mistake that is in the Regular.

Any ideas?
Mike

Re: Font Family problem on VISTA

Posted: Mon Feb 22, 2016 4:54 pm
by MikeW
Hi Mike,

No idea beyond word processors generally being dumb things. What word processor? Are the Mac naming fields filled in? If so, is the normal naming fields agree, the italic/bold/bold italic check boxes checked as appropriate? Family names consistent? That sort of thing?

Mike

Re: Font Family problem on VISTA

Posted: Mon Feb 22, 2016 5:17 pm
by Mike Thompson
MikeW

The word processor I use on the PC is OpenOffice and the IMac I use TextEdit.

For the Bold font in the Font Properties window on the Identification tab I have checked Bold :-)

I' m stumped on this.

Mike

I opened the .odt file with Word and it complained the file was corrupt but nevertheless it was displayed
and saved as a .docx. The font family problem is the same with word

Re: Font Family problem on VISTA

Posted: Mon Feb 22, 2016 5:49 pm
by MikeW
Hi Mike,

Would you be willing to send me a private message with a link to the FC project files?

I am using Windows 10, but in my experience if Word or LibreOffice / OpenOffice doesn't like them on an earlier OS it doesn't on newer ones either.

Mike

Re: Font Family problem on VISTA

Posted: Mon Feb 22, 2016 9:52 pm
by Bhikkhu Pesala
Mike Thompson wrote:For the Bold font in the Font Properties window on the Identification tab I have checked Bold :-)
What is the weight set to on the Weight drop down? 700 bold is the usual setting.

Re: Font Family problem on VISTA

Posted: Wed Feb 24, 2016 2:13 pm
by Mike Thompson
Bhikkhu
Yes that fixed the problem. Thanks
Mike