Participating Frequently

Question

Indesign not recognizing font by same name as other programs

Forum|Forum|3 years ago
March 25, 2022
3 replies
3342 views

Hi there,

I am currently running MacOS Mojave 10.14.6, with InDesign cs6.

Our company is beginning to transition from QuarkXpress 2017 to IDcs6, so we purchased the plug-in program Markzware to convert all of our .qxp files into .idml files. Everything is running smoothly for the most part, but indesign is having trouble recognizing our body copy font as the same in quark and indesign. After converting the file, I open the IDML in indesign and the typical missing font error pops up, only the font is not technically missing. On quark, the font is just called 'Stone Serif' but when looking at it through indesign, it's called "ITC stone serif." On my system, however, the font family is just called 'Stone' and each of the different font styles are listed as 'StoneSer ....'

I found an article which states "the font you are looking for, uses a different internal font name than do QuarkXPress and/or InDesign, and the same font, under a slightly different name, will be available, referring to the exact same font" which is exactly the issue I'm having, but the article provides no solution on how to tell InDesign that the font it's reading is the same one as what it says is missing.

I know that it's not a huge workaround to just use the "Find Fonts.." panel in Indesign and update all of our body text, but we are looking to convert hundreds of files from quark to indesign, so I'd like to see if theres a solution/a way that I can tell indesign to read the font in the same way it does for Quark, so that when I open the new .idml pages in Indesign, I don't have to update the font and style sheets every time I open a new document.

It should be noted as well that it is only creating this issue for two of our fonts, Stone Serif and Matrix. It does not say the fonts are missing for other text we use on the page.

Hopefully the screenshots below help illustrate this issue a bit better. I will also link articles I've already looked at so it's known what I've already tried to fix the issue.

https://www.qppstudio.net/webhelp_xv4/fonts-installed-available-to-quarkxpress-and-indesign.htm

- this page technically is referring to their software, but it is where I saw the information about quark and indesign reading separate file names.

https://helpx.adobe.com/indesign/kb/error-fonts-currently-available-incopy.html

- tried everything from this thread to no avail.

https://design.tutsplus.com/tutorials/quick-tip-troubleshooting-font-problems-in-adobe-indesign--cms-24652

- tried everything here as well, and what's even weirder, is under the Library/Application Support/Adobe/ folder, I don't have a fonts folder, only the FontsRecommended and FontsRequired folders.

This topic has been closed for replies.

Brad @ Roaring Mouse

Community Expert

A bit of history is in order here in regards to the Stone family of fonts which might explain things a bit.

But before that, you are going to a lot of trouble for nothing to do this now because, come January 2023, your existing Type 1 fonts (which is what your Stone fonts are) will no longer be usable, so this whole undertaking will only be good as long as you never need to open these CS6 converted files in anything Adobe releases after January.

Soooo, back to Stone.

When Stone first came out, in the late 80s, it was packaged as all Mac Type 1 fonts were, with a Font Suitcase and the Outline fonts. Within the Font Suitcase, were the Screen Fonts, which contained the spacing information/font metrics. like so...:

So here's where the naming is confusing. Quark (and other programs back then) used the names of the actual Screen Fonts in their menus (the files on the right of my screengrab), which did not include the initial ITC moniker.. that was only on the name of the enclosing Font Suitcase.

Fast forward to now, and modern font managers don't need the Type 1 screen fonts separately anymore... they read the data from them and then store it internally, but now list everything according to the "Family Name" (which in this case is the name of the Font Suitcase.. i.e. "ITC Stone Informal", etc. hence the different naming.

Since this naming is different than what's in your Quark file, even though they refer to the EXACT SAME Type 1 Outline font, it will show up "missing" until you replace it manually.

So, what to do: As I said, it's literally a waste of time to do this now. If you are serious about this, you need to invest in the OpenType versions of Stone (unfortunately, and weirdly, Adobe does not offer them in their Cloud fonts.. you have to BUY them from a reseller like fonts.com. Be warned: it won't be cheap)... and they have been renamed to "ITC Stone Informal Std...", etc etc, but they are a direct replacement for the Type 1 versions.

A

alywitmerAuthor

Participating Frequently

I created a video illustrating what the issue is at hand a bit better than my typed description:

https://youtu.be/a29GiOtKyHk

jane-e

Community Expert

@alywitmer wrote:
Our company is beginning to transition from QuarkXpress (sic) 2017 to IDcs6

InDesign CS6 (released in 2012) is no longer available for purchase from Adobe. Any copies you find today are likely to be pirated and contain malware. Current plans for legal versions are available through Adobe from this site — click the appropriate tab.

https://www.adobe.com/creativecloud/plans.html

Jane

A

alywitmerAuthor

Participating Frequently

Hi Jane,

Thanks for your response, however, these are not new downloads of cs6, our office macs are from 2012 and have had Adobe CS6 on them for years. We are only transitioning now to allow more cross-compatibility with the elements we create in photoshop and illustrator. These computers are not capable of running creative cloud as they're still running Mojave 10.14.6.

A

alywitmerAuthor

Participating Frequently

Just as heads up - worth thinking about future plans. (1) New Macs won't be able to run Mojave (2) Later systems won't be able to run CS6 (3) One day Macs need replacing. I realise this may be well outside the problems it's up to you to solve, but it's worth knowing.

Thanks for your response. I don't forsee the company replacing all of the computers any time soon until it becomes absolutely vital or apple stops supporting them. In terms of upgrading from cs6 to CC, it's less of a worry because all of the files are being converted to .idml so we will still be able to open them in CC.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded