MadCap Software Forums

I'm using v4.2. I recently added page layouts and added a background image to my first page. I see the image just fine when I look at the page layout itself, but the image doesn't show up in generated FrameMaker or PDF output. Does anyone know why this is?

Thanks!

My project was created in v3.2. I've recently upgraded to v4.2. I had the impression that you would use master pages from Resources\Master Pages for help output and page layouts from Resources\Page Layouts for print output. I have both types of layouts created. When I'm in my WebHelp target and try ...

Thanks for the tip on the Master Page. If you don't want an ignored word - or any ignored words - to appear in your page source, you need to delete if from your Master Page. I think another tip is that you need to be choosy about what words you want to "ignore." We didn't realize they end up in the ...

I know how to add ignored words, but how can I delete them? If I open the Project Organizer\Advanced\Dictionary file, I only see the words I added, not the ones I specified to ignore. Is there a way I can do edit this data?

I've recently upgraded to 4.2 from 3.1. We have a project that includes content files for the master project and also one merged project. The merged project generates an Alias file and the master project generates a different Alias file. In 3.1 we had to manually merge the two alias files into one ...

We're still using Flare 3.1, and with merged WebHelp projects we have to use the knowledge base workaround where we manually create one alias file. Has this been corrected in v4? Will Flare build one alias file for your merged projects?

Thanks.

It sounds like that could create the printer-friendly version I'm looking for, but is there a way to open all the sequential topics together in that skin? For example, Tutorial 1 contains Topic A, Topic B, Topic C, and so forth. If I open a printer-friendly version of Topic A, it won't automatically ...

Is there a control you can add to WebHelp topics that open a printer-friendly version of the entire topic? I realize there is a Print button you can add to your skin, but that only prints the topic you have displayed, and the output includes other formatting from the master page (banner, breadcrumbs ...

I've been using Flare 3.1 for several months (waiting to upgrade to 4.1) and I come from a FrameMaker mentality. While I love how easy it is to export to WebHelp or printed documents, I don't get how I can reuse a file from one project to another while maintaining only one source file.

A good ...

Does anyone have suggestions on how to automate builds on our network? We're using v3.1 on our Win XP machines. Our projects are located on a network machine. I can easily create a batch file that kicks off madbuild from my machine, but is there any way I can set it up so the builds can be started ...

As it turns out, the problem was an apparently corrupt master page. This is the second time I've run into a bizarre build problem that was caused by the master page.

I decided to see how fast help would compile if I didn't use a master page. On my local drive, it took 1 min. 19 sec. (versus 1 hour ...

Thanks for all your responses and suggestions. I moved a copy of the project to my local drive and it is still processing the output. It's almost at 40 minutes processing time and it's nowhere near finished. I deleted all previous output before I started.

What surprises me is to hear that a project ...

There are three of us who work on this help project and we all use Windows XP. The Help project is located on a network drive, and the output goes to a subdirectory under the project directory. We created this project about a month ago.

The project (I'll call it Project A) is a compilation of topic ...

I've got a help project that has recently become very slow to build in WebHelp. I'm using Flare 3.1. The project isn't a large one and it used to take about 20 minutes to build. In the past two weeks or so, the time to complete a build has gone up tremendously, taking closer to 2 hours. The output ...

Hmmmm. My body proxy Start Number is set to default. I tried setting it to 2 and generated Frame output to see if it had any influence on the page numbers, but the chapters still start at 1. I also checked my bodyProxy mc-page-number-start-value in the stylesheet and that is (not set). Changing it ...

To add a little more info...My Flare master page for print is just the topic body proxy. I don't have any headers or footers in it, as I will apply those from the FrameMaker template. When I generate the Frame output from that master page, each new chapter starts at 1, as in my first post. Then I ...

Hi Steve,
If it is the master page forcing the restart, where do I change that? I checked the stylesheet settings for the bodyProxy that is on the master page, but I don't see anything that looks like it's setting the page number.

I'd like to add a comma for the index output, but where do I do that?

The output for my print version looks like this:
attributes 22

I would like for it to look like this:
attributes, 22

In my print TOC, topics that begin a new chapter have the property "Start a new chapter document" enabled. I do this because the first page of each chapter has a different page layout than the pages that follow it. Also, when we get our 1200+ page user guide into Flare we don't want one massive file ...

Thanks Lisa. When you distribute your content to your SMEs for review, do you have a way of highlighting new content for them? I'm wondering if there is a way in Flare to highlight text that is new, so the reviewers know to skip over old text and focus on the new? Since the conditional text colors ...

Yay, it's working! After reading the older post I realized my mistake was trying to set the Block text-indent instead of the Box margin-left. I had tried margin-left previously, but my px value was too low and it didn't indent at all, so then I gave up on it. 60 px was a good margin-left, and I ...

There are margin settings from the p class, other than that, I've tried to keep the settings as simple as possible.
p
{
font-family: sans-serif;
margin-right: 0px;
margin-left: 0px;
margin-top: 6pt;
margin-bottom: 6pt;
font-size: 10pt;
display: block;
}

I looked at the file in Notepad, but ...

This may be a question of trying to do too much with Flare, but I thought I'd ask in case anyone else is trying something like it.

Before we started our migration to Flare our docs were in Frame and we used WebWorks to output to HTML. When we added new release content in Frame, we applied a "Future ...

Thanks for your help! I created p.Numbered1 and p.Numbered styles and I can generate WebHelp without an error. As was mentioned, it looks different in the xml editor (the numbers are almost out of view in the left margin of the editor panel).

I had tried creating p subclasses for the numbered list ...

To add a little more detail, the following is what the li.Numbered1 style looks like:
li.Numbered1
{
mc-auto-number-format: 'H:{n=1}.';
mc-auto-number-offset: 20px;
display: list-item;
mc-auto-number-position: outside-head;
}

With this style, I get double numbers - both the simple list number ...