MadCap Software Forums

Just to follow up, we did this formatting for output that needed to end up in Word. We generated Word docs from Flare, then ran the macros, then copied the cleaner code into our existing Word templates. Since most of our output was for web/online rather than Word, we didn’t want to go to the trouble ...

Macro to convert web/html paragraphs to Word styles.


Sub stl_convert_all_paras_normal()
' ----
' This routine converts web-type paragraphs (p, p_1, p_2, etc) to Word Normal
' in the current selection in the active document.
' It loops through the document checking the style of each paragraph ...

Macro to convert Flare generated web/html headings to Word


Sub stl_convert_all_StandardHeadings()
' ----
' This routine converts web-type headings (H1) to standard Word ones (Heading 1),
' in the current active document.
' It loops through the document checking the style of each paragraph found ...

We used a macro that converted anything with the specified prefix to a standard Word style, so we didn't have to keep adding in all the possible ones that Flare came up with.
For example, all of your examples - "h2_heading2," "h2_Heading2," "h2_heading2_1," and "h2_Heading2_1" - since they all start ...

No, don't combine them.

The last place I worked at had a similar size. We ended up with separate projects and used global project linking to share common information. We stored the source in GIT and used automation tools to trigger builds to publish to the output locations.

We tested a combined ...

The main reason I paid for maintenance is so I could get the automatic updates.

As for support, I am also in a different time zone so only had bronze, but the (very) few times I have needed support, email overnight was fine.

Unfortunately this is not possible at this point. I encourage you to raise an enhancement request.
I have put in a similar request in the past - I would like to break a large Word import into subfolders using the H1 level headings as the sub-folder.

Thanks for your thoughts. There are a few different use cases around link updating – I think that I have just hit one instance where it doesn’t work. I agree that when moving within a project the links need to be updated – and this works fine.

The traditional import process works OK too – I was ...

I have used an external tool called FAR to do a bulk rename and keep links. I can't see how to do it directly in Flare.

And thanks to Madcap from me as well. These are the worst fires any of us (or our parents) can remember.

We modified "ul.MCGlossaryProxy_0"
Look under ul - we set the list-style-type to none

And here is another one that converts all "p" and "p_*" to normal paragraphs

Sub stl_convert_all_paras_normal()
' ----
' This routine converts web-type paragraphs (p, p_1, p_2, etc) to Word Normal
' in the current selection in the active document.
' It loops through the document checking the style ...

This routine will convert all html headings to equivalent Word headings.
I maintain a separate template (publishing-tools.dotm) to store the code but you could put the macros in Normal.dotm if you really want. I keep it in my Word Startup folder and link to the macros from the ribbon so I always ...

I have just started using micro content but have come across a few issues.
I created some micro content successfully in a number of ways - entering directly into the micro content editor, using snippets, and linking to other files - all worked well.
Then I tried adding some links into the micro ...

We have spotted an issue with the new drag and drop import feature - have reported it as a bug, though there was some discussion about whether it was desired behaviour or not.
My current work around is to use copy/paste of files in Windows rather than drag/drop.

In our style sheets and master pages ...

Flare does not map directly to Word styles - as mentioned it uses h1_heading1 and so on.
We have a set of macros that we run in Word to do the conversion after export.
Can post the code if you like.

I just tried this as well and had the same problem - I am using the latest version v2019 r2.
I have had no trouble creating file tags in the past - this looks like a new error.
As a work around, I can still edit them in the code OK (right-click - open in Internal text editor).

I follow a similar process to the others. We create Word targets first, mainly because we have more control.

We already have substantial Word templates, with images, backgrounds, boxes, etc in corporate brand styles, and did not want to have to recreate in Flare.
We generate a basic Word target ...

I don't think it breaks anything, but if you do an import from Word then Flare will recreate \Resources and store the imported \images and \Stylesheets (if selected) in there. You could end up with multiple stylesheets.

I have also raised a request along similar lines.

First up, though, I really like the drag and drop feature of creating a Word import - saves lots of time.
And imported list items have improved (but still not perfect - I need to test more).

But I have problems with the defaults.
The default for ...

Just for an example, we use the following syntax without errors - uses a single rather than a double quotes, which I believe should not matter:

@import url('main-styles.css');
@import url('local.css');

I don't see a report for "number of topics" but I use the file list for this.

Select View > File List and filter for topics.
If you then select all items (Ctrl-A) it will show you the total number down the bottom of the screen.

Another option is to run a report with both "Topics linked by map id ...

As well as defining new topic styles, are you also mapping the Word styles to Flare ones on the Paragraph Styles tab?
Check this help page for imports:
https://help.madcapsoftware.com/flare20 ... -Files.htm

Is it possible your Windows file extensions have been reset?

You can use the Export function. You can find that on the Project Organizer tab.
You can export depending on conditions, on targets, on file tags etc.
Here is the help file.
https://help.madcapsoftware.com/flare20 ... ojects.htm