MadCap Software Forums

You may also want to check out these topics/articles, which discuss using prism and prettify for syntax highlighting within Flare:
(Prism) https://forums.madcapsoftware.com/viewtopic.php?f=13&t=30396
(Prettify article with links and screen shots) https://www.madcapsoftware.com/blog/syntax ...

Interesting. It's in the Styles panel for me.

The styles in the list change depending on the location of the editing cursor. For example, the em style only shows up when the cursor (or selection) is at inline content (like text), which the tag can be applied to, as opposed to block content (like p ...

I put the analytics code in a snippet, then put that in the body of the master page(s). I can confirm analytics="" works in this arrangement.
Can I ask, how did you put the script into a snippet? And, subsequently, how did you insert the snippet into the body? I love this idea but I've tried doing ...

Did you try wrapping the phone number in a custom span tag, like the one I suggested? From my limited research it seems the problem may be due to browsers (and maybe print) breaking before a parenthesis (or bracket or other punctuation) even if it's preceded by a non-breaking space character.

I don't know if you can insert a variable into the value within the MadCap Stylesheet Editor, but you can certainly add a prefix before the breadcrumb proxy with anything you want by entering it on the master page or topic or wherever you put the proxy.

Also, different browsers commonly render bullet characters slightly differently. I think it may be safe to guess the same is true for browsers vs printer drivers vs PDF, unless you specify in your CSS exactly how the bullet characters should display for each medium.

Just an educated guess, though ...

D'oh! I just noticed you posted your question under Printed Documentation Targets. It's possible the target format (e.g. Word, PDF, etc.) treats word-wrapping similar to browsers, and so presents the same issue. Hopefully, the solution works for both web and print.

-jeff

Are you trying to add the non-breaking space in the topic text or in a variable?

One possible reason for the problem could be that browsers, particularly IE, tend to break on punctuation, such as the opening parenthesis in "(0)." One option could be to wrap the phone number (or the troublesome part ...

I made snippets for variables that I need to format, where I applied a span style as ChoccieMuffin mentioned. Then, instead of inserting the variable into a topic, I insert the snippet. If the variable has multiple definitions, I can set the value by right-clicking the inserted snippet and using the ...

I don't know about a variable, but I think you should be able to insert images into a frame and then apply conditions that you can include or exclude at the target level. Or, you should be able to add multiple images to a snippet and apply conditions to those images within the snippet. Insert the ...

I don't think so, but what you can do is create a snippet of the text/sentence that you want to use and apply a Snippet Condition , such as "Hide Content" for example. Save the snippet and then insert that into your topics (or other snippets). Then, exclude that at the snippet/topic/target level as ...

Just be mindful of case-sensitivity!

You can also edit the Xref in the CSS Editor (or in the text editor) to display different text for different media. For example, the default xref looks like this (I may have added italics and changed the color, I don't recall), Here it is in the Advanced Editor:

css-xref-diff-media.png

In the ...

Nice. On the occasions that I'm worried about clicking Replace All by accident, I copy the Find value into the Replace field. This works for most non-Regex searches. For Regex searches, I enter a Replace expression that equals the Find expression (the two are not always the same string).

Cheers ...

Just to add to Nita's reply, FWIW, I typically provide a sample of the output to clients, in addition to the review packet, so they can see how the finished document looks as well as review the source files.

Cheers,
-jeff

Hi folks,

I use snippets for common elements of my task steps and I use Snippet Variables to make quick customizations per topic. For example, I use snippets for common wording such as "Navigate to the <Page> and then select <Menu path> from the menu" and other similar general steps ...

Are you using the built-in Style editor for your CSS or are you using the Text Editor to manually change the CSS? I ask because it sounds like this could be based on the precedence/specificity of the style within your style sheet. Specificity rules often make me dizzy.

But, it's possible that, if ...

I think you're close but there may be a simpler way. Import the MainStyles.css style sheet into the "specialist" style sheet, and then customize the selectors (styles) in the new sheet. For styles that already exist in MainStyles, changes you make in the new style sheet will override existing values ...

It's a sad thought. I hope they stick around for a while, though. I love CHM files.

The warning in step 5 is a feature, not a bug. If you want to edit text displayed for the micro content result, but also have a link, you do it a different way (which is to type the text, and include a link.)
Yeah, thanks. I know it's part of the Microcontent feature. I only included that info to ...

Hi folks,

I recently tried to add some micro-content, mostly to test it out, and I ran into a frustrating issue. Here's what I did:
I selected steps in a topic and then clicked the Create Micro Content button on the Home tab of the ribbon.
I filled out the "New" dialog and gave the new micro ...

The shortcut for Make Simple Item(s) is Shift+Tab, but it doesn't seem to work on an <li> tag with a single <p> inside.
For this situation, if you want to get rid of the p tag (the one on the same line as the li ) you can "unbind" the paragraph by clicking somewhere on the line and then pressing ...

Feebeegeebee wrote:I also dislike the fact that they are planning on deprecating the Tool Strip, as I hate Ribbon style menus.

This. A thousand times, this.

In addition to the margin and padding properties, try adjusting the line-height property (listed under Font in the Flare CSS editor). From your screen shot, it looks like the line-height is currently set to 21.7667px, that's nearly a quarter of an inch (0.2267 inches for a 96px/in resolution or 0 ...