Best practices for converting FM to Robohelp

[Jeff Coatsworth]

Yes, I could do that too, but then I’d have to run it in reverse if FM ran into trouble and it needed one of those “extra” files to recover/restore from – FM needs the smarts to be able to know where they’re located and retrieve from that location when needed, which it’s currently lacking. Break out the wish list ;>)

From: Keith Soltys [mailto:keith.soltys at tmx.com]
Sent: September-05-14 8:48 AM
To: Jeff Coatsworth
Subject: RE: Best practices for converting FM to Robohelp

I run a batch file at least at the end of every day to move my backup files into their own directory.  I could probably automate this with ExtendScript, if I had the time to figure it out. But a batch file is simple, and it works (as long as I remember to run it).

Regards,
Keith



From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at lists.frameusers.com> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Jeff Coatsworth
Sent: Friday, September 05, 2014 8:37 AM
To: framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
Subject: RE: Best practices for converting FM to Robohelp

They probably weren’t corrupted at all – you just had selected the backup instead of the “live” copy when you opened up the next file (and then your workflow just perpetuated the mistake). One longstanding FM grumble is the program’s desire to always maintain all its files (.book, .fm, .backup, .lck, .auto, etc.) in one location – you can never designate another place to keep those “extra” file types out of the way.

From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at lists.frameusers.com> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Apurva Bahadur
Sent: September-05-14 5:50 AM
To: framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
Subject: Re: Best practices for converting FM to Robohelp

Fellow Framers,
Problem solved after some investigation, although I cannot understand the entire process.
Problem

·         While editing, I created the various FM files by renaming and saving the complete file as the next file, deleting the existing stuff and editing new content on the page.
·         Somewhere in the process, one FM file got corrupted and ended with the extension '.backup' instead of '.fm.'
·         Due to 'save as' process, all the subsequent files had the '.backup' extension.
·         Even on corruption, these .backup extension files were visible in the FM book. I could open, edit and create perfect pdf outputs of the FM book.
·         However, Robohelp refused to recognize the files with .backup extension and made a CHM containing only the files with proper .fm extension.
·         This resulted in an incomplete CHM, and a growing sense of helpless panic...
Solution
·         I opened the corrupted files from within FM book and saved them by a different name. I checked in the Windows explored that the copy of the files were saved with the proper .fm extension.
·         I added the renamed files to the book and deleted the corrupted files from the book.That was all to it.
I couldn't have solved this problem from within Framemaker itself as the book showed the corrupted files as normal FM files - I would open edit and save them without any indication of an error. So, when black magic starts to happen, please check the extensions of files in Windows explorer!

Any idea why FM book could open a file with .backup extension?  Probably .backup are valid FM files, as these display a smaller version of the Framemaker icon in the Windows explorer.

Regards,

Apurva



NOTICE OF CONFIDENTIALITY This e-mail, including all materials contained in or attached to this e-mail, contains proprietary and confidential information solely for the internal use of the intended recipient. If you have received this email in error, please notify us immediately by return e-mail or otherwise and ensure that it is permanently deleted from your systems, and do not print, copy, distribute or read its contents.

AVIS DE CONFIDENTIALITÉ Le présent courriel, y compris tous les documents qu'il contient ou qui y sont joints, renferme des renseignements exclusifs et confidentiels destinés uniquement à l'usage interne du destinataire prévu. Si vous avez reçu le présent courriel par erreur, veuillez nous aviser immédiatement, notamment par retour de courriel, et vous assurer qu'il est supprimé de façon permanente de vos systèmes; veuillez également vous abstenir d'imprimer, de copier, de distribuer ou de lire son contenu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20140905/75282dae/attachment.htm>