Changes between Version 2 and Version 3 of DirHierarchy

Timestamp:

Jul 30, 2007, 5:38:09 PM (17 years ago)

Author:

Nicolas

Comment:

Minor formatting

DirHierarchy

@@ -18 +18 @@
 }}}
 
-This takes a name of the input file and the absolute path of the root of the download hierarchy (typically the download_dir element from [ProjectOptions config.xml]) and returns the absolute path of the file in the hierarchy. Generally make_directory_if_needed should be set to true: this creates a fanout directory if needed to accommodate a particular file.  Secondly, your validator and assimilator should call
+This takes a name of the input file and the absolute path of the root of the download hierarchy (typically the `download_dir` element from [ProjectOptions config.xml]) and returns the absolute path of the file in the hierarchy. Generally `make_directory_if_needed` should be set to true: this creates a fanout directory if needed to accommodate a particular file.  Secondly, your validator and assimilator should call
 
 {{{
@@ -33 +33 @@
 }}}
 
-dir_hier_move moves all files from src_dir (flat) into dst_dir (hierarchical with the given fanout). dir_hier_path, given a filename, prints the full pathname of that file in the hierarchy.
+`dir_hier_move` moves all files from `src_dir` (flat) into `dst_dir` (hierarchical with the given fanout). `dir_hier_path`, given a filename, prints the full pathname of that file in the hierarchy.
 
 == Transitioning from flat to hierarchical directories ==
@@ -45 +45 @@
 
  This causes the file deleter to check both old and new locations.
- * Use dir_hier_move to move existing upload files to a hierarchy.
+ * Use `dir_hier_move` to move existing upload files to a hierarchy.
  * Start the project, and monitor everything closely for a while.