MadCap Software Forums

I see the same thing. I'm adding this to my other two oddities I noticed in 2019 R2.

viewtopic.php?f=9&t=32073

I'm also noticing improper behavior in the language pop-up too. In the 2019 output, it is cropped. In 2018 the whole window displays.
Flare 2018 output: Flare 2019 output:

If I generate my HTML5 project in Flare 2019 R2, the tooltip ends up in smaller text and under the cursor.
If I generate the same HTML5 project in Flare 2018 R2, the tooltip shows properly. Looking back, it must have been OK in the earlier version of Flare 2019.
Flare 2018 R2 output:
Flare2018tip ...

SO does this mean our outputs wont look as we need them to until Adobe fixes this bug????
Adobe has already fixed the bug on August 22nd. So if you update your Adobe Acrobat Reader or Acrobat installation, you should be fine.

This isnt the case for me. I installed Adobe Acrobat Pro DC at the ...

Adobe has released the update.
it is supposed to be pushed out over time, but you can get it buy checking for updates within Acrobat.
So far so good!

That said, MadCap Flare is apparently embedding the font incorrectly. If the font were embedded correctly by Flare's PDF engine, this wouldn't be an issue. So I hope MadCap is also looking at this for a fix from their side, so if Adobe decides again at some point to strictly enforce font encoding ...

Hi,

Did you ever work out what was going on? I'm in the same boat with company specific OTF fonts embedded as CID identity-h. All was OK until the very latest Acrobat ugrade last night (2019.012.20036 - Aug 13 2019) which no longer seemed to display the fonts. The documents were the same and could ...

Bart Bogaert wrote:Which version of Acrobat Pro are you using? I cannot seem to find the 'Fix potential font problems' fix... I'm using Acrobat Pro X.
Is there a way to share this profile and fix?

Mine is Acrobat Pro DC.
This option is well hidden. I tried to detail how I got to it in the post above.

Here is a file-by-file way to get around this issue from a post by an Adobe employee on their forum. I've had to resort to this as no fix has come from Adobe and I need to get some PDFs distributed to my teams. It's apparently not just Flare PDFs that have the issue.
Open the PDF file and dismiss ...

Isleofgough wrote:Same issue for me. Everything worked until today. I contacted Dov Isaacs at Adobe and sent him the problem pdf.

I was not impressed with Mr. Isaacs' response to the problem in Adobe's forums.

Adobe tech support has requested I send them a file with this issue after I told them it would be impractical to generate every PDF file I've made using these fonts. Plus some others have started to see the issue both in Acrobat DC and Reader DC.
Fingers crossed for a quick patch from Adobe.

Has anyone else had problems with Adobe Acrobat DC? An update from Adobe installed yesterday (8/13) and now I get an error about fonts opening PDF files. These files are generated from Flare and both new and old files (that I previously could open) have this error. Other people with Reader can open ...

Yes, I'd tried all of that with no luck. It was quite frustrating.
it was Flare's support staff that came up with the answer.
Under Display Personalization, on the Colors tab is an option called "Automatically pick an accent color from my background".
As soon as I unchecked that option, the screen ...

So what I've observed is that Flare is shifting to the left when it is displayed on my monitor and not being actively used.
If I use Flare, whatever I select returns to its normal position but the remainder of the display remains offset to the left.

When I'm working in Flare, I get odd distortions on the monitor (almost like a visual stuttering) where Flare is displayed. I've got a Windows 10 machine with two monitors and it doesn't matter which monitor I use for Flare.
I can minimize Flare and then maximize it and I get a clean screen for a ...

So I found the answer by deleting parts of the document until would generate the Word file. Some of the contents of the project were imported from Framemaker.
The problem was a web link in the imported section of the file. The link for www.XYZcompany.com had www. XYZcompany.com in the HREF code ...

I have a print project. The project is several tables, each cell filled in by a snippet.
I can generate a PDF target from the project. However, when I try to generate a Word target, I get the following error message:
Build failed: startIndex cannot be larger than length of string.
Parameter name ...

I've ran into the same issue. I've submitted a bug.
I need PDF output to supplement online output from this project.
If Flare can't put out an appropriate PDF file, I will be extremely disappointed.
I was able to manually manipulate the contents of the table to make the output work. It was either ...

I've ran into the same issue. I've submitted a bug.
I need PDF output to supplement online output from this project.
If Flare can't put out an appropriate PDF file, I will be extremely disappointed.

I can't say about Flare 8 - we are still using the modified structure we began as a work around and have stopped upgrading at Flare 6. I guess that is what we are stuck with.
Since the problem was opened with MadCap support we haven't recieved a single update from them. When I inquire if it is fixed ...

I'll give my update, since I posted the original issue and the problem was never addressed within Flare. We basically redesigned the layout of our project to live within the limitations of the slower opening process. By monitoring the IIS logs, we were able to see that the "newer" versions of Flare ...

Just because it's what we have installed from an earlier time, I've been using Microsoft FrontPage 2003 for link checking.
We have a parent project with about 30 child projects under it. Some of these child projects have 6-8 child projects (grandchild projects?).
We've been frustrated because of a ...

Still waiting on notices for fixes for it in 6.0 or bugs opened 2 years ago - things that never made 7.0, wonder if it's worth pinging them to see if they are in 7.1.

I'll assume we are 0 for 4 in the bug fix department.

Don't feel bad. Issues I reported over a year ago still aren't included in 6.0 or 6.1. We spend a decent amount of time working around the issues because it seems like they really don't test with large, multi-layered projects.

Sadly, the four open issues we have reported were not fixed in Flare 6.
Time to bug support, I guess.