MadCap Software Forums

In case it wasn't clear from what ChoccieMuffin said, if the topic does not have a <title> section then the title will be replaced by H1 at build time. Therefore, deleting the titles from your topics is the easiest way to keep in in sync!

Another thing to check: there might be an issue on the topic before or after the break. That would cause it to stay in the same place even when you've moved the topic you think is offending. It could be worth making a fresh TOC and adding topics/books to it one by one to check when the problem ...

On the topic of keyboard shortcuts, you can record macros and apply them to any shortcut you want. You can record and manage them from the Tools ribbon.

I've used that to create shortcuts for our span classes - but note that the behaviour isn't quite the same as the classic CTRL+B. You have to ...

Unfortunately the mc-heading-level determines BOTH the print table of contents level AND the heading level in the document (if the Use TOC Depth is turned on). TOC level 1 = h1 = print table of contents level 1, because they all =mc-heading-level 1.

You could avoid the 'push down' effect by ...

This can easily be handled through the stylesheet. Images use the img tag, so you can open that selector in your stylesheet and set the height and width as required. That is most convenient if the majority of images in your project have the same size requirements. For any exceptions you can edit the ...

It's probably six of one, half a dozen of the other really. We keep all of our (many many) snippets in the global project, so the list is really too long to look through for every import (and it takes too long to over-write the whole lot). The easier workflow for us is Synchronise Global -> Import ...

There are a couple of ways you can do that:

- External Resources, which let you map a folder in Flare to an external folder and synchronise changes between them. See here in the Help: https://help.madcapsoftware.com/flare2019r2/Content/Flare/External-Resources/External-Resources.htm

- Global ...

Oh, good spotting - thanks for sharing the solution!

By the way, the css property works great for hiding text in pdf, especially if it might end up on differently coloured backgrounds. The text won't be selectable and it will still appear in your header/footer regardless.

My heart goes out to you from NZ as well. We're seeing some effects even here - I can't imagine the devastation in Australia itself.

That one's pretty tricky, unfortunately. The autonumbers have a fixed width - they're kind of just objects that Flare is inserting beside your text much like custom list bullets. The best thing to do is to give them a width and position that is unlikely to cause overlap and just accept that it is ...

Sorry, I suggested you post some code and immediately went away on summer holiday! Unfortunately I don't see anything wrong with your code.

One further suggestion: instead of writing your footer directly into the page layout frame, try writing it into a snippet and inserting that into the frame. I ...

Hmm, I misinterpreted you - I didn't realise that you had a single topic intended to span several pages rather than several topics.

Looking at what you have described in your second post, I don't see any reason why that would not work. Now you've moved the heading variable to the top of the topic ...

The heading variables look for the most recent heading that appears on the page - they aren't going to look 'forward' to future topics. If you want the heading to be picked up on your title page, you have to put it on your title page or before!

If your translation provider is using Madcap Lingo, I believe that there is some functionality for assessing which strings in the project have been changed since the last time it was loaded in.

If you want to do it with just Flare, try creating some custom Reports in the Project>Reports tab. There ...

Not sure how other people handle empty pages, but I would do it by creating a placeholder topic that doesn't have any content, inserting it whenever necessary and setting it to 'Empty Left' in the TOC. Bit of a brute force method.

This is happening because you have the Generate resized copies of scaled images option checked in the Target (Advanced tab). It has exactly the behaviour you've described, and I've found too that the option kills animated gifs (presumably because Flare creates a new copy of the image but doesn't ...

I don't know about BitBucket in particular, but try the commit window if such a thing exists? There might be a little 'merge conflicts' flag up the top that should hopefully open the merge dialogue.

A variant of this problem has just started up for me: when I hit build the Status hangs on Started, then jumps straight to terminated. However, the document has actually been built - I can open it from the Output folder, just not from the Builds pane itself. No issues in the build log, so it's as ...

You should be able to enter in <meta> tags for information just like any HTML page. See https://www.w3schools.com/tags/tag_meta.asp

But putting hidden content on the topic itself would be more obvious... You might consider using snippets? Create one snippet per month/quarter and put it onto each ...

You can set the output folder for each target in the Target Editor, General tab.

For reference, I get this error periodically - usually, as expected, when I've been moving files around.
Generally the error is fixed if I close Flare, commit all current changes (I use Git Extensions) and open Flare again. It seems to me that the Working Directory has just become a bit messed up ...

Ok, I've worked out the issue:
When Flare makes the heading levels follow the TOC, it does so by shifting them down or up an h-level. h1 becomes h2, h2 becomes h3, etc. If the heading has a class, it keeps that class, e.g. h1.myclass becomes h2.myclass, etc.

So in your situation:
Grandparent h1 ...

I haven't used table styles, but it seems like it could be worth a shot. If you use mediums for the different companies (like I do sometimes), you could go into the table style css code and add in the code for each company medium. There's a chance that Flare will see the @medium flag and treat it ...

Hmm... The 'Use TOC Depth for Heading Levels' option ought to do exactly what you want, and it does so for me.

One potential issue I can think of: Have you messed with the mc-heading-level of any of the other heading levels? Because that is how Flare 'knows' what level to put headings in the print ...

I don't think that should be true? I don't think that anything in Flare actually demands that a topic start with a head, it's just generally good practice.

But if it works it works!