"Destination font family contains more than one font with same style"

[switters]

I'm attempting to convert a PC TT to Mac TT.  The destination suitcase is red, and I get the following error message:

"Destination font family contains more than one font with the same style.  Please, use properties dialog to move conflicted styles to the separated families or check on the "Do not build families" checkbox in Preferences before the adding of fonts."

I'm not sure why I'm getting this error message.  There are not duplicate fonts in the suitcase.  Here's a screenshot of the properties dialog box:



If you could please tell me what I need to do to convert these fonts, I'd appreciate it.

[Alex Petrov (FontLab)]

You have five italics and three bolds in the family which is prohibited by Mac OS.
You need to manually organize families so that every unique Family Name has max of 4 fonts: plain, bold, italic and bolditalic.
See Adam's post for details:
http://forum.fontlab.com/fontlab-studio-tips-and-tricks/font-family-naming-in-fontlab-studio-5-t313.0.html;new#new

Unfortunately TransType cannot do this automatically.

[switters]

Thanks, Alex.  That solves the problem.

Chris

[switters]

Alex,

I'm having a similar problem with font style naming.  I have a big font family that contains a number of styles.  One of those styles is "Display", including "Display Italic", "Display Bold", etc.

However, their style name shows up only as "regular" after I convert them in TransType.  I've tried going into the Properties dialog and manually changing the style name to "Display", but when I export it goes back to being named "Regular".  Do you know why this is happening?

This is what I see when I open the Display Italic font.  Notice that the style name just says "italic".  This will conflict with other fonts in that family with the "Italic" style.

[switters]

Also, I have tried renaming the font family name manually from within TransType to "Sabon Next LT Display", but when I export the font and import it into my font manager, it gets automatically grouped with the "Sabon Next LT" family.  It seems like none of the manual changes I make in TransType are holding when I export the fonts.

[Alex Petrov (FontLab)]

I would name the Font Family manually to "Sabon Next LT Display" and OT Family Name to "Sabon Next LT".
Try the scheme as on the screenshot attached:

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics