No problem, Scott!

Any information that helps people, is good.

Z

> I hope you guys don't mind .. but I copied the useful bits from this thread 
> into
> a post on the Omsys Blog ..
> 
>      http://blog.omsys.com/2016/04/24/mif2go-and-fm-2015/
> 
> That way this info will be available to others.
> 
> If anyone would like to provide tips or other info for Mif2Go (or other Omsys
> tools), please contact me and I'll give you access to post to this blog.
> 
> Cheers,
> ...scott
> 
> On 4/24/16 1:11 PM, Syed Zaeem Hosain wrote:
> > Thanks, John.
> >
> > I will take a look …
> >
> > Regards,
> >
> > Z
> >
> > From: John Sgammato [mailto:john.sgamm...@actifio.com]
> > Sent: Sunday, April 24, 2016 06:56 AM
> > To: Syed Zaeem Hosain <syed.hos...@aeris.net>
> > Cc: framers@lists.frameusers.com
> > Subject: Re: [Framers] Mif2Go and FM 2015
> >
> > Hi Syed,
> > I have the m2rbook.dll in place.
> > The issue that I run into is a familiar one, and infuriatingly vague. It's 
> > a "could not write <file>.mif" issue.
> > I have seen this before and resolved it for FM12. I expect I can do it 
> > again when I have some time later this week or next week.
> > In case you want to research it, here's the log. The book is well-formed 
> > unstructured FM 2015, cleaned up for online use. It has just four chapters, 
> > none of them very large, and no special tricks.
> >
> > Mif2Go could not write 
> > C:\Project\ToBeProcessed\DomainManagerUsers\DMU_Security_Intro.mif
> > Mif2Go failed for file: 
> > C:\Project\ToBeProcessed\DomainManagerUsers\DMU_Security_Intro.html
> > type 5, code -43, at: Sun Apr 24 09:50:05 2016 Could not write MIF file.
> >
> > Mif2Go could not write  
> > C:\Project\ToBeProcessed\DomainManagerUsers\Users_Orgs.mif
> > Mif2Go failed for file: 
> > C:\Project\ToBeProcessed\DomainManagerUsers\Users_Orgs.html
> > type 5, code -43, at: Sun Apr 24 09:50:09 2016 Could not write MIF file.
> >
> > Mif2Go failed for file: type 6, code 0, at: Sun Apr 24 09:50:11 2016 
> > Cancelled by user.
> >
> > On Sun, Apr 24, 2016 at 2:37 AM, Syed Zaeem Hosain 
> > <syed.hos...@aeris.net<mailto:syed.hos...@aeris.net>> wrote:
> > Okay, I did a little digging in the source code for m2rbook … and think his 
> > last fix (as per my earlier e-mail below) may work for FM 2015 … but am not 
> > really sure yet!
> >
> > In one file, where Jeremy checked for the FrameMaker version number 
> > returned by the Adobe FDK, he had code to do a specific check for the 
> > version of FM.
> >
> >  From what I can tell so far, the last change he made for FM 12 stopped 
> > doing an explicit check for an exact version for FM 12 and above.
> >
> > I.e., the code says “if (FrameVersion >= 12) {“ rather than the other ones 
> > that look like “if (FrameVersion == 11) {“ and “if (FrameVersion == 10) {“, 
> > etc. This variable is set by a call to the Adobe FDK and I assume that FM 
> > 2015 returns the value 13 (but this is a guess).
> >
> > This means that he was assuming, for the moment, that the next version of 
> > FrameMaker did not need any special code (he had not seen FM 2015, of 
> > course …)
> >
> > So … I think it may work. But, please try it and let me know! If it does 
> > not, I will investigate further.
> >
> > By the way, one side note: it looks like the very last release of Mif2Go 
> > will not work with versions older than FM 7 … even though Mif2Go was 
> > available for FM 5.5 and FM 6. It is possible that Jeremy took the code 
> > support for those older versions away, since nobody(?) was using them by 
> > 2013.
> >
> > Z
> >
> > From: Syed Zaeem Hosain
> > Sent: Saturday, April 23, 2016 10:43 PM
> > To: 'John Sgammato' 
> > <john.sgamm...@actifio.com<mailto:john.sgamm...@actifio.com>>
> > Cc: framers@lists.frameusers.com<mailto:framers@lists.frameusers.com>
> > Subject: RE: [Framers] Mif2Go and FM 2015
> >
> > John, that would be great, thanks!
> >
> > And just to remind people of the specifics: there is a zip file 
> > “m2rbook115.zip” in the mif2go.com<http://mif2go.com> downloads site, under 
> > “Beta Components”.
> >
> > This ZIP contains a single DLL file called “m2rbook.dll” that must replace 
> > the older one (typically in “C:\Program Files 
> > (x86)\Adobe\AdobeFrameMaker12\fminit\Plugins”) for FM 12 to work.
> >
> > I am not sure why this simple fix works yet. The code contents are 
> > essentially identical to the old one … the properties on the version number 
> > are the only difference that I can see with a byte-for-byte comparison.
> >
> > Some investigation is needed to see if this will work for FM 2015 or needs 
> > another fix. Since I am not running FM 2015, I cannot test this.
> >
> > Regards,
> >
> > Z
> >
> > From: John Sgammato [mailto:john.sgamm...@actifio.com]
> > Sent: Saturday, April 23, 2016 10:09 PM
> > To: Syed Zaeem Hosain  <syed.hos...@aeris.net<mailto:syed.hos...@aeris.net>>
> > Cc: Ben Allums <all...@webworks.com<mailto:all...@webworks.com>>;
> > framers@lists.frameusers.com<mailto:framers@lists.frameusers.com>
> > Subject: Re: [Framers] Mif2Go and FM 2015
> >
> > I've got a major release next week, but after that I will do the full test. 
> > I need Mif2Go to work with FM2015, else I'll have to save everything back 
> > to FM12 to get the content into our Salesforce knowledgebase.
> >
> > On Sun, Apr 24, 2016 at 12:16 AM, Syed Zaeem Hosain
> <syed.hos...@aeris.net<mailto:syed.hos...@aeris.net>> wrote:
> > For those of you who used Mif2Go successfully with FM 12 (with the changed 
> > file that is needed, as described on the web site), have you tried this 
> > _same_ fix with FM 2015 yet?
> >
> > Migrating from FM 11 to FM 2015 is not the issue - since FM 11 did not need 
> > that fix.
> >
> > Z
_______________________________________________

This message is from the Framers mailing list

Send messages to framers@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 listad...@frameusers.com

Reply via email to