Documentation Center

Directories and Files

To view the Contenta registry values:

Procedure

  1. In the Contenta Explorer select: Tools > Options
  2. Click on the Registry Settings tab in the Tools Options window.
  3. Open the HKEY_LOCAL_MACHINE folder by clicking on the plus sign to the left of the folder.
  4. Open the Contenta root directory folders.
  5. Open the Settings folder.
  6. Click on the Directories folder to display the registry settings (Value) in the right pane of the window.

    The following lists all subdirectories and files in the ../encaps/di directory.

    Parent DirectoryContentsDescription
    .../di

    di.pl

    digui.pl

    pcmimport.pl

    pcmimport.pm

    Dynamic Import Perl programs.
    dipaths.plUsed by DI to resolve the directory paths in the distribution files; it is executed when digui.pl is executed the first time after the install.
    ElemHide.pmUsed by DI to hide elements in the XML hierarchy from being in the Contenta hierarchy.

    Win32.pm(UNIX only)

    Found only on UNIX systems; it supports some of the Windows-y calls on the UNIX platform.

    customcallbacks.pm

    utils.pm

    Perl modules; must be copied to the custom directory—refer to the ../di/custom directory.

    The Dynamic Import (distribution) configuration files.

    Copied from/copied to

    The first time you execute DI the distribution files are copied to the files as noted in the left column.
    config.dist/digui.cfg The digui.cfg file.
    Copied from/copied to

    PCMObject.dist/PCMObjects

    The PCMObjects file.
    SliceCheck.pm

    Used when -validate argument is specified for di.pl execution.

    TokeParser.pm

    (Windows only)

    Used by SliceCheck.pm

    ../di/*.xmlDirectory where the DriveFiles are stored when you run the Split process separate from the Import process.
    ../di/Gifs *.gifDynamic Import icons.
    ../di/OmniProgs

    child.xif

    head.xif -

    headsgm.xif

    headwf.xif

    headxsd.xif -

    implied.xif

    omxerces.xmd -

    omxerces.xin -

    parent.xif

    tail.xif

    skel.xom

    skels.xom

    utf8pat.xin*

    Dynamic Import files required for OmniMark processing.

    Dynamic Import uses boiler-plate OmniMark programs and creates run-time OmniMark programs.

    Filenames containing xerces are associated with XML schema support.

    ../di/SgmlFiles

    *.htm

    *.xml

    *.sgm

    *.html

    Sample XML and SGML documents.

    schema-sample-di.dist

    sschema-sample.xsd

    schema-sample.xml

    wellformed.xml

    Filenames containing schema are associated with XML schema support.

    Sample well-formed XML file.

    ../di/Tk

    FileDialog.pm

    Pane.pm

    User interface Perl module files.
    ..\di\Entities

    imp.dtd

    *.dtd

    *.ent

    *.elm

    Sgml.dec

    .omnilib

    SGML related files; character entity files, omnilib (catalog) file, the DTD (imp.dtd) that supports the DriveFile.

    di_except.ent (not delivered)

    The entity exception list. The entities listed in the file are not protected; they are expanded.

    Do not create/use if the -protent or -nope switch is specified in the digui.pl file, or if issuing the di.pl command with the -protent or -nope switch.

    ..\di\MapFiles *.mapSample Dynamic Import map files.
    ../di/Tmp

    Used by Split process to store temporary files. Also stores the DriveFile when you run Dynamic Import as a single process by selecting: Activity > Import

    ../di/custom

    CustomCallbacks.pm

    utils.pm

    Perl modules that can be customized as required.

    These .pm modules are delivered to the ../di directory and must be copied into the custom directory for Dynamic Import to execute without error. This should take place during installation.

    If using a custom file for a specific editor, the filename may be editor-specific such as DITACustomCallbacks.pm or FrameToolCustomCallbacks.pm