Upgrade Woes

Jannie · Post by **Jannie** » Wed Mar 16, 2011 2:26 pm

I just upgraded to Flare 7 and need to build a target for a 422-page printed document from my project. Silly things are happening now that weren't happening before the upgrade. Something different happens each time I try to build the target.
Flare isn't able to find the Output file every single time -- the footers from the left pages disappeared -- the Title Page disappeared and had to be reinserted into the TOC from the Content folder.
Is anyone else having these types of problems before or after the upgrade?

Post by **LTinker68** » Wed Mar 16, 2011 2:31 pm

I haven't had any problems after upgrading. If you were a beta tester then you should have uninstalled the beta version before installing the release version. Other than that, did anything happen to your environment between installing v6 and installing v7? Did your permissions on your computer change, for example?

Jannie · Post by **Jannie** » Wed Mar 16, 2011 2:38 pm

Not a beta tester.
Nothing that I know about happened between Friday and Monday.
We upgraded from Flare 6.
Could the size of the doc have anything to do with it?
It takes Flare nine minutes to build the target.

Post by **LTinker68** » Thu Mar 17, 2011 8:04 am

I don't think I've built anything that large but I don't recall anyone else mentioning problems doing large builds, at least not before v7. It could be a v7 issue. Perhaps someone else out there has an equally large print output that they can build to see if they encounter the same problem.

jcollins · Post by **jcollins** » Thu Mar 17, 2011 10:08 am

I haven't been able to build a PDF target with Flare 7 either. (Our PDF User Guide is about 1200 pages/43MB.) We upgraded from 6.x to 7 last week and now I can't preview a topic with the PDF target selected, build a PDF, or print a previewed topic as a PDF. Looks like something is broken with the PDF output in Flare 7.

When I try to build the PDF target, I receive this error message: "Method not found: 'Void iTextSharp.text.pdf.PdfWRiter.SetLanguage(System.String)'."

Has anyone else seen this error or had this problem?

Jannie · Post by **Jannie** » Fri Mar 18, 2011 8:44 am

JCollins,
Thanks for your input.
Are you using Acrobat Pro X or Reader 9?

Jannie · Post by **Jannie** » Fri Mar 18, 2011 8:45 am

It's curious that others in my workgroup who upgraded are not having problems.

jcollins · Post by **jcollins** » Fri Mar 18, 2011 8:57 am

My problem was not with viewing a PDF, but in generating the output from Flare. We use Acrobat Pro.

As it turns out, the problem was that Flare was installed in the wrong folder. We're using Windows 7 now and there appears to be a permissions issue with the Flare installation files. If you do not shift + right-click the installer and select Run as Administrator, the program cannot be installed in the folder structure within the Program Files directory that the Flare installer specifies. So when we installed Flare 6.1, we didn't have any problems using Flare, even though the files were in the wrong directory. But, when we upgraded to Flare 7, the files were installed in the same directory as the Flare 6 files (instead of in a Flare 7 directory), and the Flare 6 files were overwritten. There were likely .dll files from Flare 6 that no longer applied to Flare 7, and that mucked with our ability to generate PDFs. After we uninstalled Flare 7 in the incorrect location, and ran the installer as Administrator to install Flare 7 in the correct folder, everything worked beautifully.

We worked with MadCap support to figure all this out, so great kudos to them!

RmdHill_Writer · Post by **RmdHill_Writer** » Thu Mar 24, 2011 11:38 am

I have just upgraded to Flare 7 and my PDF output is "messed up".

The spacing between lines and between characters has increased in the pdf file. Yesterday in Flare 6.1 - the output was fine, but today my 30-page document is 44 pages. I got a new laptop with Flare7 and Windows7.

I have Acrobat 8 standard - but the issues appeared even before the full version of Acrobat was installed on this laptop. I was sure that installing the full version of Acrobat would resolve the issue - but no luck!

Any suggestions?

Thanks

jcollins · Post by **jcollins** » Thu Mar 24, 2011 12:20 pm

Have you checked the Print Medium settings in your style sheet? It could be that something has gone awry there.

What was the Medium specified in your target prior to upgrading and what Medium is specified in the target now?

It could be that the PDF target is using an incorrect Medium. Perhaps something went awry when it was upgraded. For example, if your PDF target previously used the Screen Medium when the output was generated, and when you upgraded the target defaulted to the Print Medium, everything could now look different in your output.

RmdHill_Writer · Post by **RmdHill_Writer** » Thu Mar 24, 2011 12:47 pm

Thanks for trying!

StyleSheet Medium before and after is set to print.

jcollins · Post by **jcollins** » Thu Mar 24, 2011 2:24 pm

In what directory is Flare installed on your computer?

RmdHill_Writer · Post by **RmdHill_Writer** » Mon Mar 28, 2011 8:14 am

Flare is installed in:

C:\Program Files (x86)\MadCap Software\MadCap Flare V7

Post by **rob hollinger** » Mon Mar 28, 2011 9:27 am

Please check your system DPI. This can happen if your system DPI is set to larger than the default 96dpi.

RmdHill_Writer · Post by **RmdHill_Writer** » Mon Mar 28, 2011 1:07 pm

That fixed the problem - though I'm not sure why, changing the screen resolution affects the printed ouput targets.

I would never figured that one out. Thanks so much!

gmel999 · Post by **gmel999** » Thu Apr 07, 2011 1:00 pm

Hi everyone,

I am building a not-too-big project with .chm and .pdf targets in Flare 7. I just got 4 new screencaps (nice size, clear TIFF files) from a co-worker, brought them into Corel Photo, cropped them and saved them as PNGs. Now, they look fine in the .chm output, but they are less than 1/2 the size in the PDF -- and only in this one chapter. Other images are fine. Very odd! Never saw this before... The .chm output is the one customers will actually see, but I'd like to figure out what's going on with the PDF for general reference. The PDF of this project is for review and our own files. Six-inch images are reduced to 2.something in the PDF in this chapter.

Thought I would check here before contacting Tech Support. I can't see anything in the PDF target specs that would cause this.

Thanks a lot,
Mel
(M. Blank)

jcollins · Post by **jcollins** » Thu Apr 07, 2011 1:23 pm

What is the Print Size setting for the images?

Post by **SteveS** » Thu Apr 07, 2011 2:59 pm

If the images have gone from 6 inches to 2 inchies I would guess they have been resampled to 300dpi somewhere along the line.

Now you have to find where!

gmel999 · Post by **gmel999** » Fri Apr 08, 2011 6:47 am

SteveS wrote:If the images have gone from 6 inches to 2 inchies I would guess they have been resampled to 300dpi somewhere along the line.

Now you have to find where!

Thanks, SteveS - makes sense!

It could be in Corel or Flare. Now that I think more about this, I have seen this happen once in a while even w/ Flare 5 or 6. It seems to happen sometimes when I get images from a developer - TIFFs or (gasp!) BMPs and bring them into Corel for cropping and saving as PNGs to insert into a Flare project. Normally that process works fine. Maybe something is awry in the Corel conversion algorithms??

I'm going to ask one of our excellent marketing co-ops do the same conversions in PhotoShop and see if that makes a difference.

As I mentioned earlier, the PDF output isn't critical for this rush project.

TGIF all....

Mel

MadCap Software Forums

Upgrade Woes

Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes

Re: Upgrade Woes