Skip to main content
Jason_Nichols2
Known Participant
January 27, 2016
Answered

Framemaker 2015 issue with losing italics in legacy files

  • January 27, 2016
  • 16 replies
  • 2163 views

Our team just upgraded to FrameMaker 2015 (from FrameMaker 12). We're running into some issues where we lose italic formatting in existing files and templates, and/or the "Emphasis" character tag that we use to apply italic formatting does not work correctly.

For example, when I open our existing template in FrameMaker 2015, the "Emphasis" character tag is still defined correctly – it shows the "Italic" property in the "Angle" field. But, when I select a word or phrase and apply the "Emphasis" style, the text does not get italicized. Frame shows that the "Emphasis" tag has been applied, but the text is still roman (i.e., not italicized).

When I change the "Angle" property from "Italic" to "Kursiv" that seems to resolve the issue, but I'm not sure why.

We are also seeing inconsistent issues of italic formatting getting dropped altogether in existing files, or getting dropped just from cross-references, etc.

Are there any known issues with italic formatting in FrameMaker 2015? Or anything we might be doing that triggers this?

FYI: We are all on Windows 7.

Thanks in advance...

This topic has been closed for replies.
Correct answer Arnis Gubins

Hi Arnis,


I appreciate all your patient replies with this . . . This has gotten me closer to a solution, I think, but I'm still not quite there...

First, real quick, there was only a single instance of "kursiv" in either maker.ini file – it was in the "Angles" definition, which was identical for me to what you and Mike listed (including the order).

This got me thinking though . . . I next tried removing a plug-in that we purchased for a prior version and then restarting Frame and creating a new blank document. (This plug-in loads at startup and uses an FM file that contains content from our templates.) I thought this did the trick. The default "Emphasis" character tag was now showing "Italic" by default instead of "Kursiv." And everything appeared to be working as it should – when I applied the "Emphasis" character tag, the text actually did get italicized (even when I changed the font to Akzidenz-Grotesk Pro).

But then as soon as I opened existing files based on our templates, the italic issue was still there, as before.

What's more, opening a legacy file seemed to change Frame's behavior for that session. That is, after opening the legacy file, I tabbed back over to the new, blank document I had started with. Now, when I checked the Emphasis tag, it was showing "Kursiv" as the angle instead of "Italic," as it had before.

When I shut down Frame, then reopened it and started another new, blank document, the "Emphasis" tag and italic functionality continued to work properly until I opened a legacy document. Then it didn't work properly in any file.

This makes me think the issue is with our templates somehow. I tried another MIF wash on the templates, but the issue persists. So strange...

Thanks,

Jason Nichols


Have you checked what's in your templates? It could be that the plug-in (or perhaps another start-up initial script or a different plug-in) is loading something that leads to this behaviour. It sort of sounds like the template catalogs are getting (re-)imported at start-up to ensure a uniform behaviour in your workgroup.

16 replies

Participating Frequently
January 28, 2016

This might be a difference in the font configuration within the maker.ini file. This is found within the FrameMaker application. There is also a user-specific copy that can override the main settings. See the top of the main maker.ini file for details.

I'd investigate the following.

The Angles setting defines the vocabulary that is used for italicized fonts. This is the default for FM12:

;

; Definition of the font vocabulary:

;  Angles, Variations: a list of the words.

;  Weight: the list of words and the associated weight for Windows, if any.

;

Angles=Regular, Kursiv, Slanted, Oblique, Italic, Obliqued

Look for differences between FrameMaker 12 and 2015. Don't forget to check for overrides in your personal maker.ini files.

Also, search for Akzidenz-Grotesk in the files. Are there any settings in one file that are not in the other? Likewise for Kursiv.

Finally, the following might provide a workaround:

  1. Quit FrameMaker 2015.
  2. Open your personal FrameMaker 2015 maker.ini file in a text editor.
    This file is typically in \Users\<username>\AppData\Roaming\Adobe\FrameMaker\<version>.
  3. Add the following two lines:
    [WindowsToFrameFontAliases]
    AkzidenzGrotesque Pro, Italic, *=AkzidenzGrotesque Pro, Kursiv, *, Regular
    (I'm assuming there isn't already a WindowsToFrameFontAliases section)
  4. Save the maker.ini file
  5. Restart FrameMaker 2015.

If necessary try this again, changing the first occurence of AkzidenzGrotesque Pro to any variation you can find displayed in Windows, or within the font file itself (e.g.  AkzidenzGrotesque-Pro or AkzidenzGrotesquePro).

If this works, consider adding the setting to the main maker.ini file so it applies to all users.

Arnis Gubins
Inspiring
January 28, 2016

@Mike,

The maker.ini changes would be global, but the italic function worked properly in a new file for Jason, so it's a bit of an oddity why it happened in the upgraded documents only.

Jason_Nichols2
Known Participant
January 28, 2016

@Mike, @Arnis,

Thank you both (and apologies for the slow reply). I didn't find anything unusual in the maker.ini file, and adding the "[WindowsToFrameFontAliases]" lines to my personal maker.ini file didn't have any effect. (I should mention that we do make a couple font-related changes in the main maker.ini file, but when I reverted to the original maker.ini file the same issues were still occurring in the same way.)

Also, alas, I tried a MIF wash on one file, but that seemed to have no effect either. I'm stumped – I kinda thought that would fix it...

For what it's worth, several writers have run into some form of this issue now with our existing files, and we're seeing it in documents based on two separate templates. Also, I can start a new blank document in FrameMaker 2015, and this issue does not occur. But if I import everything from one of those existing templates, the italic issues do crop up. Not sure if that helps at all...

Anyway, appreciate your help, thanks again. If you think of anything else that would be good to try, I'm open to all suggestions   . . . And if we figure it out in the meantime, I'll be sure to post an update here...

Arnis Gubins
Inspiring
January 27, 2016

The usage of Italic vs. Kursiv all depends upon the actual typeface that you are using. What fonts are you using in the documents where this happens?

Jason_Nichols2
Known Participant
January 27, 2016

Ah, ok, thanks. We are restricted to using a single font family: Akzidenz-Grotesk Pro

All 28 fonts in the family are Open Type (.otf).

We have always used the "Italic" property in the past with Frame 10–12 – it's not until installing Frame 13 that we ran into this issue...

Thanks again!

Arnis Gubins
Inspiring
January 27, 2016

The Akzindez-Grotesk Pro family does have the Italic version according to the Berthold descriptions, so the font family shouldn't be the issue in this case.

Have you tried a brand new document in FM2015 to see if FM shows an Italic version of this font and another standard font (such as Arial) in the Angle dropdown list of the Designers? If Arial shows Italic and the Akzidenz shows Kursiv, then I would wonder if the internal setting in the Akzindenz font is suspect [i.e. have these been modified with a font editor?].