Just to mention a possibility ... FrameMaker is rather intolerant of
network latency. If you are saving to any sort of networked drive (even
a Dropbox folder), try saving to a local drive.
I've had more than one client drastically reduce random FrameMaker
crashes by moving from network to local file storage.
-Alan
On 5/18/17 7:55 AM, Lin Sims wrote:
Corporate standard (and, I think, our CMS) requires use of SVGs, partially
because it lets people search for text in the graphic once the PDF is
created. Those of us not working in DITA embed graphics because (again)
it's a corporate standard based on the fact that we don't share files
across servers/directories, so referring to them is a non-starter.
Alison, that sounds like it's a "might work". I'll have to explore that.
Thanks!
And I just realized I forgot to provide what may be a very pertinent piece
of info. The crash ONLY happens when I'm saving the file as part of a "Save
all Files in Book" operation. None of the other files trigger this, and a
couple are even larger. One of my "workarounds" is to save the other files
first and then save the problem file. That will often work for a bit, but
it's a PITA not being able to use the book-based save all.
<snip>
--
Alan Houser
Group Wellesley, Inc.
Consultant and Trainer, Technical Publishing
arh on Twitter
412-450-0532
_______________________________________________
This message is from the Framers mailing list
Send messages to [email protected]
Visit the list's homepage at http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to [email protected]
