[Framers] FM 11 / FM 14 compatibility property names for the various binary doc types that start with

[Rick Quatro]

When you use values like these in your script:

Constants.FV_SaveFmtBinary

they actually represent numbers. If you download and install the latest
FrameMaker FDK (free, but not sure the URL), you can see a list of these
constants in the include/fapidefs.h file. Somewhere around line 940 or so
you will see a list of these; here are a few of the entries:

#define FV_SaveFmtBinary100			21
#define FV_SaveFmtInterchange100	22
#define FV_SaveFmtBinary110			23
#define FV_SaveFmtInterchange110	24
#define FV_SaveFmtBinary120			25
#define FV_SaveFmtInterchange120	26
#define FV_SaveFmtBinary130			27
#define FV_SaveFmtInterchange130	28
#define FV_SaveFmtBinary140			29
#define FV_SaveFmtInterchange140	30
#define FV_SaveFmtBinary150			31
#define FV_SaveFmtInterchange150	32

You can use the raw numbers in your script, but the human-readable constants
are better. Of course after FrameMaker 12, the internal version numbers
don't match the marketing version numbers.

FrameMaker 2015 = 130 (in other areas 13)
FrameMaker 2017 = 140 (in other areas 14)
FrameMaker 2019 = 150 (in other areas 15)

Rick

-----Original Message-----
From: Framers <framers-bounces+rick=rickquatro.com at lists.frameusers.com> On
Behalf Of Lin Sims
Sent: Friday, November 30, 2018 11:12 AM
To: Frame Users <framers at lists.frameusers.com>
Subject: Re: [Framers] FM 11 / FM 14 compatibility property names for the
various binary doc types that start with

Interesting. The script I have, which was created by a former coworker who
adapted it from something Rick used in his ExtendScript class, does not seem
to have any mention of the value pairing Craig mentions. It does work,
though. I have not tried to update it for FM12, FM13, or FM14, though.

(NB: not a scripter. my updates consist of copying blocks of code and
pasting them with things like  Constants.FV_SaveFmtBinary changed to what I
assume the new numbers are. I freely admit this may not be the best or right
way to do this, but FM seems to recognize the files saved to an earlier
format as being IN that earlier format when I try to open them in the later
version.)

On Fri, Nov 30, 2018 at 11:01 AM Craig Ede <craigede at hotmail.com> wrote:

> I agree. But the values to pair those properties with are an open 
> question (though trial and error might suss it out). The value use for 
> v6-11 changes in this fashion:
> 11,12,13,16,21,23
>
> At a guess I'd start with 25 for FM12 and 27 for FM13 and see if that 
> works.
>
> Craig
> ________________________________
> From: Framers 
> <framers-bounces+craigede=hotmail.com at lists.frameusers.com>
> on behalf of Lin Sims <ljsims.ml at gmail.com>
> Sent: Friday, November 30, 2018 9:49 AM
> To: Frame Users
> Subject: Re: [Framers] FM 11 / FM 14 compatibility property names for 
> the various binary doc types that start with
>
> If Adobe maintains its pattern, then saving to FM12 would use
> Constants.FV_SaveFmtBinary120 and FM13 would be 
> Constants.FV_SaveFmtBinary130.
>
>
>
> _______________________________________________
>
> This message is from the Framers mailing list
>
> Send messages to framers at lists.frameusers.com 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 listadmin at frameusers.com
>


--
Lin Sims
_______________________________________________

This message is from the Framers mailing list

Send messages to framers at lists.frameusers.com 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 listadmin at frameusers.com