MadCap Software Forums

In a further messages, they suggested removing the \ from cross-reference formats in Frame. The \ is used to indicate a non-breaking space in the cross-reference format, for example, between the word "page" and the page number.

I tried it and it seemed to resolve the problem, although for the life ...

Madcap's support got back to me this afternoon and provided a fix. Apparently the problem lies with one of the built-in cross-reference styles, and the fix is to remove the character from the project's style sheet. After doing this, the build works.

Keith

In the second screenshot, it looks like it's hitting the error in the Managing_Orders\Viewing_transferred_user_orders.htm file. Try opening that file in the Internal Text Editor and see if you find that character somewhere in the code. If it's there, then delete it. It doesn't indicate where it ...

I have been trying to build WebHelp from projects created by importing Frame 8 files and every build fails with the following error:
Build_internal_error.jpg
This doesn't occur in every topic - it seems to be happening in 10 to 20 percent of our topics, and I haven't been able to find a pattern ...

I've created a support case about an issue I'm having generating WebHelp. This was almost 3 weeks ago, and after uploading the project file to MadCaps's FM server, I've had no response.

I see that there is a page for submitting support requests and another for submitting bugs and feature requests ...

I've been trying to build WebHelp from projects created by importing our Frame 8 files and every build has failed with an error about an invalid character 0x11.

When I import the files, I see that the import process displays some warning and error messages, but I can't see any way of saving these ...

Check out Tom Johnson's blog, I'd Rather Be Writing. He has written several posts about quick start guides, and collected some of them here: http://www.idratherbewriting.com/quickreferenceguides/

He gave a presentation about quick start guides at the STC Summit in Atlanta this year. It's probably ...

Ah, enlightenment dawns. :idea:

When I was testing importing out I was working with individual chapter files to save time. There were no TOCs, so Flare didn't build a TOC from the Frame TOC.

I just did a test import with a Frame book and a Word file that had an embedded TOC and Flare built a TOC ...

I have several FrameMaker books that I want to import into Flare. The size varies, but they average around 100 topics each.

From what I have seen in my testing so far, I have to manually re-create the structure of the book after I import the topics. This is painful.

Is there any way of ...

I met with our release manager on Friday and it looks like our options are probably CVS with a plug-in, which on TBD, or possibly subversion. Apparently PVCS has issues with deleting files and renaming files or directories. Since our developers are using CVS, there's already a server set up.

I'm ...

Unless I'm missing something basic, it appears that Flare doesn't have a feature comparable to Word's Track Changes. Is that the case?

If so, I suppose I could put together a Change Bar style and apply it manually for reviews, something like FrameMaker's Change Bar style.

But I'd like to be proven ...

Doesn't work for me - with a standard MS optical mouse. Nor does CTRL +.

BTW, this isn't in a browser, it's in Flare's native help viewer.

Keith

I've just gotten Flare and want to set it up to integrate with a source control system. From talking with our developers, it looks like I can use either CVS or PVCS, and might be able to use Subversion, but I think that Subversion is a low-likelihood possibility.

According to the Flare docs, I will ...

I'm finding that the default size of the text in Flare's help system is a bit small for my aging and nearsighted eyes. Is there any way of increasing the size of the help text to make it easier to read? I've looked and I can't see any way of doing it.

The cause of the problem has been found. It turns out to happen if you have large fonts installed, i.e., 120 dpi fonts instead of 96 dpi. I have to thank MadCap support for digging into this.

So if you're having this problem, go into the Desktop Properties - Settings tab, click Advanced, go into ...

Well, I turned off short-line elimination and hyphenation, and checked that I was working with the proper output medium, and it doesn't make any difference. So I guess I'll have to wait and see what sort of response I get from my bug report.

Keith

I've submitted a bug report. I can't open a support ticket as I don't have a maintenance key - the copy of Blaze I have is a review copy, courtesy of Sharon Burton. I have a license key but the support ticket form doesn't accept that.

Thanks,
Keith

I've removed the letter spacing parameter from the project's style sheet and rebuilt it. It made no difference whatsoever.

I get the same results using one of the sample projects, so the problem is obviously in how Flare is generating PDFs, as opposed to Word output, which appears to be fine.

I am ...

I don't have a <body> tag.

I do have a p.BodyText which is the Blaze translation of my Frame default paragraph style:

p.BodyText
{
text-align: left;
margin-left: 0in;
margin-right: 0in;
margin-top: 0pt;
margin-bottom: 6pt;
font-family: 'Times New Roman';
font-weight: normal;
font-style ...

I created a project from one of the default Factory templates, set the font to Times New Roman, which is what I use for body text, and rebuilt the PDF, and it still looks odd.

I also followed Paul's suggestions in the previous message and it didn't make any difference. All of my paragraph styles ...

I'm using the standard TrueType fonts that come with Windows: Times New Roman, Arial, Consolas.

Interesting. If it's a bug, it's one that should have kept the program from being released, given that PDF output is pretty important in a program that's designed to produce output for print.

After reading the previous reply, I tried output to Word and it appears to be fine. I was able to create a ...

This is a Blaze problem, but I didn't see an appropriate section in the Blaze forum so I'm posting it here.

I'm getting really bad PDF output from a project I've created by importing FrameMaker files. The spacing between characters is way off - it almost looks like Blaze is inserting a thin space ...