I'm using cross references to insert sections of text that are repeated in two chapters. The referenced text includes bold text that is defined in a Character Tag. The chapter where I'm inserting a reference to the text has the exact same Character Tag in its Character Catalog (I imported the character formats to be sure). But the bolding goes away in the cross-referenced text. Any ideas on how to make the bolding show up?
Neither Character Formats nor text attributes caused by Variables seem to be preserved on Xref.
What would work, however, is to put the text in an external .fm file and bring it in as an inset.
Ok, thanks 7103. Certain aspects of character formats are preserved. For example, the cross-referenced text includes custom font characters that are defined in a Character Tag, and those work fine. But not the bold text, which is also defined in a Character Tag. Strange.
I thought about using an inset, but that would be awkward, to have a separate document just for a few items that are repeated in the middle of a couple lists.
> For example, the cross-referenced text includes custom font characters that are defined in a Character Tag, and those work fine. But not the bold text, which is also defined in a Character Tag. Strange.
Strange indeed. The font name change is preserved in Xref if it's done as a Character Format, but not as a local override in the source text.
So this suggests yet another hack. If you do the bold as a separately named font, say Palatino Black, and invoked via Character Format, it might come across.
and stranger ...
I defined a Ch Fmt that had Angle, Weight, Variation, Color, Underline, Overline, Strike, Change, Super, and Small Caps elected.
The Xref appears to have honored only the Superscript and the Small Caps .
Somebody thought long and hard before architecting this ...
... and then neglected to document it.
Nice! Sounds like a feature request is in order. Thanks for looking into that.
I want to try using the bold version of my Frutiger font in the Character Tag, but it doesn't show up in the font menu in FM. Only the regular, light, and ultrablack versions show (ultrablack is scary looking, so I won't use that). I'll poke around and see if I can get it to show.
The Bold font will have to differ by name in the Font Family pulldown, not just in the Weight pulldown.
I'd make a copy of (just guessing) "frut_b.ttf" as "fruti_b.ttf"
Get a font renaming app.
Rename the font internal name from "Frutiger Bold" to "Fruti Bold".
Just renaming the font filename won't work. You need to alter the internal structure.
When I install the .ttf versions of Frutiger, Frutiger 65 Bold is available in Frame, as are all the other variations that aren't available when the .pfm versions are installed. So this solves my original problem, although now I'll need to update all my docs to use 65 Bold instead of bolded 45, because now I can't apply bolding to Frutiger 45. I guess it wants me to use 65 Bold. Oh well.
> The Xref appears to have honored only the Superscript and the Small Caps ...
I did another test, and the following are honored in Cross-References:
Small Caps, Lowercase, Uppercase
This works between files, in which case the local file can have different definition for the Character Format named.
It wasn't clear if these were honored: Pair Kern, Language
No other Character Format options were honored.
No source Paragraph Designer attributes were honored.
No local overrides were honored (well, actually, I saw a font come in on insertion, but it vanished on Update).
The above was using a simple <$paratext> Xref format. If your Xref format includes a Character Format that conflicts with the Character Format at the source, the source prevails.
If the Xref format was, say, <Symbol><$paratext>, the format's Symbol font changed all the incoming text that used a default font, but did NOT override a Character Format:Family [Albertus] at the source. Interesting.
Europe, Middle East and Africa