MadCap Software Forums

Oh, very elegant! Mucho thx.
Nita

Setup: Flare V4.2.1, Vista, targets PDF and WebHelp

I have created two styles for figure titles and two styles for table titles.
p.FigureTitle
p.FigureTitle_FullWidth
p.TableTitle
p.TableTitle_FullWidth

For PDF output, the page layout allows for a one-inch a "scholar's margin" at the left, and ...

Update:

I ditched the table styles (as in table stylesheets) altogether and formatted things with td and th. Unfortunately, I still have the same result in the PDF, so the issue has to do with merged cells generally, not with merged cells not playing nicely with table stylesheets.

Well, I've spent several hours now trying an experiment in a copy of my project; I'm trying to get rid of the table stylesheets and instead have been playing with tr, td, th, table styles, etc. So far, I can get my WebHelp versions of the tables to behave (though I'm working with very simple tables ...

Already did submit it as a bug much earlier today!

FIXED!

Followed Lisa's suggestion and looked into the registry. Bingo. Under HKEY_CURRENT_USER > Software > MadCap Software > Flare > CssEditor, I found a registry item (or whatever the heck such things are called) "Medium" (or maybe it was "Mediums"; sorry) defined as "authorhelp". I deleted this ...

Oooooo.... I really don't like your answer, Lisa (though I like you ). But I fear that you might be right, which is an especially bummer answer 'cause I just helped a fellow Flare user to set up table stylesheets last week...

I have logged a bug report this morning, but wanted to post this to the forum in case anyone else has seen this problem.

Setup: Flare V4.2.1, Vista

First, a little background--
I have a global project and a child project for Client A; there are two targets: PDF and WebHelp. For various reasons, I ...

This is how it is rendered in the output PDF, as well as in the Preview.

It looks just fine in the XML Editor, so this is opposite of what you've witnessed, I guess.

Is this another PDF output bug?

I'm using Flare V4.2.1, outputting to PDF and to WebHelp.

I have a table with some merged (vertically) cells. In one cell, I've got two paragraphs. The presence of the second paragraph seems to cause the merged cells to its left, when rendered in the PDF, to be ...

I'm going directly to PDF with the same wee bit of postprocessing that Lisa reports, which I do in Acrobat Pro. Although I've struggled a bit getting Flare to break pages, hyphenate, etc. correctly, I'm quite pleased with the results.

For review output (individual topics or sets of topics), I ...

PLEASE NOTE THAT WE'VE CHANGED THE DATE, TIME, AND PLACE so that more folks can attend: Wednesday, May 13, 6-8 p.m. at Panera Bread in Twelve Corners, Brighton . I'll get there by 5:30 to hold a couple tables.

If you're not already part of our mailing list, you can reach us at ...

Richard, my troubleshooting efforts have at least pinpointed the offending file. It's not a stylesheet (at least I don't think so), but it's one particular topic file. My guess now is that I've got some offending code someplace rather than it's a bug. But, ya never know!

If I discover a solution, I ...

I just started getting this error in the last half hour after doing a bunch of work with my style sheets (I've got 2).

Here's the rub:

My PDF target won't compile. At the point where it fails, it has already processed all the topics (so I can't pinpoint which one it finds to be the offending file ...

Thanks for pointing me to the other post. I'll try Lisa's suggestion and create a span tag for my inline "code" sample. But, given your experience, I'm doubtful it'll work. This might, indeed, be another buggy PDF issue.

Nita

Hi all,

I'm stumped (again!), so of course am petitioning you experts for assistance.

Tidbits first: Flare 4.2, WebHelp and PDF targets.

I have tagged some text within a paragraph with the "code" style. The only edit I've made to the "code" style is to have it be 9pt.

In the WebHelp output, all ...

Taking my lead from the gal in Dallas who started a Flare Users Group, I'd like to get one going in Rochester, NY. I'm already investigating free or inexpensive meeting places that will offer us the basics (electricity, heat, chairs, tables, plus relative quiet -- so I'm ruling out coffeeshops and ...

Thanks, Paul, for your explanation about how hyphenation works. I appreciate the time you've taken to educate me. I understand now that the "hyphenate: never" doesn't have anything to do with how Flare is breaking a compound word. Clearly, it's a bug that Flare is putting the hyphen with the second ...

Background: Using Flare V4.1 on Vista, target is PDF.

Is anyone else having problems with lines breaking badly before certain characters or after certain other characters in their PDF output?

For example, lines will break parenthetical phrases after the opening "(" or "[", so that this opening ...

Oh, Kevin, I am SO chuckling at your rant!

This morning, I moved the project back to my Vista machine. Deleted the language skin altogether. Created a new language skin and edited the context-sensitive cross-reference formats to read the way I want them to. Rebuilt my PDF. Voila... all seems fine ...

Curious development:

I moved the entire project over from my Vista desktop to my XP Pro laptop, also running Flare 4.1.30. I didn't touch a thing in the project, but simply rebuilt the PDF. The context-sensitive cross-references were perfect! They read exactly as I had originally specified in the ...

Thanks, Lisa. At least there are a few positives coming out of your reply:

1) I'm not crazy!

2) I too have caught this pretty early in my draft so I use another strategy for the time being.

The big negative, of course, is that this is hard-coded someplace!!! I so long for the day that this ...

This is a nit of a problem, but it's got me perplexed. My target is PDF. I'm using Flare 4.1.30. (I know there is a 4.1.40, but my installed 4.1.30 doesn't seem to know there is an update. When I check for updates, it tells me there are none...)

I'm trying mightly to figure out how to get rid of ...

Lisa, I'm aware of the issue with Open Type fonts so my workaround for the bad character (bad letter) spacing has been to go with the least common demoninators, Times New Roman and Arial. Since I installed the latest update, the bad spacing is somewhat better, although it still not right ...

I certainly appeciate the hard work of the tech folks...

As it turns out, I have had my Vista machine's fonts set to normal not to large all along, so I don't see how this is the culprit. Furthermore, if by an upcoming patch you mean the one issued around 12/18, I am still seeing the problem after ...