MadCap Software Forums

Hi Adriana

You are right, the alias file does populate the text-based header file. There should be no need to go in and change the header file at all. That file is meant to be sourced from the developers (if they define the IDs), or sent by you to the developers if you are defining the IDs. If you ...

The note may be set up as a paragraph style with an autonumber generating the word Note, and perhaps a background image. In this case you can easily insert it using Ctrl + Shift + H to bring up the style picker and then start typing the style name to insert it (e.g. "p.note").

If they are a bit ...

No problems here with that setting and Flare 2017, maybe raise a support ticket if you're worried about specific behaviour between Flare 11 and Flare 12?

When I try your code in the San Diego template, Top Nav output it works flawlessly in all browsers, with none of the problems you mention. The only exception is in when shrinking the browser so the mobile responsive layout shows, and then nothing appears at all.

Perhaps something else is ...

I don't think it's possible to change this behaviour out of the box. However being XML-based Flare is well set up for working with programmatically. You could, for example, create a post-clean-up script or command-line program that reads in the imported page layout, and converts found text in there ...

Sounds like an IIS issue. Does it work if you have the help system under a subfolder (e.g. wwwroot/help), and access via localhost/help? You shouldn't need to call default.htm directly if Default Document is set up in IIS.

I don't think a shared footer is possible within Flare, not easily anyway. One approach would be at the level above Flare, for example, have a landing page that serves up the help in the top area and the shared footer at the bottom.

As an alternative, you may be able to get close to the look you ...

Some things I've found that Word output doesn't support:

Multiple columns
Background images (in page layouts - I haven't found a way to replicate out title page with full image yet), and background images in CSS (for example, if doing note/tip images)
float left/float right on styles (e.g. page ...

You are right, the code in MadCapAll.js that constructs the document title is not hit at all for top nav, the title within each page is the one that ends up on the browser tab. That means you should be able to add some script to your master page to construct the document title however you want.

As ...

It looks like (for HTML5 output, no sure about others) the search URL is #search followed by a dash and then the search query. So I imagine it would't be too hard to have a box in the software that captures the input (e.g. "my search query") then crafts a link like:
https://myserver/help/search-my ...

Another option is to reference the prism CSS from your master CSS. Open your master stylesheet in a text editor, and put this at the top:
@import url("prism.css");
Also I'm not sure if it's a requirement, but our project is using a single directory for both the prism javascript and CSS file ...

You may want to look into a tool such as "FAR - Find And Replace"

You'll want to do something like this (using regular expressions) - you could add the class at the end of the find to remove that as well, however I would have thought leaving it there wouldn't hurt and might be useful down the track.
Find:
(<img src=".*) style=".*"

Replace with:
\1

The usual ...

Maybe try putting your Robocopy command in an external script and calling that script via the Flare target post-build event - and pass the output directory as a parameter.

Your target's post build event would be something like:
"$(ProjectDirectory)post_publish_script.cmd" "$(OutputDirectory)"
And ...

Absolutely! Flare has command line build capabilities (madbuild) which can work with any CI tool your company is using (TeamCity, Jenkins etc). Flare 2017 also has pre and post build events which you can use to call external batch and powershell scripts. Those features, along with Source Control ...

Does overrides.css appear in your output? If not then maybe "Exclude content not linked.." is enabled in the target - clear that and try again? Also try clearing the cache (with F12 developer tools showing right click the refresh button and select Empty Cache and Hard Reload). Otherwise not too many ...

Put this code in the Skin | Toolbar | Custom Javascript... section
$("head").append("<link rel=\"stylesheet\" type=\"text/css\" href=\"Resources/Stylesheets/overrides.css\">");


Add a new stylesheet to the Content | Stylesheets folder called "overrides.css".

Use that file to further customise ...

Flare does work with Source Control (SVN, Git etc), however there are no branching, merging or tagging options from within the Flare GUI. So you could treat documentation source files as code, but if you need to branch for sprints then merge back at the end, you'll need to use third-party tools like ...

Interestingly it appears Flare only uses the lower case form of stop words in HTML5, entering "With" or "WITH" etc will still search for those terms.

As a slightly out there idea you could write a script that forces text entered into the search box to be upper case. Or takes the text on submit ...

For our 'a' styles we ended up using an !important on the color to override the Flare miniTOC styles, this may be one approach you could use?

Flare's strengths are not as a document repository - it is more for authoring and content management. Therefore I don't think Flare will help much here - this sounds like more of a content strategy/process issue. You could import the word docs into one or more Flare projects, and use Flare's various ...

If you're talking about the TOC icons in HTML5 output and the 'Styles' accordion in the skin, there are two places to define them:
Navigation | Navigation Panel | TOC | Icons (use this to define your icons)
Navigation | TOC Entry | Icons (set these to "(default)" - whatever is defined above will ...

Were you adding the <link rel... tag to the masterpage or individual topics? I can understand topics stripping out the code, but I would hope the masterpage would copy the code across as is.

The other thing to try would be adding some JavaScript to the HTML5 skin (under the Toolbar accordion ...

Duplicate each topic in the TOC, with a two-column page layout, and a column break before each heading?

CHM help uses an older version of IE to render it's output (I think IE7). My guess is the older version doesn't support complex selectors in that way, or perhaps modern browsers add additional indents in their inbuilt stylesheet that CHM help doesn't.

Try using IE's F12 Developer Tools to set the ...