MadCap Software Forums

The relevant section in the CSS is Madcap|XREF. Properties in there will override anything under "A". If you want us to try and troubleshoot further, you'll need to post sample xref source code from your generated webhelp, and also the xref code from your stylesheet.

Another couple of comments ...

That would be a nice feature. Be sure to log an enhancement request with Madcap. The only thing that comes close is the glossary option to convert the first term in every topic. I guess you could provide copyright text in that glossary popup (converted to footnote text for printed), but it's not ...

I have no idea why it would be doing that. Is the Topic column too narrow (hiding the proper topic name?) Maybe try resizing. Or perhaps it is a glitch on the UI - is it the same when you open the file in a text editor?

There is no elegant solution I can think of. I guess you could always add text like "|NEW" to the end of each heading, then open the imported TOC in a text editor, and search and replace
|NEW"
with
" MarkAsNew="true"

Cheers
Greg

When you say "4. Deleted the Output file", what file did you delete? When you build HTML help, Flare will generate the HHP project in output\username\Temporary\HTMLtargetname\Content
So it could be that Flare (because of windows) cannot clear out that directory before the build. Maybe a windows ...

I think any code you place in the head of a topic (after opening in the text editor) is wiped after you build, and replaced with code from the masterpage. So I think you'd need to create a special master page and apply that to your topic.

Mine also has "visibility: hidden;", but the toolbar does show (after a very brief delay). I assume that the hidden flag is an initial setting, and the toolbar then becomes enabled via Javascript. Can you try it on a topic that does not have any fixed non-scrolling parts? There may well be a clash ...

In your Program Files, see the file " Flare.app\Resources\Xml\LanguageCodes.xml", which includes references to the directory " Flare.app\Resources\SSCE". A google on SSCE reveals that Flare may well use the Sentry Spell-Checker Engine.

Cheers
Greg

This usually indicates a problem with distiller, which will prevent images being generated from Framemaker. For us, reinstalling Acrobat fixes the problem.

Are there any mif files in your Frame directory? I've struck problems in the past where xrefs are unresolved in Flare if you are linking to another frame file, and that file also exists as a .mif in the same directory.

What Flare version are you using? And are you preserving FrameMaker styles or defining your own styles?

Double check the stylesheet entries for youe heading 1 and 2 styles, and check the mc-auto-number format for both. They should be similar to the following:
h:{n+}
h:{n}.{n+}

If you are outputting direct to PDF, you must use page layouts. From the TOC properties dialog:
"Note: Master Pages are used for Word and FrameMaker output. They are not used for PDF, XHTML, or XPS output"

So you have 2 options:
1) Create a page layout that replicates what you have for masterpages ...

The header file is just a plain old text file, and you can add to that directly which can make your life easier. As an example:
1) In Flare, generate a list of all your topics (e.g. add a report file with "Topics Not Linked By Map ID")
2) Copy the list of topics into a column in Excel (you need to ...

A target is a deliverable or the output files that you produce, e.g. webhelp, PDF, html help etc. You must have a target defined to be able to "build" something (i.e. take all the Flare content and produce your desired output). You can have 1 target per output type, or multiple targets for only 1 ...

Negative margins might cause that, also long strings in the text box (with no spaces etc to break on). Maybe try editing the properties of the text box, and add a margin-right value.

If you cannot get it to work, post the relevant code - for example, source code from the topic, and CSS if using mc ...

Just ran a quick check on my sample project with HTML help, and it seems to work via CSS. You need to alter the MC-Label property for the class Madcap|conceptLink. We're on Flare v5

Cheers
Greg

There is an option in your webhelp target file (under Advanced), called "Do not use "Content" folder in output" Maybe that has somehow become enabled in the upgrade to v5?

Another thing to try, sometimes when opening a v4 project in v5, I get odd things happening when building for the first time ...

You can select and copy text using the Messages tab. I think you'll find that all errors (that show up in the Errors tab) are duplicated in the Messages tab also.

Now you mention it, there is a Save Log button that is never enabled. Might be worth raising a bug with Support about that one.

Cheers ...

Outside of lingo...
Tools>Manage Language Skins.
Russian appears for me (v5), but you have to create and translate it yourself.
"See Also" appears under Formats>Concept Link

Cheers
Greg

Instead of & between segments in the code, you need &

Try this instead

After running RegisterItcc.bat, did he recompile the help file(s)? From what I understand it is the compilation process that is broken and the batch file fixes (i.e. not a run-time thing that affects all chms on one computer

The solution is described in this post: http://forums.madcapsoftware.com/viewtopic.php?f=13&t=8458#p47956

You need to add a skin for each accordian item that you want to jump to. The difference between each skin file is in the Basic>Features list where you can set different defaults. Then when ...

Not personally, and I don't think Flare is well designed to do that job. Most QRC's I've seen are visually appealing, with heavy graphic content, callouts, arrows, CMYK color, fancy fonts etc, and take a lot of tweaking line spacing, before and after margins, and leading. Quite often those tweaks ...

Well done Douglas, looking good!

You can specifiy page layouts at the TOC level, which will override other page layouts specified. Check various books/topics in your TOC for Properites>Printed Output "Start a new chapter document". Note you can also associate a page layout at the project level (Project>Project Properties). This may ...