Changeset 526 for trunk


Ignore:
Timestamp:
Dec 25, 2007, 4:37:57 AM (14 years ago)
Author:
Peter Johansson
Message:

added paragraph on file-name-dictionary plus some minor changes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/readme.txt

    r525 r526  
    3939''other''.
    4040
    41 From svndigest 0.7, it is possible to set the configuration file which
    42 rules are used for different files. For more on how to configure
    43 svndigest see below. If no configuration file is given or no rules are
    44 given, a set of default rules are used. For files named `*.h`, for
    45 example, rules allowing to detect comments as either `// ... \n` or
    46 `/* ... */`. These rules can be set in the configuration file using a
     41From svndigest 0.7, it is possible to configure which rules are used
     42for different files. For more on how to configure svndigest see
     43below. If no configuration file is given or no rules are given, a set
     44of default rules are used. For files named `*.h`, for example, rules
     45allowing to detect comments as either `// ... \n` or `/*
     46... */`. These rules can be set in the configuration file using a
    4747one-liner like:
    4848
     
    5959can be found in directory `.svndigest`, and the svndigest screenshots
    6060that can be reached through http://trac.thep.lu.se/svndigest/.
     61
     62Sometimes it might be useful if a file could be parsed as though it
     63was going under a different name. It could, for example, be useful if
     64files named `Makefile.in` could be parsed as `Makefile` or files named
     65`test_repo.sh.in` could be parsed as though it was named
     66`test_repo.sh`. More generally, it would be useful if files named
     67`<file-name-pattern>.in` could be parsed as though it was named
     68`<file-name-pattern>`. For this reason it is possible to set rules on
     69how a filename should be interpreted (see section
     70[file-name-dictionary] in configuration file). Default behaviour is
     71that there is only one such a rule in use, namely the one described
     72above that trailing `.in` in file names are discarded.
     73
    6174
    6275== Different file types ==
Note: See TracChangeset for help on using the changeset viewer.