#### 4.1.5 Accommodating paths to network drives

If parts of your DITA source reside on different drives, DITA2Go cannot determine relative paths from the project directory to those parts, and must use absolute paths instead.

To direct DITA2Go to use absolute rather than relative paths:

    [Options]
    ; UseFullPath = No (default, use relative paths to project components)
    ; or Yes (always use absolute paths)
    UseFullPath = Yes

When UseFullPath=No, DITA2Go determines the relative path from the project directory to the top-level map. DITA2Go continues this process, determining the relative path from the project directory to each component, for essentially every path in the maps and topics. If the initial map is on a different drive from the drive where the project directory is located, DITA2Go cannot determine a relative path, and uses no path at all. This can cause your conversion project to fail.

When UseFullPath=Yes, you get absolute paths to images as well as to map and topic files; this means that for HTML output, references to graphics might resolve only on the original system. To get around this problem, you must either remove paths from graphics references or specify a path explicitly. (This is not an issue for RTF output, where DITA2Go embeds images in the RTF code itself when possible, or places graphics files in the same directory as the RTF files.)

To remove path information from references to images for HTML output:

    [Graphics]
    ; StripGraphPath = No (default)
    ;  or Yes (remove path from referenced graphics)
    StripGraphPath = Yes

To specify a path to graphics files for HTML output:

    [Graphics]
    ; GraphPath = path to use (replacing any previous) for all graphics
    GraphPath = path/to/graphics/files

See §32.1 Locating graphics files for HTML.

Previous Topic: 4.1.4.2 Specifying options for a generated map

Next Topic: 4.1.6 Checking output type and file extension

Parent Topic: 4.1 Specifying operating settings

Sibling Topics:

4.1.1 Connecting to XML catalogs

4.1.2 Accommodating specializations

4.1.3 Specifying a DITA XML DTD

4.1.4 Generating a map from a DITA topic file

4.1.6 Checking output type and file extension

4.1.7 Producing print output selectively

4.1.8 Including element tags and paths in output

4.1.9 Reusing or discarding ASCII DCL files

4.1.10 Specifying how to treat cases, spaces, and wildcards

Table of Contents • Index