We have recently switched from version 5 to version 7. This worked in version 5.
In the styles sheet, I changed the h5 to add a page break before the paragraph and keep it the way it was "styled" before it was set to h5. I use it to have a page break before the paragraph (initially style = p -- changed to h5) prior to an image. It looks okay on the screen when editing in Flare. It looks okay in the final output; however, it changes to all bold when I do an abbreviated version of the output. Is there a reference to styles that isn't being picked up by the subset of the Word document?
Text text ....
(image)
Originally the text would be a p paragraph.
When reviewing, I see that it breaks between the text and the image.
I change the text paragraph to an h5.
In full Word output -- it behaves as desired.
In small test set of files -- it turns to all bold.
not bold vs bold -- output different in shorter test version
Re: not bold vs bold -- output different in shorter test version
Those small test sets of files... Did you create a new target for those test sets, and if so, is it pointing to the correct stylesheet and/or medium in that stylesheet (most likely the print medium)?
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
Re: not bold vs bold -- output different in shorter test version
Yes, I have a target -- test
The Advanced -> Stylesheet Medium -> Medium is set to "print."
The Advanced -> Stylesheet Medium -> Medium is set to "print."
Re: not bold vs bold -- output different in shorter test version
When you say you switch it from a paragraph to an h5... Is the h5 styled the same as the paragraph, because by default heading styles are defined as being bold? If you had a paragraph class on the paragraph to set it not to be bold and switch to an h5 tag, then the class wouldn't affect the h5 tag unless the class was a generic class. In other words, if you have a style called p.notBoldText then the class will be ignored if you switch from <p class="notBoldText"... to <h5 class="notBoldText"... because the class "notBoldText" is specifically associated with a tag of type paragraph. If you had created it as a generic class (.notBoldText instead of p.notBoldText), then <h5 class="notBoldText"... would apply the class to the h5 tag just as it would to a paragraph tag.
Does that make sense?
Does that make sense?
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
-
wclass
- Propellus Maximus
- Posts: 1238
- Joined: Mon Feb 27, 2006 5:56 am
- Location: Melbourne, Australia
Re: not bold vs bold -- output different in shorter test version
In your test target do you have "Use TOC depth for headings" set (Advanced tab)? This could be affecting the heading level, and hence, changing the look.
Margaret Hassall - Melbourne
Re: not bold vs bold -- output different in shorter test version
My settings are:
Font
font - Arial
font-family - Arial
font-size - 12pat
font-weight - normal
Block
display - block
Box
margin - 0
margin-botton - 0
margin-left - 0
margin-right - 0
margin-top - 0
Print Support
column-break-after - avoid
mc-heading-level - 0
page-break-after - avoid
page-break-before - always
page-break-inside - avoid
AutoNumber
mc-auto-number-offset - 0
mc-auto-number-position - inside-head
DITA
mc-dita-type - p
Unclassified
mc-disable-glossary-terms - true
Every other setting is "(not set)"
It looks like I should probably change:
mc-disable-glossary-terms to "not set"
This is a reminder --- this WORKS with the final output. It does not work with a subset.
Font
font - Arial
font-family - Arial
font-size - 12pat
font-weight - normal
Block
display - block
Box
margin - 0
margin-botton - 0
margin-left - 0
margin-right - 0
margin-top - 0
Print Support
column-break-after - avoid
mc-heading-level - 0
page-break-after - avoid
page-break-before - always
page-break-inside - avoid
AutoNumber
mc-auto-number-offset - 0
mc-auto-number-position - inside-head
DITA
mc-dita-type - p
Unclassified
mc-disable-glossary-terms - true
Every other setting is "(not set)"
It looks like I should probably change:
mc-disable-glossary-terms to "not set"
This is a reminder --- this WORKS with the final output. It does not work with a subset.