DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › TOPLEAF: Chapter/Appendix Titles into Headers?
[email protected] July 22, 2011 at 3:23 pm
TOPLEAF: Chapter/Appendix Titles into Headers?July 22, 2011 at 3:23 pmParticipants 0Replies 1Last Activity 11 years, 8 months ago
What variable do I need to add to the odd page header for the current chapter, appendix, or front matter heading to appear before the page number?
Will I need to set up different headers for each section type or can I account for all variations in the single odd page header?
RPgjn2066 September 20, 2011 at 5:55 am
Reply to: TOPLEAF: Chapter/Appendix Titles into Headers?September 20, 2011 at 5:55 am
There are a couple of issues with your headers that need to be cleared up. Consider the following content (of your righthead header):
directive is a singleton (ie. empty tag). So while it is not exactly an error to use it to wrap content, the result will probably not be what you expect. It is normally used to invoke a font effect that doesn't coincide with the normal XML hierarchy (eg. when marking new/amended text, which may cross tag boundaries). This is not the case here and there are easier ways to achieve the desired effect.
Secondly, you can rely on the Font tab of your header to set the default font for the header. so you only need mark areas where a different font effect is needed (eg. the page number).
Thirdly, while an explicit
directive is not wrong, it is usually better to use a named space which is proportional to the current font size. So if you change the header size, the gap will scale appropriately. The “named spaces” I refer to are:
- — wide character (M) space
- — half character (N) space
-   — number width space space (useful for left padding numbers to preserve alignment)
- — thin space (about the width of a capital I)
-   — hair space (used for minute gaps, such as between text and surrounding quotation marks)
Note that while TopLeaf supports the named forms, you can also use the Unicode equivalents. For example = .
Combining all the above techniques, we can simplify the header content to:
where is just a custom marker to trigger bold font.
Of course none of this actually answers your original question! To create a variable for use in a header, [u]scan[/u] the content of a mapping and then in the Pre-content use something like:
If you use the same variable to hold (a copy of) the content of all the relevant elements, then you can set up a single header that will deal with all section types.
Note however that if the value used in the header can change within a page (eg. a subsection title) then you need to be a bit more cunning, but that's another story.
- You must be logged in to reply to this topic.