MadCap Software Forums

The h file is pretty basic, with #define, space, text identifier, space then numeric/hex value. I imagine Flare only knows this format when adding an existing file, so you'll need to manipulate the .js file (perhaps using regex in a text editor like Notepad++) to the proper header format before addi...

Have a look at this post:
https://stackoverflow.com/questions/263 ... -file-urls

In addition to <td> becoming <th>, the row <tr> also needs to appear in a separate <thead> (hopefully that makes sense!) Something like: <thead> <tr> <th>Heading</th> <th>Heading</th> <th>Heading</th> </tr> </thead> <tbody> <tr> <td>Body</td> <td>Body</td> <td>Body</td> </tr>... Unfortunately the on...

I don't believe Flare has any feature like this. Are you using source control? If so then you could do a report of all commits since a certain date/revision, focusing on *.htm files changed or added. Note that Flare can make a change to the XML under the hood so a commit may not be an actual content...

They have a reasonable point, Git is not made for storing binaries. From what I understand each time a change is made to an image then it is pretty much duplicated in the repository rather than just the differences as with text-based files. In saying that the images are an important part of the soft...

Nice solution. An alternative to search on replace via SSH on the server is to run a post build command in Flare that calls a Powershell script that does the search and replace. This means it will happen automatically on build, and is available to check locally before upload.

Are you looking at Layout(Print Layout) in the XML editor? This should show how it will look in the PDF and may make it look better. If there is a big discrepancy between how that looks and the final PDF, then I think you have a CSS problem (perhaps using complex selectors or other fancy CSS tricker...

If you want rich text in glossary items (including links) and other fancy things like images, then you can use a topic as the glossary definition and then link to it in your glossary file. The end result is not much different - they still appear as popups when clicked. From memory they appear as a l...

If you use H1 to H6 in the topic, and are happy to use that for the topic title, then use Search and Replace / Find in source code / Regular Expressions to remove all topics titles for your project.

Flare will then use the heading in the topic to auto-populate the title in the generated help.

Note the above removes the width, if you want to put a different width in there, replace becomes something like:

If the above doesn't work, the following wildcard search should do it:
Search: Replace: Make sure you backup your files before replacing all.

It may be best to look at a plugin within the Flare editor that saves/copies/synchronizes the XHTML from a topic to your SQL database and/or back again? Or some kind of integration between source control supported in Flare like GIT or SVN and the database. That way the Flare output is separate and c...

You are right about needing the initial quotes, sorry about that. I am guessing one or more PHP files has a reserved character in the filepath. Try using -literalPath param( [string]$filePath ) $filePath $phpFiles = (Get-ChildItem $filePath -Filter *.php) for ($i=0; $i -lt $phpFiles.Count; $i++) { (...

Probably easiest using Powershell. This is similar to the approach we use and should loop through PHP files searching and replacing the text you want. post_publish_script.cmd and post_publish_script.ps1 are in the high level directory next to your project file. Build Command in Flare: $(ProjectDirec...

The easiest solution is a search box in the app that captures the text input and sends it to the help system's search page in a new tab. Perhaps by default the search box searches the site, and there is an adjacent checkbox that says "Search Help" or similar. This won't be integrated with ...

Pass the output directory to your script in the build event in Flare, e.g. "post_publish_script.bat" "$(OutputDirectory)" Then use %1 in your .bat file to grab the name of the file, e.g if it's a PDF: for %%F in ("%1\*.pdf") do ( set "NAME=%%~nF" ) echo %name%...

I assume you're using a topic toolbar in HTML help? Go to the skin (e.g. Default.flskn). Using the 'Styles' accordion, navigate to Toolbar Item . Find the entries for Expand All and Collapse All . Set the three ...Icon properties to None. Enter the text you want in Label . Save and rebuild.

I just replied to another similar post. You should be able to control you TOC styles using
td.GenTOCText1
td.GenTOCText2
td.GenTOCText3

I believe you are looking for the class td.GenTOCText3

However applying your styles to that may push your page numbers to the next line. I think you are better off with something like this:

Add an Alias and header file in Flare (Project Advanced). Add a new identifier to the Alias file. Give it the Identifier you currently use, e.g. MySettingsEditPreferences, let Flare assign the Value, and assign the topic you want to link it to. The developer then uses JavaScript or a URL to open the...

Great question - I guess it depends on what the UI designer is tasked with. If it just the styles within topics then you can probably hand over the stylesheet and have them work with that. They won't be familiar with the propriety MadCap styles though (e.g. xrefs, miniTOC, breadcrumbs, popups, auton...

I was wondering if anyone know how the queue is ordered when you use a batch target? I suspect it is the order within the file itself (which may not reflect the UI). Try right clicking the batch target | Open With | Internal text editor. Then cut and paste the entire <target ... > tag to the end. (...

Cross references are in your stylesheet under MadCap|xref or MadCap|xref.[name] My guess is either you have padding or margins set in there - or you have padding or margin set on another style that is not cascading down to the xref style. Either way, tweaking the xref style should fix it: MadCap|xre...

Not when viewing topics in the output via search or navigation, the URL will reference the topic name plus some other things (e.g. TOC identifier or search highlight info).

The ID is used (and can become part of the URL) when calling a topic. E.g.
http://yourserver/Help/Default_CSH.htm#6414

Unfortunately that's how xrefs work, if they include {paratext} then it will have the entire heading (or paragraph) text. You have a few options, but this will require fixing in Word pre-import or in Flare afterwards (search and replace may help) Use hyperlinks - where you can define the text as you...