[Framers] Now it's a buggy SVG IMPORT into Frame 2019 files

[Lin Sims]

Some days, it just doesn't pay to get out of bed.

Importing the Visio files using File > Import > File gets the image in
without the weirdnesses happening with the lines.

But importing the file, even if specified as import by reference, is
importing by copy with a link to the Visio file, so yes, it updates if the
Visio source is changed, but the FrameMaker file size is increased
DRASTICALLY.

I am so FRUSTRATED, I'm about to go back to the FrameMaker 2017
installation and tell my co-worker we'll just wait for the next 6 months or
so and see if SVG issues (2 now!) get fixed.

On Fri, Oct 19, 2018 at 4:01 PM Lin Sims <ljsims.ml at gmail.com> wrote:

> If it's not one thing, it's another.
>
> I'm still on Windows 7, so I've continued importing my images into Frame
> 2017 as SVG files since I have no issues creating PDFs from them.
>
> But we've JUST upgraded to Frame 2019, and now the IMPORT of SVG images
> into Frame has gone screwy. In this case, the images are screenshots taken
> with SnagIt, pasted into Visio where graphic callouts and a text box
> containing the graphic's number is added, and exported to SVG.
>
> When the resulting SVG is imported into FrameMaker, all the callouts and
> the graphic's number MOVE, either to the right (in the case of the
> callouts) or to the left (in the case of the text box containing the
> graphic's number).
>
> For now, I'm giving up on SVGs and we're just going to import Visio files,
> since that doesn't appear to have any problems. I have non-proprietary
> examples of the issue (as JPG images) for those interested in a look. I'm
> not attaching them because I can't remember if the list software scrapes
> attachments off or not. I've also posted a query in the Adobe FrameMaker
> forum. I'm still debating whether to file a bug report. <sigh>.
>
> Weekend, here I come.
>
> --
> Lin Sims
>


-- 
Lin Sims