Use the MRG2FAP utility to convert a Documerge or Documaker AFP or Metacode file into a FAP file or a PDF file or both. You can then view and edit the FAP file using Documaker Studio. In addition to creating a FAP file, you can also create a PDF file.
The MRG2FAP utility lets you load Xerox FRM files and IMG files that are referenced in the Metacode print stream being converted. It can also produce a BPSD/Field cross-reference listing.
The system looks for the FRM and IMG files in the directory specified by the FormLib option in the MasterResource control group. If you omit this option, the system looks in the current directory.
MRG2FAPW /I /T /X /P /L /A /O /AO //VF /MF /MR /M /INI
Parameter |
Description |
/I |
Enter the name of the AFP file (include the extension) or Metacode file (omit the extension). |
/T |
Enter the file type: AFP or MET. |
/X |
Enter the name of the font cross-reference (FXR) file. Omit the extension. |
/P |
(Optional) Enter the PrtType control group in the INI file to use, such as XER. |
/L |
(Optional) Include to create a listing of the BPSD tag field names from the input file and the subsequently created FAP field names. You must specify the file name in the BPSDReport option in the MasterResource control group. |
/A |
(Optional) Include to also create a PDF file. The system uses the PDF settings in the PrtType:PDF control group. See also Adding PDF bookmarks. |
/O |
Use this parameter to specify the output FAP file name. This name can differ from the input file name. Include a path to direct the output FAP file to a specific location. Here is an example: /O=d:\output\FAPFileName |
/AO |
Use this parameter to tell the utility to only create an Adobe PDF file — no FAP file is created. If you want the PDF file to have a name that differs from the input file name, include the PDF file name. You can also include a path to direct the output FAP file to a specific location. Here is an example: /AO=d:\pdfoutput\newPDFfile |
/VF |
Include this parameter to tell the utility that the resulting PDF file should contain template fields. In PDF parlance, text fields are fields that display text, allow you to enter information, or accept multiple lines of text. In Documaker Studio these types of fields are called variable fields. Template fields look similar to text and variable fields but do not allow you to enter information. Template fields instead display the name of the variable field and if you pause your cursor over one, you will see information about the variable field, such as its name, type, length, scope, rotation, font, and locale. |
/MF |
Include this parameter to tell the utility to merge fields from a FAP file. You can specify the name of the FAP file and include a path. Here is an example: /MF=d:\source\FAPFileName Besides using /MF option, the utility also looks in the MergeFields option in the PrtType:xxx control group to determine if it should merge fields. If you omit the FAP file name, the utility uses the FAP file name you specified with the /I parameter. |
/MR |
Include this parameter to tell the utility to merge rules from a FAP file. You can specify the name of the FAP file and include a path. Here is an example: /MR=d:\source\FAPFileName If you omit the FAP file name, the utility uses the FAP file name you specified with the /I parameter. You can also do this via Documaker Studio. |
/M |
Include this parameter to tell the utility to merge both fields and rules from a FAP file. You can specify the name of the FAP file and include a path. Here is an example: /M=d:\source\FAPFileName If you omit the FAP file name, the utility uses the FAP file name you specified with the /I parameter. |
/INI |
Include this parameter if you want to specify the INI file the utility should use. For instance, you could point to a FSIUSER.INI file and if the FSIUSER.INI file referenced a FSISYS.INI file, the utility would load the FSISYS.INI file too. By default, the utility only loads the FSISYS.INI, so all necessary INI options (in the PrtType:XER and PrtType:PDF control groups) need to be in the FSISYS.INI file. |
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.