MadCap Software Forums

Would it be menu skin or top nav skin? Would it potentially be under menu item level 2 for example? And would it be Margin, Padding, or Block? There is a value called Text Indent under Block - but from what I can see so far it doesn't seem to have an effect. I am doing lots of trial and error but no ...

Hi, finally managed to find time to get back to this...
See screenshot below. Looks like the menu is using the li tag, and I guess that explains the indent.
Does this mean I need to use a separate stylesheet for the home page?
Or can I make a new style class for li and then make the menu use that ...

Yes I can do that, absolutely. Can you be more specific though - for the Nav code, where do I find it. And for the CSS, which elements?

I have tried and tried...but just can't work out how to get rid of this unwanted indent in my top nav sub-menu. Any clues?
Well, come to think of it, also of course I would like to stop the text spilling outside the sub-menu box.
Can I sort it in the skin? Or do I need to use the stylesheet?

Sub ...

Got it. If you include a dot file ending in the Output field, for example, ".pdf" - all works fine.
If you don't have a dot file ending in the Output field, Flare truncates the file name after the dot (if there is a dot).

Okay, I fixed it by copying in a target file where the Output Field is working correctly. Now the Output Field accepts decimal numbers and works as expected. So, problem solved. But clearly something strange is going on. For some of our projects, the target file and Output Field work fine. For some ...

This is still a mystery. Any help really appreciated. MadCap?

Thanks for the pointer to the other thread. Unfortunately, it didn't help.
The strange thing is I have other projects where a dot in the Output File is working fine.
So, it is something with this particular project.
And, actually, even for this particular project the Output File worked correctly ...

This is a very strange one. What am I missing? In one of our projects, the Output File field in the Target is behaving as follows: If the specified file name includes a decimal number, for example, version 6.1 - the resulting output file name cuts at the 6. So, for example, if Service Manger 6.1 ...

Okay, I've solved it - but I don't really understand.
In the chapters that didn't work, the h1 tagging looked like A below - so I took out the xmlns attribute to make it like B.
This I could understand....
But then I noticed that some (but not all) of the chapters that have been working fine have h1 ...

And, by the way, the chapter numbers come out correctly in the header and in the body text. See pic.

The chapter word, chapter number, and chapter heading appear as wanted in my PDF Bookmark list for the first eight chapters, but are missing the chapter word and chapter number for the last four entries. See pic below. Also, all of the last four chapters have H2s underneath - and although they are ...

The TOC was correct by the way...

Okay, I have it all working. Your post helped. When I do a full build (instead of just page preview) I get Appendix A and so on.
But I can see now that the style definitions need to be: {paranum} {paratext}
Was there some change perhaps between Flare 10 and Flare 11? It seems very odd to me that ...

Good thinking. I just checked and unfortunately it doesn't. In the adjusted case, I still end up with Appendix 1 instead of Appendix A.
By the way, the appendices are rendered correctly in the actual headings - so in both projects, the appendices appear correctly as Appendix A, Appendix B, and so on.

I have two pretty much identical projects (in fact I copied one from the other) but my appendix cross references are behaving differently. I am clearly missing something, but I can't see what it is. Any help appreciated. Below is the full story. I am running Flare 11 on Windows 10.

In project A ...

Interesting to read about ClearCase, thanks.
The entire thread really helped me get some clarity around this issue - and we have decided to push ahead using Subversion. I have it set up now, so I will try various use cases and see how it goes.
We will also, later, experiment with Accurev (our ...

Thanks all for your input. Extremely useful to get input from this general level (it is what I had hoped for when I posted my "too-general" question). If anybody else wants to rant/rave/praise, I am interested.

That's a very good answer. Thanks.
You say that Subversion has some major flaws and annoyances. What are these? Or is it just the performance?
This would be a problem I would say, as one of the reasons we are trying to get Flare into source control is Flare's poor performance when working over a ...

My question is, in a way, simple - we need and want to implement source control for our large Flare project, but which source control system shall we go for? Yes, I know, I am not supposed to ask such general questions, but I think in this case it makes sense to do so. Our goal is simple. A source ...

Perfect, thanks so much.

Does anybody know of a graphical merge tool to use with ClearCase. We are using Flare 8.1.1.
(With ClearCase, there seems to be a problem merging when the files are UTF. We were able to get round this by installing and using KDiff3, but this is a text based tool and merging seems tricky in Flare ...

In the Pending Check-Ins tab, does anybody know if it is possible to use more advanced filtering. I want all Flare related files to show up (.html, .css, and so on), but I don't particularly want ClearCase related files to show up (for example, .keep).

We are experimenting with ClearCase for source control. We are using Flare 8.1.1.
When you move a file, it seems like the version history is lost.
Also, it seems like one has to, after moving, add the newly moved file to the source control system.
Are we doing something wrong? Is there a particular ...

Thanks. Yes I have been looking into the relationship tables a little more and it could be the way to go.
I think concept linking is closer to the topics and, therefore, probably easier to set up.
But, if the output isn't up to scratch - then it is not much use.