[Framers] Problems with cut off equations

[Sheila Loring]

Peter, I thought it might be related to the display resolution or graphics
card on each writer's computer. But I tried shrinkwrapping the equations on
one computer, and that didn't help either.

Robert, I've worked extensively with WebWorks on this problem. Here's what
tech support wrote: It sounds like that on your system, the fonts being
used are causing the image to be taller and the margin you have placed
around the anchored frame is not large enough to account for the increased
font size of the equation text.

It sounds like I need to add more space above and below each equation and
run the shrinkwrapping FrameScript on a single computer.

We're all on WIndows 10 but use different web browsers. I don't think it's
a browser problem though. If I look at the actual equation image that was
generated, it's cut off.

I appreciate your opinions! All ideas help.

Sheila

On Tue, May 25, 2021 at 3:38 PM <framers-request at lists.frameusers.com>
wrote:

>
> Message: 1
> Date: Tue, 25 May 2021 11:21:15 -0500
> From: Sheila Loring <sheila.loring at gmail.com>
> To: framers at lists.frameusers.com
> Subject: [Framers] Problems with cut off equations
> Message-ID:
>         <
> CAN86hRfk8B2Dw2tbxPijAAA9D4KOQutkYhENX_hO53Zu6Cu8sg at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> My team has a chronic  problem with equations in FrameMaker. They look fine
> in FrameMaker, but when converted to HTML in WebWorks ePublisher, the tops
> and/or bottoms of the equations are cut off so that you can't see the math
> symbols.
>
>
> Today I discovered that an equation looked cut off on my computer but
> looked fine on another writer's computer. But the problem can happen on
> anyone's computer.
>
>
>
> At one point, I thought the solution was to add 12 points of space around
> the equations with a FrameScript. That worked beautifully a few times. Now
> the problem is back.
>
>
> The computer I'm generating the help on has 52GB of free space and Intel(R)
> Xeon(R) Gold 6148 CPU @ 2.40GHz 2.39 GHz processors. That seems like enough
> space and processor speed so that hardware isn't an issue.
>
>
>
> Has anyone run into this problem? We're using unstructured FrameMaker 2015.
> All of the writers are using the same fonts. We've tried unshrinkwrapping
> and reshrinkwrapping. And like I said, adding 12 points of space around the
> equations (inside the frames) helped only temporarily.
>
>
> Sheila Loring
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 25 May 2021 11:31:56 -0500
> From: Peter Gold <peter at petergold.photography>
> To: "An email list for people using Adobe FrameMaker software."
>         <framers at lists.frameusers.com>
> Subject: Re: [Framers] Problems with cut off equations
> Message-ID:
>         <
> CAGoR+AhS-xzbY+V6SNjG+_WTxqKdv_zeoHbyYscerM0p5W0Rnw at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Any chance it's related to screen resolution, or a particular graphics
> card?
>
> On Tue, May 25, 2021, 11:21 AM Sheila Loring <sheila.loring at gmail.com>
> wrote:
>
> > My team has a chronic  problem with equations in FrameMaker. They look
> fine
> > in FrameMaker, but when converted to HTML in WebWorks ePublisher, the
> tops
> > and/or bottoms of the equations are cut off so that you can't see the
> math
> > symbols.
> >
> <snip>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 25 May 2021 11:58:02 -0700
> From: Robert Lauriston <robert at lauriston.com>
> To: "An email list for people using Adobe FrameMaker software."
>         <framers at lists.frameusers.com>
> Subject: Re: [Framers] Problems with cut off equations
> Message-ID:
>         <CAN3Yy4A=V2T-_=VJdA0ELf5vKFfzc9D=-
> 67JSHzWQkEqNWGimg at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> That's a bug. Have you contacted WebWorks support?
>
> When you see the problem on one computer and not on another, are they
> running the same versions of the same operating system and web
> browser? If not, it could be browser-specific, or
> browser-version-specific. But again that's a bug.
>
>