### 36.4.2 Identifying your Mif2Go project

When you specify -project myproject, the name myproject is whatever name you gave your Mif2Go project when you set it up via the Choose Project dialog (see §3.3 Creating a Mif2Go conversion project).

Note: The name myproject is not the name of your Mif2Go project file; instead, myproject is a name that is listed in your Mif2Go project file. The names of all the Mif2Go conversion projects you have set up for a given book or document are listed in a file with extension .prj, located in the same directory as the FrameMaker files. See §3.3 Creating a Mif2Go conversion project and §C.2.1 Conversion files created during set-up.

The name myproject must be present in the .prj file for the book (or document) specified on the runfm command line (or already open in FrameMaker). If myproject contains any spaces, enclose the name in quotes.

If you are updating a document using a book project (a project listed in bookname.prj), you must make sure the book is also open; see §36.4.1.2 Specifying FrameMaker file paths: runfm -book, -doc options. When you specify a value for -doc (even if you also specify a value for -book), runfm first looks for docname.prj, in whatever directory you specified in the absolute path to docname.fm. If there is no docname.prj file in the specified directory, and a book is open in FrameMaker, runfm looks for bookname.prj. If this search also fails, runfm looks for a file named mif2go.prj.

The -project option is required to run Mif2Go. If you omit this option, runfm merely opens FrameMaker and any book or document specified, then stops. This can be a useful feature, if you frequently start FrameMaker with the same book and document for editing or testing. You could even create a desktop shortcut to use runfm this way.

See also:

§3.3 Creating a Mif2Go conversion project

§36.4.1.2 Specifying FrameMaker file paths: runfm -book, -doc options

§C.2.1 Conversion files created during set-up

| 36.4.1.3 Using FrameMaker remotely: runfm -remote option |  | 36.4.3 Configuring runfm output |