Word output puts just one line of text per page

[daicehawk]

WordOutput.jpg

I am starting getting mad, not because Word output when I have applied a page layout with custom header and body frames just put 1 line of text per page (see the attached picture) but because I wanted to attach the layout file and discovered that FLPGL files are not allowed - at the official product support forum? Come on, how crazy this is?
The page size is A4, the body frame is 180x257 mm (WxH) so it is not a size issue. What can it be?
Having worked with Flare a couple of years I can say that it is very extensive solution with a multitude of features but they interfer with each other in an upredictable way sometimes.

[nickatwork]

Are your heading levels set to start on new pages?

What text is starting on the next page? Is it another paragraph, another heading, another topic? My guess is that there is a page break going on in there somewhere. Does the same happen with PDF output?

[RamonS]

This is a peer to peer support forum, but I will ask if there is a way to have flare specific files be allowed. If you direly need someone to take a look at it contact support.
As far as the custom body, is it large enough to accommodate more than one line of text?

[LTinker68]

Also, check the margin-bottom or padding-bottom attributes for your paragraphs and such in the print medium, or whichever medium you're using for the print outputs. You may have inadvertently set the value of one of those attributes to a really large amount (e.g., 5 in. instead of .5 in.).

[rob hollinger]

testing for pagelayouts.
Also added css and masterpages as attachments.

[daicehawk]

Thank you, this attachment feature is great!
Actually I have just made a new layout which works however I have not found out what is the reason of such behaviour.
Still if this works OK with a different layout means that the paragraph style is OK and something wrong with the particular layout.

Another question is I can not prevent pages from breaking before images for Word output. I set "avoid" for page-break-before for <p.Picture_center> and <img> used for illustartions aligning, "avoid" for page-break-inside for <li>, still in the output it looks like this:

Code: Select all

<ol>
            <li>
                <p MadCap:conditions="Default.Server">Do this by pressing the X button <img src="Resources/Images/StartMenuButton.png" />.</p>
                <p class="Picture_center" MadCap:conditions="Default.Server">
                    <img src="Resources/Images/ControlPanel.png">
                    </img>
                </p>
            </li>

[LTinker68]

A couple of things...

Still if this works OK with a different layout means that the paragraph style is OK and something wrong with the particular layout.

Not necessarily. As I mentioned above, it could also be tied into styles, if you're using a different medium in the stylesheet for one output than you are for another output. Those two outputs could also have two different page layouts. So 1) how many stylesheets do you have, and 2) how many mediums do you have in those stylesheets (and what are the medium names)?

Another question is I can not prevent pages from breaking before images for Word output. I set "avoid" for page-break-before for <p.Picture_center> and <img> used for illustartions aligning, "avoid" for page-break-inside for <li>, still in the output it looks like this...

Flare will try to honor your breaks, but 1) if the content can't fit on the page then it'll break somewhere in the content, 2) although it may look like you have plenty of space on the page, if your paragraph, image, or li tags have a lot of margin or padding in them, then the space reserved for that margin and padding is included in the calculations for where to break the content. So if a paragraph has a top margin of 8pt, for example, then those 8pts are included with the actual content of the paragraph when Flare determines where to place the break (the paragraph tag itself has a "box" that includes margin, border, padding, and content). You might need to create custom classes, or even add inline styles (normally not recommended), to lessen the margin and padding on those particular elements on that particular page so that everything will fit together.

[daicehawk]

No I checked margin and padding values for <li>, <ul>, <ol>, <p> - they are either 0 or not set.

[LTinker68]

Try this, although it's a pain in the ass, but it'll narrow down the problem. First, make a copy of the stylesheet file as your backup. Then open the original stylesheet file in the Internal Text Editor and delete all page-breaks attribute lines from every style. Save the stylesheet, rebuild, and see if that takes care of the problem. If it does, then two or more of the page-break attributes you had set were probably in conflict. Start adding page-breaks back, one at a time (that is, add a page-break, save the stylesheet, rebuild, see if the output is still ok), until you get the content laid out the way you want. Don't add more than you have to.

[daicehawk]

Try this, although it's a pain in the ass, but it'll narrow down the problem. First, make a copy of the stylesheet file as your backup. Then open the original stylesheet file in the Internal Text Editor and delete all page-breaks attribute lines from every style. Save the stylesheet, rebuild, and see if that takes care of the problem. If it does, then two or more of the page-break attributes you had set were probably in conflict. Start adding page-breaks back, one at a time (that is, add a page-break, save the stylesheet, rebuild, see if the output is still ok), until you get the content laid out the way you want. Don't add more than you have to.

Yes, that has sense, thank you.