MadCap Software Forums

Yeah ... I'm not touching that one ... keep yer head down, Steve

Thanks for the responses. I did bind a copy of a project to source control for testing purposes, and it's been going pretty poorly, even with a dedicated TFS testing environment. I haven't seen some of the other issues reported, such as freezing on startup. However, a couple days ago I tried to rena...

We're considering binding our Help projects to TFS. Just wondering if people who've done this can share their experiences -- good or bad. My current thought is that we really don't need a full version history on every file. I think it would be easier to work in a shared network folder with automated...

Yeah you can't apply that style at the tr level for some reason. It might be slightly more work, but you could just create three td classes. As an added benefit, you can easily apply these in the WYSIWYG (which doesn't display tr elements). td.left_border {border-left: 1px solid black; border-top: 1...

Yeah that's certainly a conversation I had. The impetus here is keeping detailed product info away from competitors. Obviously, we have no illusions that someone determined to pass on product information will find a way to do so, but we'd like to build in a deterrent that would force people to make ...

I've recently been asked to find a way to add copy protection to our CHM deliverables. It certainly doesn't need to be bulletproof, but should be enough to discourage our users from passing on the information.

Has anyone out there done this before? Any tips would be much appreciated!

Theresa - I was finally able to get my XML files through the Flare build process unaltered. The key is to make sure no master pages are assigned to the target you're building (i.e. select (default) as the Master Page). You shouldn't need to change the file extensions or store the files in the resour...

The namespace is included in the XML file. Before I compile, the code looks like this: <?xml version=\"1.0\" encoding=\"utf-8\"?> <catalog class=\"\" MadCap:conditionTagExpression=\"\" xmlns:MadCap=\"http://www.madcapsoftware.com/Schemas/MadCap.xsd\"...

I have an XML file (source.xml), and I'm using Javascript to pull information from the XML file and display it in various Flare topics. This works just fine for CHM output, but the source.xml file gets mangled when I build WebHelp output. Looks like Flare is trying to make it into a browser-friendly...