MadCap Software Forums

Without testing I'd suggest this is just one of those CSS things that gets lost in translation when building a PDF. I'd personally set a class of .VariablesetVariable name rather than MadCap|Variable.customclass if you know it's always going to be the product variable you want to colour purple. You ...

Can you show me the code for the coloured element? If you'd prefer this to avoid the picture you can tell it to clear: right; which will make it float past any element that is floated to the right, although I suspect you just want the background-color to occupy the same space as the content.

Nice work debugging, this is the exact fix you needed

Add a new Report file in Project Explorer. There's a template 'Conditions Report' that will show you what you need or you can make a custom one.

Search results take weighting into account, so a h1 will have a higher value and will appear higher in the list than a h2, h3 etc. or a p block, however I believe multiple references will outweigh a single h1 which is likely why your results are getting 'buried'. I could ramble on but it's best to ...

CoolLime wrote:I learned something here. But then what is MadCap|variable.URL then?

That's just a custom class called "URL" for variables. Presumably it's just used to style plain text variables as a clickable URL would be.

You could use a variable as a link if desired:

I can't realistically see any use for a local workspace with Flare. Local workspaces are generally for testing code in isolation before merging up all of your changes and they present limitations that you don't have when working directly in the server workspace.

I put my dropdowns directly into a div block and set page-break-before: always on the div, works for me

Just goes to show how fussy Word output is! Great troubleshooting and thanks for posting your solution

Thanks for the super prompt reply Dave, I inspected the page you linked earlier in the thread and amended my ga event to use ga("gtag_UA_XXXXXXX_X.send" ... and this seems to work fine, in that I now actually have events appearing in my analytics!

Thanks again

...

Hi Dave, I love this set-up and I've tried to implement something similar but I seem to get an error after clicking Yes or No;


Running command: ga("send", "event", "Feedback - Yes", "N/A", "http://mypage.com")
Command ignored. Unknown target: undefined


I've completed all of the google ...

Changes made after you click Track Changes will show in red providing Show Changes is ticked.

As far as the TM goes, you'd place that outside of the variable, i.e. [%=Variables.Product%]^TM. I'm at a lost as to why you're having this problem, just ensure you're doing something along the lines of the following:
<span class="nowrap">[%=Variables.Product%]^TM.</span>

You can insert a Variable inline by using [%=Variableset.Variablename%] - you can use this in a span class with whatever formatting you need. Give that a try in conjunction with your white-space fix and see how that works out.

Ahhh, a lovely Flareism. Can I ask if there's a particular reason you use a snippet over a variable here?

If I understand your problem correctly, I'd probably be tempted to just create a destination for each different author...

How big is your project Madeline? Do you have any auto suggestion settings enabled?

Seems I gave you duff advice and Flare enforces these tags beginning with "<meta", sorry about that.

MasterPages will work fine for this, especially if you always have a Spanish (for example) equivalent page. You could get a little clever with the href link and some variables if you wanted to, but ...

Put the product name in a span class and add the attribute white-space: nowrap;

Any particular reason you aren't using Capture?

Do you have one target per language? If so I'd use the meta tags option in the target itself.

No, you don't need to define a class for it to be declared. Your problem is likely that Flare is looking for a closing '/' in some elements. For example:
<link href="styles.css" rel="stylesheet" type="text/css">
is acceptable HTML but flare insists on the following:
<link href="styles.css" rel ...

You can use the following CSS to select every li that comes immediately after a pre:

I believe the 'proper' place to do this would be Project > Project Properties > Source Control, but AFAIK, all this actually does is edit the .flproj file as you've already done. The proof of the pudding is in the eating as they say and if your method works, then I guess you're good to go!