initial caps in H/F variables

Forum|Forum|12 years ago
October 1, 2013
1 reply
2529 views

I've set H/F1 to pick up the top-level heading in the chapter, which is conventionally set with one capital letter – Chapter headings look like this

Someone is now asking for the header style where I use H/F1 to be all caps. I have a particular dislike of mixed-size capital letters, and am vaguely wondering whether [in FM 10] there is a building-block <$lowerCase> or some other nifty workaround. Just a thought!

This topic has been closed for replies.

Bob_Niland

Community Expert

> ... asking for the header style where I use H/F1 to be all caps.

Can you apply, to the MasterPage H/F para instances,

a Character Format named, say, "Uppercase" that has only

Uppercase

elected?

For other hacks, you may now be able to use <$Uppercase> as a building block where Character Format BBs are allowed.

You could also apply

Uppercase in the para format for the header, but there are usually other elements that you don't want to do that to.

F

FieryPantoneAuthor

Legend

Terrible admission, but I fear I may not have explained myself clearly! I like the idea of using a character style building-block, though, and shall save it for later.

Now to try again with a better explanation …

In the body text, the chapter heading is capitalised like this: Chapter heading

If the paragraph style for the running head specifies all caps, the result is (logically and correctly) CHAPTER HEADING

Because I don't like mixed-size caps, I would like the running head to show CHAPTER HEADING, as though the body text were chapter heading with no initial cap

Bob_Niland

Community Expert

Other contributors here may have a more elegant solution, but I can think of any number of hacks, such as ...

At each Heading1 instance, create an anchored frame, at insertion point, with a text frame inside it.

In that text frame put a paragraph of format Heading1.RHF, which is an invisible text color (white-on-white works, as does using a font color set to Invisible by Color Views). Heading1.RHF could also employ a tiny point size so it won't cause wrap-around or other flow issues. Hand-duplicate the normal Heading1 text in all caps - you might as well just type it that way, rather than apply a format.

Set system variable Running H/F 1 to <$paratext[Heading1.RHF]>.

This (and other hacks I can think of) require duplicate headings.

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