MadCap Software Forums

Leave the images set to normal size in the source, but apply a style which sets the max-width in the medium used for the print output.

Another thought, if the server is Linux, is to ensure that the file name uses the same case as the image reference in the topic. File names are case sensitive on Linux but not in Windows, so some mismatched links that work on Windows will fail on Linux.

I have not experienced this with my help, but it may be blocking based on words embedded in the URL (from the topic filename).

Flare only evaluates page references like this for the manual it is building, so in general this is not going to work. Some ideas:
Fake it all with variables. After you build the manuals once, update the variables to the right page numbers and then build it again. Fiddly, especially if you have a ...

That happened because you are not loading the topic through the skin. Take a look at the URL for the topic you want when you load it normally. It should look something like
somesite/somepath/Default.htm#somefolder/sometopic.htm
Default.htm is, effectively, the skin. It's the shell file that displays ...

Cross references do not do this. They link to specific topics.
Something that might work is to use the topic toolbar Next Topic and Previous Topic buttons.
https://help.madcapsoftware.com/flare2019/Content/Flare/Nav-Links/Toolbars/About-Topic-Toolbars.htm
If you are using browse sequences in an ...

Possibly that time you said not to update links broke all the links to the items in question. It would have broken all links except ones between files in the moved folder. Did you try moving the folder back to its old name first?

Flare doesn't ask the question if there are no links to break.

Flare supports formatted date variables which let you specify which parts of the date you want displayed, which you could use to specify only the year is displayed.
https://help.madcapsoftware.com/flare2019/Content/Flare/Variables/Editing-Date-Time-Variables.htm
These variables can also be ...

We do have some topics that large, but we haven't experienced the problems you describe, though they can be slow to work in. In our large topics, there are either long tables of information or many equations which are embedded into the topic as MathML. It might depend on what kind of content you ...

Not for top navigation. Consider using tripane if your project is more than a simple website that you can produce with a single output.

It doesn't work because Flare substitutes resized copies of the images as the thumbnails, even if you don't use the option which makes resized copies of scaled images in general. So no amount of CSS trickery can make this work. Maybe a very sophisticated Javascript could recognize the thumbnailed ...

You create a topic containing a TOC Proxy element. You should put the heading in this topic that you want to appear above the print TOC and otherwise leave the topic blank except for the proxy.
https://help.madcapsoftware.com/flare2019/Content/Flare/Output/Printed-Output/Creating-TOC-Manually-Print ...

In the Project Organizer , open your skin.
Click the Toolbar tab in the skin editor.
Click Print in the list of Available toolbar buttons.
Click the arrow between the two panes to move it into the list of Selected toolbar buttons.
Optionally click the arrows at the bottom of the Selected pane ...

I am surprised page-break-before: avoid; on the caption element does not work. But maybe try to use a complex selector:

tr:last-of-type {
page-break-after: avoid;
}

This will apply the page break formatting to the last table row, which you can additionally specify to be tables of a certain class ...

The suggested solutions are probably not going to work with topics that have invalid XML. When you ran the import, you should have gotten warnings about any topics like this which Flare couldn't parse, and so imported without any processing. You'll either need to fix the topics so the XML is valid ...

If you have header files in your project that you don't want Flare to use with a given target, set conditions on them to exclude those files. Since header files are not XML, the conditions will be stored in a .props file alongside the header file, but this works.

If you have header files in your ...

Mediums are probably the way to go. In the Advanced tag of the target you can specify the stylesheet medium to use for that target. This works very well for PDF output; not so sure about others.
Then, in the stylesheet, you define your general styles for help in the default medium, and the ...

They claim to support it now, as long as you don't want to output to DotNet Help or FrameMaker.
http://help.madcapsoftware.com/flare201 ... ght=hebrew

You'll need to investigate the styles affecting the text that moves. Look for something with a hover selector, i.e. a:hover for setting the style of links when the mouse moves over them. If this is sufficiently different from the regular style, e.g. bold vs. regular weight, it can affect how much ...

Does the path ../../../Resources/Images/a4.png go outside the project?

Each ../ goes up one folder, so if you have topics at Content\foo\bar\baz\topic.htm then it would go up the three folder levels to Content and then down into the project's Resources folder to find the image. This should be fine ...

I've been adding bookmarks at the top of the topic and linking each TOC entry to a different one. Then you can specify a different bookmark in each CSH entry and it will sync with the unique TOC entry matching each one.

The issue with inline scripts is that they often include < and > symbols which would be taken by HTML as tags. The CDATA is a clever trick that makes the two syntaxes compatible with one another. In:
<script type="text/javascript" src="Resources/scripts/featured_resource.js">/* <![CDATA[ */
show ...

page-break-(somewhere): avoid IS effectively keep-with-next. It says "don't allow a page break to occur here if it's avoidable by moving something to another page."

When you put page-break-before, page-break-after, and page-break-inside on the same object, it means "keep this object all on one page ...

When viewing CHM help, you can right-click the topic and click Properties to open a Properties dialog box about the page, which includes the full URL for the page. You will have to click and drag to read it all since it is usually too big to fit into the small box assigned for this.

Multiple ways, depending on just what you want to do:
Create a conditional tag, apply it to the topics themselves in the content explorer, and configure your target to exclude content with this tag.
Move the files out of the Content folder. You can create other folders inside your project ...