MadCap Software Forums

I imagine it's just using whatever stylesheet is the primary for your project. It should use the target stylesheet in the output.

I've had a really hard time with Flare's Git integration, to the extent that I think we shouldn't have bothered in the first place. Especially issues with authentication - it doesn't like the two-factor authentication that our Git provider requires. We basically just use Git Extensions now ...

It's a bit difficult to tell what is wrong from your description - there are all sorts of things it could be. But here is what I would do:

Create a single page layout file with three pages: Title, First and Body (or, if required, Title, First, Left, Right).
Put the title page content in one ...

I have the same very frustrating problem - our products and companies vary between vowels and consonants. I use snippets with condition on the [n] so it will only appear in some outputs (easier than creating new variables for me). Note that you will need two - one for small a(n) and one for capital ...

Also - do you know how we can remove the icon from the skin, now, that shows the ability to turn highlight on/off, since we have made it transparent?

Topic Toolbar tab in the Skins Editor.

Skins are weird! The images in the skin aren't stored in the explorer and linked like in topics etc, but are stored in the skin file itself as binary. If you open the skin file as text, you will see a bunch of code that represents the image. I'm sure that you could retrieve the image from the binary ...

Slightly old thread, but I think the name is what causes the confusion:

New topic styles are the styles which create a new topic.
Style mappings define which Word styles go into the auto-generated stylesheet.

Maybe try opening the Import file as text and checking whether there are any spurious css references in there.

Sometimes I have differences between the preview and the output in PDF because the preview doesn't have to worry about other topics. This really got us one time in a document with a lot of images, because things didn't end up where the preview suggested. Might not be your issue though.

It would probably help more if you asked some specific questions or pointed out what wasn't working instead of a general call for 'basic instruction'! It's hard to tell what you actually need help with (source control in general? integration with Flare? any number of minor issues that I might know ...

The characters you are seeing is how Git marks merge conflicts within files. This happens when the same line/lines of code has been edited in both your local file and in the remote (i.e. whatever your coworkers have edited), or in two different branches. Usually whatever git manager you're using ...

Counter-intuitive, but I generally find that this happens when there are too many attempts to control the page breaks. Flare has to put a page break in somewhere, but it you overdefine the situation it will just try to put one in anywhere. Maybe the following page has too much content that isn't ...

It actually still keeps them, it just outputs them in a different way. They won't be the standard Heading 1, Heading 2 etc - they'll appear in the style picker in Word as h1_heading1, h2_heading2, etc. I don't think Flare can map them back to their original positions because the styles are encoded ...

I haven't dealt with your exact problem, but here's my thinking:

The examples given in that Stack Overflow may well work! Flare stylesheets are no more and no less than CSS stylesheets, only limited by what Flare will support. This differs between different output types. I would suggest that you ...

It seems to me that your Word doc might be saved as .doc or .docm. You want to save it as .docx (i.e. the XML format that modern MS Word uses). There should be no additional steps required to bring it into Flare after that.

As I discovered when starting to look at HTML after a long time of only creating PDFs, skins are weird!

Essentially when you put an image in a skin (whether a full skin or Favicons or w/e) it doesn't actually create a link to the image. What it does store the image as code within the skin xml ...

Unfortunately not - MS Word is relatively limited when it comes to page layouts. I do notice that the Flare Help mentions that decoration frames are not support in Word, but doesn't mention anything about frame background images.

A couple of things that might be tripping you up:

When you say 'kept that TOC active', what do you mean exactly? It's not enough to set a TOC as the Primary for the project - you need to tell the target which TOC to use.
To prevent Flare from building the entire project, make sure that the ...

Easy. I used the FAR: Find and Replace tool to replace every tab (regex \t) in the relevant folder with four spaces. The line breaks aren't perfect (I wish I could tell Flare that it could wrap at particular characters - e.g before < and after >), but they're definitely good enough.

Submitted that ...

Oh, that is very clever, I reckon I can work with that. This code isn't actually being updated regularly from a live source (I just had to import it from Author-It). So if I can work out how to run a find/replace on a tab, I should be able to replace each tab in the document with 2-3 space ...

My problem: long lines of text in <pre> tags extend off the edge of the page in pdf.

I know that this has been discussed before (in particular here: https://forums.madcapsoftware.com/viewtopic.php?f=6&t=8630 ) but I haven't found a solution anywhere for PDF output in particular .

A few notes ...

You'll probably find that there are a number of PDF features that aren't supported in Word. The ones that bugged me the most were decoration frames in page layouts (e.g. the logo on the title page), heading variables (e.g. in the header/footer) and div tags (simply ignored).

Probably an obvious question, but it has to be asked - neither of you have any styling on the Madcap variable or Madcap snippettext selectors respectively?

It isn't possible to define the style for a variable in your stylesheet. But I don't understand what you mean by " Madcap snippettext ...

That is interesting! I had some assumptions about how snippets worked because if you put a snippet in a TOC for a print output, it just inserts itself in the correct place in the output as if it were a topic. I just tested the same for HTML5 and it's completely different: for some reason the build ...

For future reference: the Flare UI won't do it, but if you jump over to the text editor you absolutely can apply a second style class to an element without affecting the first. Just find the class="caption_next" bit and add the other class, for class="caption_next body".