MadCap Software Forums

I suggest you add this comment verbatim as a feature request. Or email MadCap directly to let them know why you're not using it, and unlikely to renew your subscription. They need to know.

If you've got your @print medium set up nicely, then the user should be able to print the topic from their browser.

Or do you mean, they want to have a PDF they can refer to, rather than something printed on paper? If the second, then they should be able to print to a PDF rather than to a printer ...

I don't understand what you're trying to achieve.

Meanwhile you might want to look at table stylesheets, the help is here: https://help.madcapsoftware.com/flare20 ... sheets.htm

Assuming you have a condition tag set defined that includes Prod_A, Prod_B, Prod_C etc, create the styles to apply the conditions in your DEFAULT medium, and only in the REVIEW medium add the background colours.

So this is what you need to add to your DEFAULT medium (assuming you've created a ...

Both are good points.

In this project, I followed Madcap's template structure and just changed names. The topics must appear in a certain order irrespective of where they are used. I could create a large topic for each section, leading to long web pages (something I didn't want).

Usually, however ...

Thinking off the top of my head, you can do this.

1. Create a "REVIEW" medium in your stylesheet.
2. Create a "REVIEW" target.
2. Create styles in your stylesheet to apply the conditions and, in the REVIEW medium only , apply background colours as you want.
3. Apply those styles, not just the ...

How about using different masterpages (or whatever they're called now - template pages?) so your HOME page uses a template that doesn't have a Search bar and your topics use a different template that does have one.

Joesii, I'm not convinced you've now got valid HTML - I didn't think a <p> was a valid child for an <ol>, as you now seem to have for "First nested paragraph" and "Second nested paragraph".

To make your original source code appear nested, I only had to add two Returns (before </li> in the two ...

Yes, you've got the gist of it.

I suggest that you look at using MEDIUMs, as that might allow you to get where you want to go.

I think it depends on how you're anticipating using your conditions, I don't quite understand what you're trying to achieve.

A first thing to do is close Flare, delete the \Analyzer folder, then re-open the project. That forces Flare to regenerate the database of links etc. You might find that solves your problem, but it won't do any harm. Give it a try and see what happens.

Well done, Bruce, happy to see you getting stuck in and playing in your stylesheet!

I have w3schools.com bookmarked, and you'll find some useful resources and information in there to do with CSS.

ChoccieMuffin's response is perfect for someone who is just learning CSS - I have another suggestion for when you're feeling more confident.
If your tables with narrow columns have a specific style class, you can specify that you want any paragraphs (of any type) within that table to use hyphens ...

Any updates on this? I'm trying to do something with ::before and can't work out how to do it. If it's a bug I'll stop trying.

Lots of questions, I'll answer the one I can.

I could create a style class p.tablePara in my stylesheet, with hyphenation turned on for that style, and specify in the table style creator that this style be used for all cells in the table.

But wouldn't that get overridden if I then apply a style ...

Lance_Moore wrote:Thank you, I'll work through that.
And thanks for the text version! (as we can't access the editors due to using CSS exceeding their support! lol)

I prefer to work in my CSS as text - I very rarely do anything at all in the Flare CSS editor!
Hope the suggestion helps.

This is a really old thread and since it was written, MadCap has introduced a way to include a condition in a style. For example, add a condition to your condition set called INTERNAL, then add the following to your stylesheet:

.INTERNAL
{
mc-conditions: '[[[ConditionSetName]]].INTERNAL';
color ...

I thought that'd be what you've done. To build on that, you might want to add a generic style, e.g. .INTERNAL, which includes that condition but also contains the colours you want. For example, you could have this in your stylesheet:

.INTERNAL
{
background: #DDE57F;
mc-conditions: general.Internal ...

How have you styled your internal only content? Just with a condition? Or with a specific style?

Beautifully put, ajturnersurrey, that's how I'd approach it too.

And when it comes to managing version numbers, consider using a variable. You can modify a variable for a specific target when necessary, so in the Joe target the version number could be 1.2 and the Bob target could have version ...

Warm welcome to the forums, DroodWrites, and you make a very good point. I doubt you'll get much of a response though, as the most recent post on that thread was five years ago. But welcome anyway!

People who prepare training material are in a completely different team to those who prepare user documentation.

In your circumstance, where both teams use Flare, could you use a "globals" project that contains the stuff that both teams need, and then import the project into both teams' Flare ...

This might be something to talk to Tech Support about, as it might be a bug. In fact, why not just report it as a bug and see what Tech Support say? Link for reporting bugs is in my signature below.

Might be a silly suggestion, but how about applying the .nobr style to "exit() ", with the space included in your .nobr span?

I would see snippets as the perfect solution in your situation.

Hi all

My current company is looking for a replacement technical author for my role as I'm moving on. The role will be based in Belgrade on a hybrid basis, working with international teams of developers, business analysts, testers and product owners as well as the rest of the documentation team ...