When saving as 2017 from directly from FrameMaker2019 to 2017 everything is OK.
But
saving it with Extendscript (Constants.FV_SaveFmtBinary140) doesn't work. Of
course
the created file can not be opened by FM-14 (2017).
Discovered by Klaus Göbel.
with Constants.FV_SaveFmtBinary140 I get a hea
"This is the 1.0 release of that code. Give them six months or a year to get
the bugs out and address limitations."
Absolutely. However, it will then be six months or a year before I upgrade. I'm
not about to give them money on faith that it might be fixed, as in its current
form it's unusable
Hi Caroline,
I am not sure without seeing the characters. You can change the default for
the clipboard in the [Preferences] section of the maker.ini file:
ClipboardFormatsPriorities=FILE, MIFW, MIF, RTF, OLE 2, META, EMF, DIB, BMP,
UNICODE TEXT, TEXT
The most useful thing is to have unicode text
Hi C2,
Can you use an autonumber instead of a prefix?
Rick
Rick Quatro
Carmen Publishing Inc.
r...@frameexpert.com
585-729-6746 NEW!
-Original Message-
From: Framers On
Behalf Of cuc tu
Sent: Tuesday, September 04, 2018 8:01 PM
To: framers@lists.frameusers.com
Subject: Re: [Framers]
Thanks for that, Rick.
I suppose that could work. I think it means I would need to create new para
formats for each description element to house the 'numbering' text (the
headings are short, such as "Description:", Settings:" etc.). This seems about
as effective as using an inline text insert