Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to DAPS 3.1

A Migrating Existing DocBook Projects

This section provides instructions on how to migrate existing DocBook projects so that you can use DAPS for managing and publishing them.

Procedure A.1: Making DocBook Projects Compatible with DAPS
  1. If your XML files are distributed across several subdirectories, flatten the hierarchy and put all XML files directly into the xml subdirectory that is required by DAPS. See Required Directory Structure. Hosting multiple documentation projects in the same xml directory is fine as long as the file names are unique. You can put multiple MAIN files there.

  2. If you have any XIncludes or entity declaration files, also put them into the xml subdirectory.

  3. Depending on the file type of your source images, add them to the respective subdirectories in YOUR_DOC_DIR/images/src. The image directory and its substructure is required by DAPS. For details, refer to Required Directory Structure.

  4. Make sure that the base names of your image files are unique. For details, refer to Section 5.3, “File Name Requirements”.

  5. Adjust all references of image files, XIncludes, and entity declarations, in the existing XML files to match the structure required by DAPS. The references must not include any absolute or relative path, the plain file name is enough.

  6. Create a Doc Config file for each deliverable (book, article, set) that you want to generate from your XML files. For more information, refer to Section 2.6, “Key Files”. Find a template for DC files in your installed system in /usr/share/daps/init_templates/DC-file.template.

Print this page