italics, variables and cross-references

Question

"Oh Niels, we've decided to use italics for the second word in the product name!"

No problem, I thought, and adapted the variable definition to include a character-style switch:

<Default ¶ Font>Name <!italic>touch<Default ¶ Font>

No problem indeed, except for cross-references :-{ The ToC shows Name touch where I've used the variable in headings, the headings show Name touch in the correct font … but cross-references show Name touch. OK, in this very particular case I could be result-driven and replace Name touch in the cross-references with Name touch. It would be good to know, though, whether there's some finesse I'm missing – always possible, always educational.

The cross-reference format, by the way, is simply

<$paranum> <$paratext>

Thanks in advance for any help on this! if you need more information from me, just ask.

Arnis Gubins · Answer

Niels,FM only extracts font family, subscript and superscript properties when referencing paratext either in a cross-ref or a running h/f variable. For this to work, the font name must contain the Italic as part of the name. Since it's not working for the font that you are using, you have to trick FM to think that there is a unique font in the family being used. This is accomplished by adding a definition to the maker.ini [WindowsToFrameFontAliases] section.Add a line using your specific font name as follows (I've used a made up name):CuneiformClay, Italic, Regular = CuneiformClay Italic, Regular, Regular, RegularWhen you next run FM, you will see that the Character or Paragraph Designers do not list an Italic version for the Angle attribute of the . You will need to explicitly select the " Italic" using the Family atttribute instead to get italics. Modify your "!italic" character tag accordingly.[This trick courtesy of Shlomo Perets - he had a source at http://www.microtype.com/resources/FTPreserveFmtXref.pdf but I can't sem to locate it now?]

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