MadCap Software Forums

Wow! First off, what you are doing is way too complicated!
That said, I'm focusing on the first body cell, which per your example you want top aligned but it is coming out is vertically centered and you wanted it to be Arial bold with an Arial Black bold number and it is some other font and not bold ...

Without your actual CSS I don't think anybody here can help, but the solution usually begins with viewing your output in Chrome/Firefox/IE and using the inspect feature to see what CSS is being applied to each element. This will help you determine what is being applied at what level and from what ...

Can you CTRL-click the links within the Flare editor to open those topics for editing? If not, then the links are incorrect somehow and you should re-link them to the appropriate topics.

Snippets are not callable. They don't even exist in your output. You link the CSH ID to the topic containing the snippet, possibly at a bookmark at that location in the topic.

I have a Flare project that generates a PDF of about 1200 pages. It works, though it takes about an hour for the generation to complete. This is comparable to any of the alternatives.

In each target, check the entry for Output Folder. If this is blank, it builds in a folder under your username in the output folder within the project, but if anything is specified here, Flare tries to write the output to that folder.

What you need is to set a Span Class (mc-autonumber-class) in the definition of the autonumber style. Then you can define that span class (span.xxxxx) to have white background and colored text in contrast to the text of the autonumbered heading element.

Another strategy I have used to accomplish this is to use bookmarks. Add a bookmark at the top of the repeated topic for each occurrence of it in the TOC except the "default" one, and make the extra TOC entries reference those bookmarks. When topics link to this topic, they choose the bookmark ...

You want to use the CSS property transform with the value rotate(90deg) as described here:
https://www.w3schools.com/cssref/css3_pr_transform.asp

One way you might be able to improve on this is to use a variable.
Within the link destination, you can type [%=VariableSet.VariableName%] to include the content of a variable within the link.
So if your link for the CHM file goes to ../otherproject/filename.htm
And the link for the web version goes ...

This is one of the gaps in CSS. You can write selectors which depend on what element(s) precede or contain the target element, but you cannot write selectors which depend on what follows the element or is contained within child elements.

You might be able to do it with a :last-child or :only-child ...

A good way to do this is with the content attribute of the ::before pseudo-element. So you'd have something like this:

p.note
{
font-weight: bold;
border-top-color: green;
border-top-width: 1px;
border-bottom-color: green;
border-bottom-width: 1px;
}
p.note::before
{
content: "Note - ";
color ...

Here's an example from my stylesheet, which does include changing the images:

MadCap|dropDown
{
mc-closed-image: url('image/plus.png');
mc-open-image: url('image/minus.png');
margin-top: 15px;
margin-bottom: 15px;
margin-left: 47px;
}

MadCap|dropDownBody
{
margin-left: 0px;
overflow ...

There are buttons in the TOC editor toolbar to do this, but they are pretty far out in the toolbar and so if you edit with the TOC beside a topic, you may miss them.
2018-06-11_14-43-31.png
The first creates a new book at the level of the selection, and the second creates one at the top level ...

A PDF output uses the topics linked from a TOC file in your project, and strings them together one after another to build the document. Links within those topics to topics which are missing or not included in the PDF create broken links in the PDF, but will not stop the build. So one thing you can ...

The best way to solve these problems is usually to look at the result in a browser and use the Inspect (Chrome) or Inspect element (Firefox and IE/Edge) command to open the document inspector, which will tell you which CSS commands are being applied to that element in what order to produce the ...

Create a topic with a glossary proxy element and the heading you want to introduce it, and sequence it where you want in the print TOC. Right now, what you are getting is an automatically generated version of this (see "Generate" checkboxes on the Advanced tab of your PDF target) and Flare is ...

Check and perhaps update the java installation. Flare uses Java to generate the equations for the PDFs. This fixed it for us when we had this problem some months ago.

When you open the Condition Tags dialog box on the link ( a tag), there is an Exclude Action at the bottom. If you select Unbind , then when the link is conditioned out, the text within the link remains behind, inside whatever the parent tag was, and you don't need to repeat it like you are doing.

Also, if you import HTML files (as opposed to just dropping them into the project), Flare should fix all these issues to make a proper XHTML source file. If it doesn't, report a bug.

This was a known bug in the 2017 versions, fixed in 2018.

Press F12 (in the browser), and use the 'inspect' option to select the item and look at its CSS. That'll tell you straight away which CSS rules and properties are being applied.
Sorry, I meant to mention that the output is a PDF rather than a web page or help, this project only has PDF output ...

Apply the condition to the <i> tag, but in the Condition Tags dialog box, for the Exclude Action at the bottom, click Unbind. This will remove the <i> tag while preserving its contents within the next parent tag.

In the instructions in the article you linked, it mentions to create a page layout break on the TOC entry for your title page to reference the new, title-page-only page layout, but it never says to do anything to go back to your regular page layout. So what I think is happening is that you are ...

This has been a major limitation of Analyzer, that it only considers the whole project and not the output that would result from applying the conditions in a specific target. Conditions can cause problems that don't show up in Analyzer output, such as:
Otherwise valid links to be broken because the ...