MadCap Software Forums

According to tech support, they were able to replicate this problem when previewing a topic as a PDF target and it's a bug. This makes sense, as I was previewing several topics before attempting to add them to version control.

Thanks Donna! Bug report was just submitted.

Not sure yet if this is limited to Flare 2017 r2, but when using it I found that a redundant copy of my "PageLayouts" directory and one of the page layout files is being mysteriously added to sub-directories within my Topics directory.

For example, I was adding/editing new topics within Content ...

I just experienced this problem when inserting a cross-reference and also found that re-selecting Topic Files in the filter fixed it.

I haven't actually used them, but you could investigate snippet conditions?
http://help.madcapsoftware.com/flare201 ... itions.htm

I'm interested too! We are investigating Git and our projects would not be bound to Flare. (We're currently using SVN, not bound to Flare).

Not related to Flare, but I'd also be curious to know how you're handling binary and large files with Git? We're also investigating Git LFS for this. We build ...

We also use TeamCity to generate Flare targets and package them for installer consumption and publishing for internal access. It works great for us too!

We also use SVN, but don't use source control integration with Flare. I haven't tried the pre- and post-build events in Flare 2017.

Is it possible that any of the globally-linked files in your project are read-only at the time of import? We use SVN and our projects are not bound to source control in Flare. We've found that if *any* of the files to be imported are read-only, the import silently fails for all files and the status ...

I believe this is actually a feature in Flare 2017 when dragging-and-dropping topics to the TOC. But when built using an earlier version, the [%=System.LinkedTitle%] is displayed instead. Is this content being worked on by multiple writers, and if so, is it possible someone is using Flare 2017?

Could you export only the content you need (based on target, condition, etc.) and then use the exported Flare project as the source for the Lingo project? This is what we do when we only need to translate a subset of content in a project. I tend to export based on target as it includes everything ...

Yeah, we have to do this each time we install Flare to a new PC/build machine. This issue has bitten us many times over the years. Now we have a topic in our internal documentation for configuring new machines for use with Flare.

Unfortunately, I don't know much (if anything) about Jenkins. I use TeamCity to build our documentation and use a TeamCity build step to build the Flare target from the command line. Within the build step, I've configured how Flare errorlevel codes are handled and to not fail for compiler warnings ...

Hmmm. A few more questions/ideas:
1) I'm assuming the images that were not properly sized are below the max-width specified in the print medium of your .css file?
2) For the image that was not correctly resized, if you right-click the image within the topic, click Image Properties and select the ...

We've noticed this too and I have been meaning to file a bug. The superscript appearance also occurs if you apply a condition tag to a span of text within a table.

First guess: Click File > Options. On the General tab of the Options dialog, is the "Automatically resize low DPI images" checkbox checked? This can cause images to be automatically resized and this is checked by default when you install Flare. (We always run into this issue when installing Flare to ...

Yeah, I've encountered this as well.

I'm able to use Flare 12 command line to build single targets without any problems.
-When specifying the folder, you don't need to specify the entire path, only the subdirectory path with Project/Targets.
-I'm using a forward slash rather than a backslash in the subdirectory path.

Instead of this ...

I looked at Pulse a few years ago and decided we didn't need to go there yet. We now really need stats on our internally hosted sites. I am back to considering Pulse but reading all of the lackluster reviews and comments has really discouraged me!
We don't really need or care about the social ...

Exactly! :) We store .CSS files, global snippets that contain boiler plate text, boiler plate images, master pages, page layouts, an HTML5 skin, a variable set, etc., in a global English project. In the global variable set, we have a variable that we use for device names with a default definition ...

Hmmm. A few thoughts:
-You shouldn't have to specify the file extension.
- It sounds like you've already tried this, but if the target is stored in a sub-directory of Project/Targets, you'll need to include this sub-directory in the path:
madbuild -project C:\My Projects\FrameMaker_Flare1 ...

You should be able to specify the logo in the skin editor, under Styles > Logos > Background > Image:
2016-12-05_14-35-05.png
In the Skin Editor, I find it helpful to click the "Highlight" button at the top of the UI. You can then click on different elements in the right pane and it will ...

We do this with global project linking by creating a variable set in a "global" project that is imported into all local projects. We then overwrite the default variable definitions in the local target files. This is helpful as we have different terms for various devices that we support, but want to ...

I think I found a workaround for this problem using Flare 12 or 2016r2+Acrobat Pro DC:
-After creating the shared review file, choose File > Save a Copy. Save the file (with the same name) to your PC in a different location than the original.
-Close the original shared review file.
-Copy the new ...

MaryseCoutureSh wrote:I have a question: do your global/child projects have different CSH files (alias and header files)? If yes, how you manage these files?

We don't maintain global CSH files. For the projects that use them, they are maintained in the local/child project only.

Glad it helped! I was lucky when I discovered this problem because the last style I had changed were the div styles, so it was easier to isolate.