.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.42)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "arename 1"
.TH arename 1 "2022-02-26" "perl v5.34.0" "User Contributed Perl Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
arename \- automatically rename audio files by tagging information
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
arename [\s-1OPTION\s0(s)] \s-1FILE\s0(s)...
.SH "OPTIONS AND ARGUMENTS"
.IX Header "OPTIONS AND ARGUMENTS"
.IP "\fB\-\-ambiguous\-use\-first\fR" 8
.IX Item "--ambiguous-use-first"
Sets the \fIambiguoususefirst\fR option. See below for details.
.IP "\fB\-\-compare\-versions\fR" 8
.IX Item "--compare-versions"
Prints the version of the arename script and the version of the Perl module,
that contains most of the code. These versions should be the same. If not,
that would indicate a possibly broken installation.
.IP "\fB\-\-copy\fR (short option: \fB\-c\fR)" 8
.IX Item "--copy (short option: -c)"
Copy files instead of renaming (moving). This can be useful to copy tracks
from your audio archive to a portable device for example.
.IP "\fB\-\-debug\fR" 8
.IX Item "--debug"
Enable debugging output. This actually sets `\fIverbosity\fR' to 10000. This output
option will cause very noisy output. You probably want something less verbose,
like `\fI\-\-verbosity 20\fR'.
.IP "\fB\-\-disable\-hooks\fR (short option: \fB\-H\fR)" 8
.IX Item "--disable-hooks (short option: -H)"
Do not make use of hooks of any sort (neither global nor local ones).
.IP "\fB\-\-disable\-profiles\fR (short option: \fB\-N\fR)" 8
.IX Item "--disable-profiles (short option: -N)"
Do \fInot\fR use configuration profiles (see below).
Overwrites the \fBuseprofiles\fR setting.
.IP "\fB\-\-dryrun\fR (short option: \fB\-d\fR)" 8
.IX Item "--dryrun (short option: -d)"
Go into dryrun mode. This means, that no action will be taken. \fBarename\fR
will print what it would do, if called without \fI\-d\fR.
.IP "\fB\-\-enable\-hooks\fR" 8
.IX Item "--enable-hooks"
Explicitly enable hooks.
.IP "\fB\-\-force\fR (short option: \fB\-f\fR)" 8
.IX Item "--force (short option: -f)"
Overwrite files if needed.
.IP "\fB\-\-help\fR (short option: \fB\-h\fR)" 8
.IX Item "--help (short option: -h)"
Display a short help text.
.IP "\fB\-\-list\-cfg\fR (short option: \fB\-L\fR)" 8
.IX Item "--list-cfg (short option: -L)"
List the current configuration in the actual configuration format.
.IP "\fB\-\-list\-file\-types\fR" 8
.IX Item "--list-file-types"
Lists all file types currently supported by \fBarename\fR, one type
per line.
.IP "\fB\-\-list\-exts\-for\-type\fR <type[,type[,...]]>" 8
.IX Item "--list-exts-for-type <type[,type[,...]]>"
Lists all extensions recognised file name extsionsion for type
\&\fB<type>\fR, one extension per line. If a list of types is given
as a comma-separated list, extensions for all listed types are listed.
.IP "\fB\-\-list\-profiles\fR (short option: \fB\-S\fR)" 8
.IX Item "--list-profiles (short option: -S)"
Print a list of profile names defined in the active configuration.
(This is primarily used by the zsh completion for the \fI\-\-profile\fR option.)
.IP "\fB\-\-read\-local\fR (short option: \fB\-l\fR)" 8
.IX Item "--read-local (short option: -l)"
Read a local config file (./.arename.local). Overwrites the \fBuselocalrc\fR
configuration setting.
.IP "\fB\-\-stdin\fR (short option: \fB\-s\fR)" 8
.IX Item "--stdin (short option: -s)"
Read filenames from stdin after processing files given on the command line.
It reads one file name per line, which means that file names containing
newlines are not supported.
.IP "\fB\-\-version\fR (short option: \fB\-V\fR)" 8
.IX Item "--version (short option: -V)"
Display version information.
.IP "\fB\-\-verbosity\fR <integer\-value>" 8
.IX Item "--verbosity <integer-value>"
Sets the `\fIverbosity\fR' setting to `\fIinteger-value\fR'.
.IP "\fB\-\-suppress\-skips\fR (short option: \fB\-Q\fR)" 8
.IX Item "--suppress-skips (short option: -Q)"
When a file is skipped, because its name would not change, this option will
cause \fBarename\fR to suppress any output. This sets the `suppress_skips' option.
.Sp
Note that if the `\fIverbosity\fR' setting is at a high enough level, you may
still get messages about the file being processed in the first place.
.IP "\fB\-\-rc\fR <file>" 8
.IX Item "--rc <file>"
Read \fIfile\fR instead of ~/.arenamerc.
.IP "\fB\-\-post\-rc\fR <file>" 8
.IX Item "--post-rc <file>"
Read \fIfile\fR \fBafter\fR ~/.arenamerc and \fBbefore\fR ./.arename.local.
.IP "\fB\-\-prefix\fR <prefix> (short option: \fB\-p\fR)" 8
.IX Item "--prefix <prefix> (short option: -p)"
Define a prefix for destination files.
.IP "\fB\-\-profile\fR <profile(s),...> (short option: \fB\-P\fR)" 8
.IX Item "--profile <profile(s),...> (short option: -P)"
Define a list of one or more profiles to use forcibly, no matter if they
would be activated normally or not.
.IP "\fB\-\-compilation\-template\fR <template> (short option: \fB\-T\fR)" 8
.IX Item "--compilation-template <template> (short option: -T)"
Define a template, that will be used for files that contain a compilation
tag.
.IP "\fB\-\-template\fR <template> (short option: \fB\-t\fR)" 8
.IX Item "--template <template> (short option: -t)"
Define a generic template (for all files that do \fInot\fR contain a
compilation tag).
.IP "\fB\-\-userset\fR <\fIvariable\fR=\fIvalue\fR> (short option: \fB\-u\fR)" 8
.IX Item "--userset <variable=value> (short option: -u)"
Set a user defined variable to a given value (see
\&\*(L"User defined variables\*(R" below).
.IP "\fI\s-1FILE\s0(s)...\fR" 8
.IX Item "FILE(s)..."
Input files, that are subject for renaming.
.PP
A word about option name stability: With \fIarename version 3.0\fR we are now
using Getopt::Long for parsing command lines options. That change was made,
because the meaningful single letter options where used up. Every option is
available via a \fI\-\-long\-option\fR. \fBThat interface will remain stable\fR. If
changes to the \fI\-\-long\-option\fR interface are done, that will happen with an
appropriate deprecation phase, so users can adjust. So, if you want to use
\&\fBarename\fR in scripts, those are the options you should use. There are
currently no plans of removing or changing any further short options, but there
are no guarantees. If it is indeed better to change a short option, we will do
so.
.PP
A list of options that changed from \fBarename\fR \fI3.x\fR to \fI4.0\fR can be found in
the project's \s-1CHANGES\s0 file and general advice about incompatible changes from
major version to major version are documented in the \s-1UPGRADING\s0 file.
.SS "Deprecated Command Line Options"
.IX Subsection "Deprecated Command Line Options"
The following options are deprecated and will be removed in a later version of
\&\fBarename\fR.
.IP "\fB\-\-quiet\fR" 4
.IX Item "--quiet"
This option is a short hand for \*(L"\-\-verbosity 10\*(R".
.IP "\fB\-\-uber\-quiet\fR" 4
.IX Item "--uber-quiet"
This option is a short hand for \*(L"\-\-verbosity 5\*(R".
.IP "\fB\-\-verbose\fR" 4
.IX Item "--verbose"
This is a short hand for \*(L"\-\-verbosity 20\*(R".
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
\&\fBarename\fR is a tool that is able to rename audio files by looking at
a file's tagging information. It uses this information to assemble a
consistent destination file name. The user can define the format of the
destination filename by the use of template strings.
.PP
Templates can be defined in the \*(L"Configuration files\*(R", by the
\&\fItemplate\fR and \fIcomp_template\fR settings (See \*(L"\s-1SETTINGS\*(R"\s0 below).
.PP
By default, \fBarename\fR will refuse to overwrite destination files,
if the file in question already exists. You can force overwriting by
supplying the \fB\-\-force\fR option.
.PP
In order to see what would happen instead of actually modifying files, you
can use the \fB\-\-dryrun\fR option. This way you can avoid problems, that would
occur if the situation (e.g. the information in the files or your
configuration) is not exactly as you expected it.
.SS "Supported file formats"
.IX Subsection "Supported file formats"
Since version 4.0, \fBarename\fR supports a lot more file formats than it
used to (version 3.0 only supported \fI.mp3\fR, \fI.ogg\fR and \fI.flac\fR
files). Thanks to Audio::Scan, we now support a much wider range of
file types, of which most may exist using different file name
extensions (e.g. \fI*.ogg\fR and \fI*.oga\fR are both of the type \fIogg\fR).
.PP
You may use the `\fI\-\-list\-file\-types\fR' and `\fI\-\-list\-ext\-for\-type\fR'
options to find out which file type is mapped to which file name
extensions.
.PP
If you would like support for another file type in \fBarename\fR, you
will have to persuade the Audio::Scan developers to extend their
module with said feature. Adding support for it in \fBarename\fR after
that should be trivial.
.PP
To give you an idea, arename (in connection with Audio::Scan \fB0.85\fR)
lets you rename \fImp3\fR, \fImp4\fR, \fIaac\fR, \fIogg\fR, \fIflac\fR, \fIasf\fR,
\&\fImusepack\fR, \fImonkey audio\fR, \fIwav\fR (this type also supports \fIaiff\fR)
and \fIwavpack\fR files.
.SS "Inputting a *lot* of files"
.IX Subsection "Inputting a *lot* of files"
\&\fBarename\fR can be used to keep the file names of whole audio archives in
sync. However, that means that you will have to tell the script the
location of many files, thousands maybe.
.PP
In order to do that you will face the problem, that on most UNIX-like
systems, the length of the argument list for external programs is limited
(recent Linux versions, as an exception, do not have that limitation
anymore).
.PP
So, even if your shell can do recursive globbing like ksh or zsh, this will
most likely get you into trouble (for more than just a few files):
.PP
.Vb 1
\&  % arename \-d **/*.mp3
.Ve
.PP
There are several ways to overcome that limitation, of course.
.PP
The first solution is to use \fBfind\fR in connection with \fBarename\fR's \fI\-s\fR
option:
.PP
.Vb 1
\&  % find . \-name "*.mp3" \-print | arename \-d \-s
.Ve
.PP
This will break for file names that contain newlines, because \fI\-\-stdin\fR will
read one file name per line from the standard input stream.
.PP
Another way of using \fBfind\fR to deal with this problem is to use find's
\&\fI\-exec\fR option:
.PP
.Vb 1
\&  % find . \-name "*.mp3" \-exec arename \-d \*(Aq{}\*(Aq \*(Aq+\*(Aq
.Ve
.PP
This will work for every possible file name. No matter if it has spaces
or newlines in it. The \fI+\fR at the end of the call causes find to call
the external program (\fBarename\fR in this case) with as many arguments as
possible, without exceeding the limit. This requires a POSIXly correct
find. \s-1GNU\s0 find for instance, did not support the \fI+\fR way for a long time.
If you are stuck with an old version, you can exchange the \fI+\fR with a
\&\fI;\fR (note, that a semicolon \fBmust\fR be quoted in any case), or use the
xargs tool instead.
.PP
A last solution for zsh users would be zargs (which requires
\&'autoload zargs' in your zsh configuration):
.PP
.Vb 1
\&  % zargs \-\- **/*.mp3 \-\- arename \-d
.Ve
.SH "GENERAL USAGE"
.IX Header "GENERAL USAGE"
When you are first confronted with \fBarename\fR and you try to get started
with the documentation you might argue, that a 1000+ lines manual, that
is not filled with too many examples is hardly starter-friendly.
.PP
Therefore, this section was introduced to give you the bare minimum of
information in order to use the program without going through too much
fuzz.
.PP
If you are really afraid of documentation, you could of course just read
the output of the \fI\-\-help\fR option and see which options to provide in order
to get what you want. Then again, you will soon be pissed by the weird
default values \fBarename\fR uses.
.PP
You will probably want other templates. After all, the ability to have
these expanded strings is one of the points to use \fBarename\fR in the first
place. They are described in the \s-1TEMPLATE\s0 section; and reading that
section is the minimum effort you will want to go through.
.PP
After that, you can open the file \fI~/.arenamerc\fR in your favourite
text editor and resemble the following text (and presumably change the
few values in there to your liking):
.PP
.Vb 3
\&  # now you certainly want your own templates, so define them here
\&  # one for your normal files
\&  template &artist \- &album \- &tracknumber. &tracktitle
\&
\&  # and another one for files that orignate from compilations
\&  comp_template va \- &album \- &tracknumber. &artist \- &tracktitle
.Ve
.PP
If you want more automation or more customization, you will not get
around reading the manual below. If you need to solve special
problems, the \*(L"\s-1HOOKS\*(R"\s0 part even further below is for you.
.SH "ENVIRONMENT VARIABLES"
.IX Header "ENVIRONMENT VARIABLES"
.IP "\fB\s-1ARENAME_LOAD_QUIET\s0\fR" 8
.IX Item "ARENAME_LOAD_QUIET"
When set to \fI1\fR, \fBarename\fR will not output any startup messages; not
while reading the configuration or hook files, nor will \fBarename\fR emit
messages about whether it is in copy mode or on a dry-run or similar.
.Sp
However, if warnings or errors are encoutered while loading the
configuration, those messages are still emitted, of course.
.Sp
Any other value but \fI1\fR \- and that includes \s-1ARENAME_LOAD_QUIET\s0 being
absent from the environment \- will cause \fBarename\fR to start up in
its normal manner.
.IP "\fB\s-1ARENAME_SUPPRESS_COLOURS\s0\fR" 8
.IX Item "ARENAME_SUPPRESS_COLOURS"
When set to \fI1\fR (and only 1 \- \fBarename\fR will ignore any other setting),
arename will turn off its output colourations. As of version 4.0, \fBarename\fR
uses Term::ANSIColor to produce output, that features terminal colours.
.SH "FILES"
.IX Header "FILES"
\&\fBarename\fR's behaviour can be altered by a number of files it reads when
starting up.
.PP
Normal configuration tasks are done in (how convenient)
\&\*(L"Configuration files\*(R", described below.
.PP
If you need more control, or want to solve special problems you are having,
you can do so by supplying Perl code in \*(L"Hook definition files\*(R".
.PP
\&\fBarename\fR can be configured to read configuration files as well as hook
definition files from the current working directory. This feature is
disabled by default, because they can be a security issue on multiuser
systems.
.PP
There are no such things as system wide configuration files in \fBarename\fR.
.PP
For all setup files \fBarename\fR tries to find (except for the local ones)
four different locations are tried. If the \fI\f(CI$XDG_CONFIG_HOME\fI/arename\fR
directory exists, \fBall\fR files are expected to be there. If that directory
does not exist, \fI~/etc/arename/\fR and if that is not there \fI~/.arename\fR are
are tried instead. If those directories could not be found either, \fBarename\fR
will try to find the file it is looking for directly in the user's home
directory.
.PP
The default for \fI\f(CI$XDG_CONFIG_HOME\fI\fR is \fI~/.config\fR.
.PP
The first setup directory we find always wins. \fBarename\fR does not consider
more than one setup directory.
.PP
If, for example, \fI~/etc/arename/\fR exists and we are looking for the normal
configuration file (see below), but
\&\fI~/etc/arename/rc\fR could not be found, we do \fBnot\fR try to find it in
\&\fI~/.arename/\fR or the user's home directory.
.SS "Configuration files"
.IX Subsection "Configuration files"
\&\fBarename\fR uses up to three configuration files. As for most programs,
the script will try to read a configuration file, that is located in the
user's \fIhome directory\fR. In addition to that, it will try to load \fIlocal\fR
configuration files, if it finds appropriately named files in the
\&\fIcurrent directory\fR (and the \fIuselocalrc\fR feature is enabled):
.IP "\fB\f(CB$XDG_CONFIG_HOME\fB/arename/rc\fR" 8
.IX Item "$XDG_CONFIG_HOME/arename/rc"
.PD 0
.IP "\fB~/etc/arename/rc\fR" 8
.IX Item "~/etc/arename/rc"
.IP "\fB~/.arename/rc\fR" 8
.IX Item "~/.arename/rc"
.IP "\fB~/.arenamerc\fR" 8
.IX Item "~/.arenamerc"
.PD
per-user normal configuration file.
.IP "\fB./.arename.local\fR" 8
.IX Item "./.arename.local"
per-directory local configuration file (only read if \fIuselocalrc\fR is set
or the \fI\-\-read\-local\fR option is given on the command line).
.PP
The per-user normal configuration file can be substituted by another file,
if specified via the \fI\-\-rc\fR option.
.PP
Last but not least, you can specify an intermediate configuration file,
that is read in between the normal and the per-directory file, via the
\&\fI\-\-post\-rc\fR option.
.PP
\fIFile format\fR
.IX Subsection "File format"
.PP
The format of the aforementioned files is pretty simple.
It is parsed line by line. Empty lines, lines only containing whitespace
and lines, whose first non whitespace character is a hash character (\fI#\fR)
are ignored.
.PP
There are two different types of settings: boolean and scalar settings.
.PP
Booleans can be set like this:
.PP
.Vb 1
\&  <setting> [true|false]
.Ve
.PP
If the value is omitted, \fItrue\fR is assumed. \fItrue\fR and \fIfalse\fR are
recognized case insensitively, and a value of \fI1\fR is synonymous to \fItrue\fR,
as is \fI0\fR to \fIfalse\fR.
.PP
Scalar settings are done in a very similar way:
.PP
.Vb 1
\&  <setting> <value>
.Ve
.PP
If the value is omitted, string values will be set to an empty string and
numeric values will be set to zero.
.PP
In both cases, setting and value are separated by one or more whitespace
characters. The value will be the rest of the line (all of it, including
trailing whitespace).
.PP
If the value part starts with a backslash, that backslash is left out of the
value. That makes it possible to define templates with leading whitespace.
.PP
If a line contains only a string within square brackets, that string is the
start of a section. Section names are matches for starts of file names.
That means, the settings following such a section definition will only
applied for input file names that start with the same string as the section
name. Where file name means the string, handed over to \fBarename\fR. The string
\&\fI~/\fR at the beginning of a section name is expanded to the user's home
directory.
.PP
You may start as many sections as you would like.
.PP
A section named \fI/foo/bar/\fR supersedes a section named \fI/foo/\fR for a file
named \fI/foo/bar/baz.ogg\fR. So, the longest match wins.
.PP
Another possible configuration file entry is a user variable, which is
defined via the \fBset\fR command. These settings are very different from the
normal settings. Therefore, they are defined in a different way. That way
is described in the \*(L"User defined variables\*(R" subsection below.
.PP
Last but not least, you may define so called
profiles, see below.
.PP
\fIConfiguration profiles\fR
.IX Subsection "Configuration profiles"
.PP
Profiles are a very flexible and context sensitive way of using multiple
configuration files at once. With profiles, local configuration files (and
local hook definition files) can be substituted in a secure way; even on
multi-user systems.
.PP
Reading local files (configs and hook-files) is still supported for backwards
compatibility (see \fIuselocalrc\fR and \fIuselocalhooks\fR options).
However, you are strongly encouraged to use profiles whenever you can.
.PP
As normal configuration files and global hook-files, profile-related files are
searched in one of the setup directories described above. They are using the
following naming conventions:
.IP "\fB\f(CB$XDG_CONFIG_HOME\fB/arename/profile.PROFILENAME\fR" 8
.IX Item "$XDG_CONFIG_HOME/arename/profile.PROFILENAME"
.PD 0
.IP "\fB~/etc/arename/profile.PROFILENAME\fR" 8
.IX Item "~/etc/arename/profile.PROFILENAME"
.IP "\fB~/.arename/profile.PROFILENAME\fR" 8
.IX Item "~/.arename/profile.PROFILENAME"
.IP "\fB~/.arename.PROFILENAME\fR" 8
.IX Item "~/.arename.PROFILENAME"
.PD
Profile related configuration files; read if \fI\s-1PROFILENAME\s0\fR is active.
.Sp
They are read after a intermediate config file defined by \fI\-\-post\-rc\fR and
a local config file (if enabled).
.IP "\fB\f(CB$XDG_CONFIG_HOME\fB/arename/profile.PROFILENAME.hooks\fR" 8
.IX Item "$XDG_CONFIG_HOME/arename/profile.PROFILENAME.hooks"
.PD 0
.IP "\fB~/etc/arename/profile.PROFILENAME.hooks\fR" 8
.IX Item "~/etc/arename/profile.PROFILENAME.hooks"
.IP "\fB~/.arename/profile.PROFILENAME.hooks\fR" 8
.IX Item "~/.arename/profile.PROFILENAME.hooks"
.IP "\fB~/.arename.PROFILENAME.hooks\fR" 8
.IX Item "~/.arename.PROFILENAME.hooks"
.PD
Profile related \*(L"Hook definition files\*(R" (see below for details); read if
\&\fI\s-1PROFILENAME\s0\fR is active.
.Sp
These files are read, between global and local hook-definition files.
.PP
In order to define profiles, you need to use the \fIprofile\fR keyword:
.PP
.Vb 1
\&  profile <name> <pattern>
.Ve
.PP
Where \fIname\fR is a string, that is used in the place of \fB\s-1PROFILENAME\s0\fR
in the file location lists above. This name may contain of the following
character range: \fBa\-zA\-Z0\-9_\-\fR
.PP
\&\fIpattern\fR is part of a Perl regex pattern (see \fIperlreref\fR and \fIperlretut\fR
manpages). The pattern will be anchored at the beginning and is open at
the end, somewhat like this pseudocode:
.PP
.Vb 1
\&  if ($working_directory =~ m/^PATTERN/) { use_this_profile(); }
.Ve
.PP
Example:
.PP
.Vb 1
\&  profile music /mnt/audio/music/
.Ve
.PP
Will cause the profile \fImusic\fR to be active when the working directory is
\&\fI/mnt/audio/music/\fR or below. So, do not be afraid. You can use profiles
without understanding regular expressions.
.PP
Like many other values in \fBarename\fR's configuration, a leading backslash of
a pattern will be ignored to allow patterns, that start in white spaces.
Furthermore, if a pattern starts in \fI~/\fR, that string is replaced by the
user's home directory.
.PP
You may add as many patterns to a profile name, as you want:
.PP
.Vb 2
\&  profile music /mnt/audio/music/
\&  profile music /mnt/extern/audio/music/
.Ve
.PP
The above activates the \fImusic\fR profile in \fI/mnt/audio/music/\fR and
\&\fI/mnt/extern/audio/music/\fR, for example.
.PP
More than one profile can be activated at the same time. If that is true,
the according configuration files are read in lexical order.
.PP
\fISections versus Profiles\fR
.IX Subsection "Sections versus Profiles"
.PP
Since \fBarename\fR provides two context sensitive configuration facilities,
you might ask yourself when to use which, when you are confronted with both
for the first time.
.PP
First of all, \fIprofiles\fR are more powerful. They may even introduce new
hooks for \fBarename\fR to use. But that is not the conceptual difference
between the two.
.PP
\&\fIsections\fR are sets of configuration settings, that are considered for
\&\fBeach and every\fR input file and they are \fBonly\fR enabled for input files,
whose name matches the section name.
.PP
\&\fIprofiles\fR on the other hand are sets of configuration and hook-definition
files, whose inclusion in the current \fBarename\fR run is decided at the
\&\fBbeginning\fR of the program's execution (not for every input file) \- namely,
if the name of the current working directory matches one of the profile's
patterns.
.PP
That means, that if you need to introduce slight configuration changes based
on an \fBinput file's name\fR you want to use a \fIsection\fR.
.PP
If you need to make broader configuration changes, considering the name of
the \fBcurrent working directory\fR, \fIprofiles\fR are the way to go.
.PP
Of course, profile configuration files may introduce new sections, too.
.SS "Configuration file example"
.IX Subsection "Configuration file example"
.Vb 2
\&  # switch on verbosity
\&  verbosity 20
\&
\&  # canonicalize file names before working with them
\&  canonicalize
\&
\&  # the author is crazy! use a sane template by default. :\-)
\&  template &artist \- &album (&year) \- &tracknumber. &tracktitle
\&
\&  # activate the \*(Aqmusic\*(Aq profile below /mnt/audio/music/.
\&  profile music /mnt/audio/music/
\&
\&  # force files from /foo/bar/ to stay below that directory
\&  [/foo/bar/]
\&  prefix /foo/bar
.Ve
.SS "Hook definition files"
.IX Subsection "Hook definition files"
.IP "\fB\f(CB$XDG_CONFIG_HOME\fB/arename/hooks\fR" 4
.IX Item "$XDG_CONFIG_HOME/arename/hooks"
.PD 0
.IP "\fB~/etc/arename/hooks\fR" 4
.IX Item "~/etc/arename/hooks"
.IP "\fB~/.arename/hooks\fR" 4
.IX Item "~/.arename/hooks"
.IP "\fB~/.arename.hooks\fR" 4
.IX Item "~/.arename.hooks"
.PD
Defines global hooks, that are in effect in every directory if the \fIusehooks\fR
option is set to \fBtrue\fR.
.IP "\fB./.arename.hooks.local\fR" 4
.IX Item "./.arename.hooks.local"
This allows you to define special hooks, that will only be applied for processes
that run in the directory the local file is found (and if the \fIuselocalhooks\fR
option is set to \fBtrue\fR).
.PP
For details about hooks in \fBarename\fR, see \*(L"\s-1HOOKS\*(R"\s0 below.
.SH "SETTINGS"
.IX Header "SETTINGS"
The following settings are supported in all configuration files.
.PP
Not all of them are usable in \fIsections\fR. The ones you can use in
sections are: All \fIdefault_*\fR options, \fIforce\fR, \fIprefix\fR, \fIsepreplace\fR,
\&\fItnpad\fR, \fIcomp_template\fR and \fItemplate\fR.
.IP "\fBambiguoususefirst\fR" 8
.IX Item "ambiguoususefirst"
Some tag types support setting the sametag multiple times. The
scanning backends before arename 4.0 did not support such tags. When
this option is set to \fIfalse\fR (default), arename gives up when it
encounters such tags.
.Sp
When set to \fItrue\fR, arename just uses the first value it encounters.
.Sp
For maximum control over how tags with ambiguous values are handled,
you may use the `\fIambiguoustag\fR' hook. (default: \fIfalse\fR)
.IP "\fBcanonicalize\fR" 8
.IX Item "canonicalize"
If set, a given file name will be transformed to its cleaned up absolute
path. You may want to set this, if you are using sections in the
configuration. If you do not use sections, all this will give you is a
performance penalty. (default value: \fIfalse\fR)
.IP "\fBcheckprofilerc\fR" 8
.IX Item "checkprofilerc"
If set, \fBarename\fR will check if there is a configuration file for a
profile as soon as it reads a profile definition in the setup and \fBonly\fR
consider the profile if it found the according config file. Profiles
without config file will cause a warning if this is set, which may cause the
\&\fIdryrun\fR option to be set if the \fIwarningsautodryrun\fR option is set.
.Sp
If unset, profiles without config file will not cause warnings. You will
see messages about missing configuration files, if a profile without config
file is active. (default: \fItrue\fR)
.IP "\fBchecktemplatesinitially\fR" 8
.IX Item "checktemplatesinitially"
If set, \fBarename\fR will inspect all \fItemplate\fR and \fIcomp_template\fR
settings for possible problems. Unsetting this option probably only
makes sense, if you are working with templates within hooks and know
what you are doing. Normal users will most likely want to stick with
the default. (default: \fIon\fR)
.IP "\fBcomp_template\fR" 8
.IX Item "comp_template"
Defines a template to use with files that provide a compilation tag
(for 'various artist' CDs, for example). This setting can still be
overwritten by the \fB\-\-compilation\-template\fR command line option. (default
value: \fIva/&album/&tracknumber \- &artist \- &tracktitle\fR)
.IP "\fBdefault_*\fR" 8
.IX Item "default_*"
default_artist, default_album, default_compilation, default_genre,
default_tracknumber, default_tracktitle, default_year
.Sp
Defines a default value, for the given tag in files, that lack this
information. (default value: \fIundefined\fR)
.IP "\fBhookerrfatal\fR" 8
.IX Item "hookerrfatal"
If this is set to false, arename will continue execution even if
reading, parsing or compiling a hooks file failed. (default value:
\&\fIfalse\fR)
.IP "\fBprefix\fR" 8
.IX Item "prefix"
Defines a prefix for destination files. Setting this to '/foo/bar' results
in destination files named '/foo/bar/Expanded Template.ogg'
.Sp
This setting can still be overwritten by the \fB\-\-profile\fR command line option.
(default value: \fI.\fR)
.IP "\fBsepreplace\fR" 8
.IX Item "sepreplace"
Tagging information strings may contain slashes, which is a pretty bad
idea on most file systems. Therefore, you can define a string, that replaces
slashes with the value of this setting. (default value: \fI_\fR)
.IP "\fBsuppress_skips\fR" 8
.IX Item "suppress_skips"
Like the `\fI\-\-suppress\-skips\fR' command line option, this disables messages for
files that \fBarename\fR will skip because the file name would not change.
.IP "\fBtemplate\fR" 8
.IX Item "template"
Defines a template to use with files that do not provide a compilation tag
(or where the compilation tag and the artist tag are exactly the same).
This setting can be overwritten by the \fB\-\-compilation\-template\fR command
line option. (default value:
\&\fI&artist[1]/&artist/&album/&tracknumber \- &tracktitle\fR)
.IP "\fBtemplate_aliases\fR" 8
.IX Item "template_aliases"
If this option is set, \fBarename\fR allows the use of abbreviated taq
names in \fItemplate\fR and \fIcomp_template\fR. See \*(L"Available expression
identifiers\*(R" below for details. (default value: \fIoff\fR)
.IP "\fBtnpad\fR" 8
.IX Item "tnpad"
This defines the width, to which the track number field is padded with zeros
on the left. Setting this to zero disables padding. (default value: \fI2\fR)
.IP "\fBusehooks\fR" 8
.IX Item "usehooks"
If set to true, use hooks defined in \fB~/.arename.hooks\fR.
(default value: \fItrue\fR)
.IP "\fBuselocalhooks\fR" 8
.IX Item "uselocalhooks"
If set to true, use hooks defined in \fB./.arename.hooks.local\fR.
(default value: \fIfalse\fR)
.IP "\fBuselocalrc\fR" 8
.IX Item "uselocalrc"
If set to true, read a local configuration file (\fB./.arename.local\fR),
if it exists. (default value: \fIfalse\fR)
.IP "\fBuseprofiles\fR" 8
.IX Item "useprofiles"
If set to true, configuration profiles will be used. If false, they are not.
(default value: \fItrue\fR)
.IP "\fBusetypeasextension\fR" 8
.IX Item "usetypeasextension"
One file type may be used for different file name extensions. For
example, files matching \fI*.ogg\fR and \fI*.oga\fR will both be handled as
type \fIogg\fR in Audio::Scan (the information gathering backend,
\&\fBarename\fR is using since version 4.0).
.Sp
When this option is set to \fItrue\fR, a file matching \fI*.oga\fR would be
renamed using \fI.ogg\fR as the extension, since its type is
\&\fIogg\fR. Otherwise, the original extension is left untouched. (default:
\&\fItrue\fR)
.IP "\fBverbosity\fR" 8
.IX Item "verbosity"
Integer option, that sets the verbosity of \fIarename\fR's output. The default
value is `\fI10\fR'. The `\fI\-\-verbosity\fR' option may be used to override this
setting.
.IP "\fBwarningsautodryrun\fR" 8
.IX Item "warningsautodryrun"
Switches on the \fIdryrun\fR option (if not enabled already), as soon as the
configuration file parser encounters non-fatal warnings. This option was
introduced to avoid destructive behaviour due to incorrect lines in any
of the configuration files. (default value: \fItrue\fR)
.SS "Deprecated Settings"
.IX Subsection "Deprecated Settings"
.IP "\fBverbose\fR" 4
.IX Item "verbose"
This setting has no effect and will be removed in a later version. Use an
appropriate `\fIverbosity\fR' setting instead.
.IP "\fBquiet\fR" 4
.IX Item "quiet"
This setting has no effect and will be removed in a later version. Use an
appropriate `\fIverbosity\fR' setting instead.
.IP "\fBquiet_skip\fR" 4
.IX Item "quiet_skip"
This setting has no effect and will be removed in a later version. Use an
appropriate `\fIverbosity\fR' setting instead.
.IP "\fBdebug\fR" 4
.IX Item "debug"
This setting has no effect and will be removed in a later version. Use an
appropriate `\fIverbosity\fR' setting instead.
.SS "User defined variables"
.IX Subsection "User defined variables"
You can use the \fBset\fR command in arenamerc files. This way the user can
define his own variables. The namespace is separate from \fBarename\fR's
normal settings. (That means, you cannot, for example,  overwrite the
internal \fItemplate\fR variable with this command.)
.PP
The sytnax is quite simple (and \fBdifferent\fR to normal settings on purpose!):
.PP
\&\fBset\fR \fIvarname\fR = \fIvalue\fR
.PP
There may be an arbitrary amount of whitespace around the equal sign
(including no whitespace at all). If you want to have a value that
starts in a whitespace character, you may start the value with a
backslash character (just like with the normal settings, a leading
backslash is always ignored).
.PP
You may also set user defined variables on the command line by using the
\&\fI\-\-userset\fR option:
.PP
.Vb 2
\&  % arename \-\-userset variable0=value
\&  % arename \-u variable0=value
.Ve
.PP
User defined variables are useful to make hooks configurable (see
\&\*(L"\s-1HOOKS\*(R"\s0 below). Starting with version 4 of \fBarename\fR, user defined
variables may also be defined within sections, which (just like normal
option) makes them applicable only if said section is used for a given
file.
.SH "TEMPLATE FORMAT"
.IX Header "TEMPLATE FORMAT"
\&\fBarename\fR's templates are fairly easy to understand, but powerful.
.PP
At simplest, a template is just a fixed character string. However,
that would not be exactly useful, because then every file you would
ever want to rename would be getting the exact same name. That is why
\&\fBarename\fR is able to expand certain expressions with information
gathered from the file's tagging information.
.PP
An expression basically looks like one of the following forms:
.IP "\fB&\fR\fIidentifier\fR" 8
.IX Item "&identifier"
This is the `\fBtrivial\fR' expression. It will expand to the information
stored within the corresponding tag. If the tag in question is not
available, the expansion of the template string will fail.
.IP "\fB&\fR\fIidentifier\fR\fB[\fR\fIlength\fR\fB]\fR" 8
.IX Item "&identifier[length]"
The `\fBsized\fR' expression. The \fIlength\fR modifier in square brackets
defines the maximum length, to which the expression should be
expanded.
.Sp
That means, if the artist of a file reveals to be '\fIFrank Zappa\fR',
then using '\fB&artist[1]\fR' will expand to '\fIF\fR'.
.IP "\fB&{\fR\fIidentifier\fR\fB:\fR\fIdefault-template\fR\fB}\fR" 8
.IX Item "&{identifier:default-template}"
This is the first complex expression, called `\fBcomplex-default\fR'. When
the tag, which corresponds to `\fIidentifier\fR' is available, this
expression will expand exactly like the trivial expression would.
.Sp
If it is \fBnot\fR available though, the expansion doesn't fail, but
instead the `\fIdefault-template\fR' string is expanded.
.IP "\fB&{\fR\fIidentifier\fR\fB?\fR\fIset-template\fR\fB!\fR\fIunset-template\fR\fB}\fR" 8
.IX Item "&{identifier?set-template!unset-template}"
This expansion is called `\fBcomplex-set-unset\fR'. Again, what will be
used during template expansion depends on whether the tag which
corresponds to `\fIidentifier\fR' is set or not.
.Sp
If it is \fBset\fR, the string \fIset-template\fR is expanded; if it is
\&\fBunset\fR, the \fIunset-template\fR string is used.
.PP
Both simple expansions may be used with braces, like the complex
expansions are:
.IP "\fB&{\fR\fIidentifier\fR\fB}\fR" 8
.IX Item "&{identifier}"
This is equal to `\fB&identifier\fR'.
.IP "\fB&{\fR\fIidentifier[length]\fR\fB}\fR" 8
.IX Item "&{identifier[length]}"
And this is equal to `\fB&identifier[length]\fR'.
.PP
Backslashes are special in template strings, because they are used to
quote characters that bear special meaning (for example, to get a
ampersand character, you need to use "\fB\e&\fR"). To get an actual
backslash in the resulting string, you need to use a backslash, quoted
by a backslash. A backslash on non-special characters is silently
dropped.
.SS "Nesting expressions"
.IX Subsection "Nesting expressions"
In complex expressions, the strings called `\fIdefault-template\fR',
`\fIset-template\fR' and `\fIunset-template\fR' are subject to regular
template expansion. Hence, expressions like the following are
possible:
.PP
.Vb 1
\&  "&{album?&album/!}"
.Ve
.PP
If `\fBalbum\fR' were set, it would expand to its value followed by a
slash; otherwise it would expand to nothing. Using this, it is fairly
easy to deal with album-less tracks:
.PP
.Vb 1
\&  "&artist/&{album?&album/&tracknumber. !\-no\-album\-/}&tracktitle"
.Ve
.PP
That will effectively use the following template if `\fBalbum\fR' is set:
.PP
.Vb 1
\&  "&artist/&album/&tracknumber. &tracktitle"
.Ve
.PP
But if it is not set, it will instead use this:
.PP
.Vb 1
\&  "&artist/\-no\-album\-/&tracktitle"
.Ve
.PP
Caution has to be taken if certain characters are to be used within
conditional template expressions. For example, to use a closing curly
bracket in either of them, it needs to be quoted using a backslash
character.
.PP
Similarly, if an exclamation mark is to be used in a
`\fIset-template\fR', it needs to be quoted by a backslash to avoid the
character being interpreted as the end of the `\fIset-template\fR'
string.
.SS "Available expression identifiers"
.IX Subsection "Available expression identifiers"
The data, that is expanded is derived from tagging information in the
audio files. There are two kinds of information available. One is the
purely informational tag (like a track's artist) and the other further
describes the format of the audio file (like the file's bitrate).
.PP
If you are defining a lot of templates on the command line, you may
find that these identifiers take quite a while to type. If the
\&\fItemplate_aliases\fR option is set, you may use shorter alias names
instead of the the real identifier. Available aliases are listed with
their corresponding idetifier below.
.PP
This is a list of all informational identifiers available for
\&\fBall\fR file-types:
.IP "\fBalbum\fR" 8
.IX Item "album"
The album the currently processed track is part of. (alias: \fIal\fR)
.IP "\fBartist\fR" 8
.IX Item "artist"
The artist for the current track. (alias: \fIar\fR)
.IP "\fBcompilation\fR" 8
.IX Item "compilation"
Compilation tags are not very stable across different file
types. Usually, this is set to a string like "\fIVarious Artists\fR" for
tracks that are part of some sort of compilation album (like motion
picture sound-tracks). (alias: \fIcmp\fR)
.IP "\fBgenre\fR" 8
.IX Item "genre"
The genre or content type of the audio file. (alias: \fIgn\fR)
.IP "\fBtracknumber\fR" 8
.IX Item "tracknumber"
The number of the position of the track on the disc. Obviously. However, this
can be in the form of '12' or '12/23'. In the second form, only the part left
of the slash is used. The tracknumber is a little special, as you can define
to what width it should be padded with zeros on the left (see \fItnpad\fR setting
in \*(L"\s-1SETTINGS\*(R"\s0). (alias: \fItn\fR)
.IP "\fBtracktitle\fR" 8
.IX Item "tracktitle"
The title of the currently processed track. (alias: \fItt\fR)
.IP "\fByear\fR" 8
.IX Item "year"
Chronological information about the track (usually the year a song was
written or the year the album a track is part of was
released). (alias: \fIyr\fR)
.PP
Here is a list of file-format information tag available for \fBall\fR
file-types:
.IP "\fBbitrate\fR" 8
.IX Item "bitrate"
The bitrate the file was recorded/encoded with. (alias: \fIbr\fR)
.IP "\fBchannels\fR" 8
.IX Item "channels"
The number of channels available in the file (for example, this is `2'
for stereo files). (alias: \fIch\fR)
.IP "\fBlength_ms\fR" 8
.IX Item "length_ms"
The length of the track in milli-seconds. (alias: \fIln\fR)
.IP "\fBsamplerate\fR" 8
.IX Item "samplerate"
The samplerate the file was recorded/encoded with. (alias: \fIsr\fR)
.PP
For \fBall\fR file-types, the following tags are generated from the ones
listed above (for convenience):
.IP "\fBkbitrate\fR" 8
.IX Item "kbitrate"
Kilobits per second (bitrate / 1000). (alias: \fIkbr\fR)
.IP "\fBksamplerate\fR" 8
.IX Item "ksamplerate"
Kilosamples per second (samplerate / 1000). (alias: \fIksr\fR)
.IP "\fBlength_sec\fR" 8
.IX Item "length_sec"
The length of the track in seconds. (alias: \fIls\fR)
.PP
Some tags are only available for certain file-types. They are always
called `\fItype_\fR\fB*\fR'. File-type specific identifiers do not have
alias names. Here is a list of those tags:
.IP "\fBflac_wordsize\fR" 8
.IX Item "flac_wordsize"
The word-size used in a flac file. `24' if samples are 24 bits wide.
.IP "\fBmp3_id3_version\fR" 8
.IX Item "mp3_id3_version"
The version of the id3 tag used in mp3 files (e.g. "\fBID3v2.3.0\fR").
.IP "\fBwav_id3_version\fR" 8
.IX Item "wav_id3_version"
The same as `\fImp3_id3_version\fR', but for wave files.
.SH "EXIT STATUS"
.IX Header "EXIT STATUS"
\&\fBarename\fR returns zero if everything went fine; non-zero on fatal
problems. This may change in future versions.
.SH "HOOKS"
.IX Header "HOOKS"
Before we start, a word of warning: Hooks can solve a lot of problems.
That amount of flexibility comes at its price. All data passed to
hook functions are \fBreferences\fR to the \fBactual data\fR in the script
(except for the namespace argument, which is a copy). If you write
hooks carelessly, arename will get back at you! \s-1HOOKS ARE A BIG
HAMMER, THAT CAN CRUSH PROBLEMS AS WELL AS LIMBS\s0!
.PP
\&\fIYou have been warned!\fR
.SS "Discussion"
.IX Subsection "Discussion"
The reason for implementing hooks was to have a simple way of post
processing tags, filenames etc. without having to invent own magic in
the configuration files, when Perl has regular expressions on steriods
anyway. Hooks can do more then pure pre and post processing, because
they are called in numerous places and give broad access to the script's
data structures. Still, post processing is probably the most useful
feature they implement.
.PP
Hooks are just Perl subroutines, which are defined in one of two files
(see \*(L"\s-1FILES\*(R"\s0). They are run at certain events during the
execution of arename. The contents of the argument list for each hook
depends on what hook is called (see the \*(L"List of hook events\*(R" below).
However, the first argument (argument zero aka. \f(CW$_\fR[0]) to all hooks is
the hook namespace, the subroutine is called in.
.PP
The global hooks file is read before the local one, which means, that
this local file may overwrite and extend the definitions from the global
file, as much as Perl permits. This also means, that hooks from the
local file are run \fIafter\fR the ones from the global file (unless you
are using your own method of registering hooks; but if you do so, you
know what you are doing anyway).
.PP
Subroutines must be registered to arename, to be known as hooks.
Once registered, a subroutine can be removed from the known hooks,
if requested (see \*(L"Utility subroutines\*(R" below).
.PP
The keys in various data hashes passed to the hooks can be one of
the following: \fIalbum\fR, \fIartist\fR, \fIcompilation\fR, \fIgenre\fR,
\&\fItracknumber\fR, \fItracktitle\fR, \fIyear\fR.
.SS "Utility subroutines"
.IX Subsection "Utility subroutines"
\fIRegistration subroutines\fR
.IX Subsection "Registration subroutines"
.PP
There are two subroutines, that are used to tell arename about
subroutines, you defined that shall become hooks.
.IP "\fBregister_hook\fR(\fIevent\fR, \fIcoderef\fR)" 4
.IX Item "register_hook(event, coderef)"
Registers a \fIcode reference\fR (read: your subroutine) for the given
\&\fIevent\fR. Example: register_hook('startup', \e&custom_banner);
.IP "\fBremove_hook\fR(\fIevent\fR, \fIcoderef\fR)" 4
.IX Item "remove_hook(event, coderef)"
Removes \fBall\fR entries of the \fIcode reference\fR for the given
\&\fIevent\fR. Example: remove_hook('startup', \e&custom_banner);
.Sp
If the coderef was added more than once, all entries are removed.
.PP
\fIFile access and manipulation\fR
.IX Subsection "File access and manipulation"
.PP
The currently processed file name can be accessed via two subroutines:
.IP "\fBget_file\fR()" 4
.IX Item "get_file()"
Returns the current file name as a string. This way, you can get the
name of the currently processed file in every hook.
.IP "\fBset_file\fR(\fIfile name string\fR)" 4
.IX Item "set_file(file name string)"
This gives you the opportunity of manipulating the current file name.
Be careful using this, because if you break the file name, \fBarename\fR
cannot work properly.
.PP
With these, you could even change the file name of the processed file,
while \fBarename\fR works on it (which you really should only do, if you
know what you are doing).
.PP
\fIUser-defined-variable subroutines\fR
.IX Subsection "User-defined-variable subroutines"
.PP
Hooks can also use the data from user defined variables, via their Perl
interface:
.IP "\fBuser_get\fR(\fIsetting\fR)" 4
.IX Item "user_get(setting)"
Returns the current value of \fIsetting\fR. This is always a scalar value.
.IP "\fBuser_set\fR(\fIsetting\fR, \fIvalue\fR)" 4
.IX Item "user_set(setting, value)"
Change the value of \fIsetting\fR to \fIvalue\fR.
.PP
Here is an example for user defined settings:
.PP
.Vb 5
\&  # Assume, the user set the myvar\-variable to "bar" in his
\&  # configuration file
\&  my $foo = user_get(\*(Aqmyvar\*(Aq);    # $foo is now "bar"
\&  user_set(\*(Aqfoo\*(Aq, "bar, baz");
\&  my $foo = user_get(\*(Aqmyvar\*(Aq);    # $foo is now "bar, baz"
.Ve
.PP
\fI\s-1API\s0 for accessing to arename's internal configuration\fR
.IX Subsection "API for accessing to arename's internal configuration"
.PP
You can also access the configuration data of \fBarename\fR itself:
.IP "\fBget_opt\fR(\fIsetting\fR)" 4
.IX Item "get_opt(setting)"
Returns the current value of \fIsetting\fR. This is always a scalar value.
.IP "\fBset_opt\fR(\fIsetting\fR, \fIvalue\fR)" 4
.IX Item "set_opt(setting, value)"
Change the value of \fIsetting\fR to \fIvalue\fR.
.PP
A list of settings \fBarename\fR will use: canonicalize, dryrun, force,
hookerrfatal, prefix, quiet, quiet_skip, readstdin, sepreplace, tnpad,
usehooks, uselocalhooks, uselocalrc, verbose, verbosity, comp_template and
template.
.PP
If you want to actually change these settings, you should have a profound
knowledge of \fBarename\fR's internals. Be careful.
.PP
\fI\s-1API\s0 for default_* settings\fR
.IX Subsection "API for default_* settings"
.PP
If you need to access the current values of the \fIdefault_*\fR settings:
.IP "\fBget_defaults\fR(\fItagname\fR)" 4
.IX Item "get_defaults(tagname)"
Returns the value of default_\fItagname\fR.
.IP "\fBget_default_keys\fR()" 4
.IX Item "get_default_keys()"
Returns a lexically sorted array of tag names of currently set \fIdefault_*\fR
values.
.IP "\fBset_default\fR(\fItagname\fR, \fIvalue\fR)" 4
.IX Item "set_default(tagname, value)"
Sets the value of default_\fItagname\fR to \fIvalue\fR.
.PP
\fIMiscellaneous subroutines\fR
.IX Subsection "Miscellaneous subroutines"
.PP
And finally, a few miscellaneous functions ARename.pm provides, that
might be of interest.
.IP "\fBchoose_template\fR(\fIdata hash reference\fR)" 4
.IX Item "choose_template(data hash reference)"
Return the appropriate template (\fInormal\fR versus \fIcompiliation\fR template)
by the data in the referenced data hash.
.IP "\fBexpand_template\fR(\fItemplate string\fR, \fIdata hash reference\fR)" 4
.IX Item "expand_template(template string, data hash reference)"
Return the expanded version of \fItemplate string\fR. The information, that
is used to do the expansion is taken from the referenced data hash.
.Sp
Keep in mind that this function calls hooks itself. Avoid endless loops!
See \*(L"Hooks when expanding the template\*(R" for details.
.IP "\fBensure_dir\fR(\fIdirectory\fR)" 4
.IX Item "ensure_dir(directory)"
Makes sure \fIdirectory\fR exists. Think: mkdir \-p \fIdirectory\fR
.IP "\fBfile_eq\fR(\fIfile0\fR, \fIfile1\fR)" 4
.IX Item "file_eq(file0, file1)"
Checks if the name \fIfile0\fR and the name \fIfile1\fR point to the same file.
Returns \fI0\fR, if one of the file names does not exist or if the files do
not point to the same file, \fI1\fR otherwise.
.Sp
Dies if it cannot stat one of the given files.
.IP "\fBtag_supported\fR(\fItagname\fR)" 4
.IX Item "tag_supported(tagname)"
Returns \fI1\fR if the tag \fItagname\fR is supported by arename, \fI0\fR otherwise.
.IP "\fBtemplate_deep_inspect\fR(\fItemplate_string\fR)" 4
.IX Item "template_deep_inspect(template_string)"
This tokenises a template string and then looks at the whole token
tree, and tries to figure out any potential problems in it.
.Sp
If tokenisation already failed, a negative value is returned. In case
of any warnings with the token tree, zero is returned. If nothing came
up, a positive value is returned.
.Sp
This subroutine is called for the `\fItemplate\fR' and `\fIcomp_template\fR'
strings in all sections when \fBarename\fR starts. If the user chooses to
change a template string in a hook it is recommended to use this
function to avoid any errors due to broken templates.
.IP "\fBxrename\fR(\fIsrc\fR, \fIdest\fR)" 4
.IX Item "xrename(src, dest)"
Renames \fIsrc\fR to \fIdest\fR. Works across file systems, too. Dies
if something fails.
.SS "List of hook events"
.IX Subsection "List of hook events"
This is a complete list of hooks events with descriptions.
.PP
The first argument (argument number \*(L"zero\*(R") for every hook is the
name space they are called in. To find out the name of the currently
processed file, use the \fIget_file\fR() subroutine described above.
.PP
\fIHooks in the main loop\fR
.IX Subsection "Hooks in the main loop"
.PP
These hooks are called at the highest level of the script.
.IP "\fBcanonicalize\fR" 4
.IX Item "canonicalize"
This is called in the middle of the file name canonicalization process
(but \fBonly\fR if the \fIcanonicalize\fR setting is set).
.Sp
You can get the current file name via \fI\f(BIget_file()\fI\fR. The canonicalized
file name is handed to you via the hook's arguments. The value from
this argument will be assigned to the processed filename after the
execution of this hook.
.Sp
\&\fIArguments\fR: \fB1:\fR canonicalized file name
.IP "\fBnext_file_early\fR" 4
.IX Item "next_file_early"
Called at the start of the main loop \fIbefore\fR any file checks and
canonicalizations (if enabled) are done.
.Sp
\&\fIArguments\fR:
.IP "\fBnext_file_late\fR" 4
.IX Item "next_file_late"
Called in the main loop \fIafter\fR the file checks and canonicalizations
are done.
.Sp
In this context, file checks means tests for read-access and for
whether the processed file is a symlink. \fBarename\fR will refuse to
process symlinks and files it cannot read.
.Sp
\&\fIArguments\fR:
.IP "\fBfile_done\fR" 4
.IX Item "file_done"
Called in the main loop \fIafter\fR the file has been processed (unless
\&\fBfiletype_unknown\fR was triggered, see below).
.Sp
\&\fIArguments\fR:
.IP "\fBfiletype_unknown\fR" 4
.IX Item "filetype_unknown"
Called in the main loop \fIafter\fR the file was tried to be processed but
the file type (the extension, specifically) was unknown.
.Sp
\&\fIArguments\fR:
.IP "\fBfiletype_known\fR" 4
.IX Item "filetype_known"
Called when it has been established, that the file in question should
theoretically be supported by arename.
.Sp
\&\fIArguments\fR: \fB1:\fR the current file name extension \fB2:\fR the file
type that has been detected
.IP "\fBpre_rename\fR" 4
.IX Item "pre_rename"
This is triggered directly before the actual file renaming process
starts. All information about the file has been gathered at this
point.
.Sp
\&\fIArguments\fR: \fB1:\fR the file type, \fB2:\fR the extension that will be
used to assemble the target filename, \fB3:\fR the data hash
.PP
\fIHooks in the renaming procedure\fR
.IX Subsection "Hooks in the renaming procedure"
.PP
When all data has been gathered, \fBarename\fR will go on to actually
rename the files to their new destination name (which will be generated
in the process, see \*(L"Hooks when expanding the template\*(R" below).
.IP "\fBpre_apply_defaults\fR" 4
.IX Item "pre_apply_defaults"
This is the first action to be taken in the renaming process. It is
called even before the default values are applied.
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR file extension
.IP "\fBpre_template\fR" 4
.IX Item "pre_template"
Called \fIbefore\fR template expansions have been done.
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR file extension
.IP "\fBpost_template\fR" 4
.IX Item "post_template"
Called \fIafter\fR the template has been expanded and the new file name
has been completely generated (including the destination directory
prefix).
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR file extension
\&\fB3:\fR the generated new filename (including directory prefix and file
extension)
.IP "\fBpost_ensure_dir\fR" 4
.IX Item "post_ensure_dir"
The destnation directory for the new file name may contain sub directories,
which currently do not exist. This hook is called \fIafter\fR it is ensured,
every directory portion exists.
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR file extension
\&\fB3:\fR the generated new filename (including directory prefix and file
extension)
.IP "\fBpost_rename\fR" 4
.IX Item "post_rename"
This is the final hook in the actual renaming process. The file has been
renamed at this point.
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR file extension
\&\fB3:\fR the generated new filename (including directory prefix and file
extension)
.PP
\fIHooks when expanding the template\fR
.IX Subsection "Hooks when expanding the template"
.PP
These hooks are called when the template string is filled with the data
from tags in the audio files. To do this, \fBarename\fR first tokenises the
template string into a data structure, which is later used to assemble
the target file name.
.IP "\fBpre_expand_template\fR" 4
.IX Item "pre_expand_template"
Called before any expansions are done.
.Sp
\&\fIArguments\fR: \fB1:\fR the template string, \fB2:\fR the data hash
.IP "\fBpost_expand_template\fR" 4
.IX Item "post_expand_template"
Called after all expansions have been done, right before the the resulting
string is returned.
.Sp
\&\fIArguments\fR: \fB1:\fR the template string (fully expanded), \fB2:\fR the data
hash
.IP "\fBexpand_template_pre_expand_tag\fR" 4
.IX Item "expand_template_pre_expand_tag"
Called each time the value of an existing tag is expanded. This may be
more than once, as tags may be used as often in a template as the user
requires. At each point, this hook will be called right before the
data was retrieved and post-processed (like zero-padding the
`tracknumber' tag).
.Sp
\&\fIArguments\fR: \fB1:\fR the tag's name, \fB2:\fR the data hash
.IP "\fBexpand_template_unknown_tag\fR" 4
.IX Item "expand_template_unknown_tag"
This hook gets called whenever arename tries to expand a tag within a template,
for which it does not have any data available.
.Sp
\&\fIArguments\fR: \fB1:\fR the supposedly expanded string (`undef' upon hook-entry),
\&\fB2:\fR the tag's name, \fB2:\fR the data hash
.IP "\fBexpand_template_post_expand_tag\fR" 4
.IX Item "expand_template_post_expand_tag"
Called each time the value of an existing tag is expanded. Like with
the `expand_template_pre_expand_tag' hook, this may be more than once.
.Sp
At each point, this hook will be called right after the data was
retrieved and post-processed.
.Sp
\&\fIArguments\fR: \fB1:\fR the value, which will be used for expansion, \fB2:\fR
the tag's name, \fB2:\fR the data hash
.PP
\fIHooks while gathering information\fR
.IX Subsection "Hooks while gathering information"
.PP
These hooks are triggered while the tag information is extracted from
the audio files \fBarename\fR is processing. This is done in two
steps. First the Audio::Scan module is used to scan for the raw meta
data information from the current file. Then \fBarename\fR's data hash is
being filled with that data.
.IP "\fBpre_scan\fR" 4
.IX Item "pre_scan"
This hook is called right before any scanning has been done.
.Sp
\&\fIArguments\fR: \fB1:\fR the type of the file being processed (`ogg' for
ogg vorbis files)
.IP "\fBpost_scan\fR" 4
.IX Item "post_scan"
This is triggered as soon as Audio::Scan is done processing the
current file, but before \fBarename\fR's data hash has been filled.
.Sp
\&\fIArguments\fR: \fB1:\fR the type of the file being processed (`ogg' for
ogg vorbis files), \fB2:\fR the data structure returned by `Audio::Scan'
.IP "\fBambiguoustag\fR" 4
.IX Item "ambiguoustag"
When the data hash is being filled it is possible, that for one
\&\fBarename\fR tag (like `artist') multiple values where returned by
Audio::Scan. This hook is triggered as soon as such a tag with
ambiguous values is processed.
.Sp
The hook may be used for maximum control over how ambiguous values are
handled. To do this, the ambiguous value (passed as an array reference
in the second argument) should be turned into the desired scalar
value.
.Sp
If the array reference is left as it is, the usual `ambiguoususefirst'
behaviour is followed. The the option's description for details.
.Sp
\&\fIArguments\fR: \fB1:\fR the name of the tag with the ambiguous value,
\&\fB2:\fR its current (ambiguous) value, \fB3:\fR the data hash in its
current form (obviously not all values will have been filled in at
this point), \fB4:\fR the data structure returned by Audio::Scan (see its
documentation for details)
.IP "\fBpost_fill\fR" 4
.IX Item "post_fill"
Finally, the `post_fill' hook is called after the data hash has been
filled. This is a good spot, if post-processing the values of
individual tag is desired.
.Sp
\&\fIArguments\fR: \fB1:\fR return code of the filling process (`0' in case of
an error, `1' otherwise), \fB2:\fR the type of the file being processed
(`ogg' for ogg vorbis files), \fB3:\fR the data structure returned by
`Audio::Scan', \fB4:\fR the data hash.
.PP
\fIMiscellaneous hooks\fR
.IX Subsection "Miscellaneous hooks"
.IP "\fBapply_defaults\fR" 4
.IX Item "apply_defaults"
This is triggered before values from the default_* settings are applied
to missing values in the audio file. This hook is \fIonly\fR run if a
default value for a tag will be used!
.Sp
\&\fIArguments\fR: \fB1:\fR data hash, \fB2:\fR current key
.IP "\fBstartup\fR" 4
.IX Item "startup"
Called directly after all the module initialisation is done, at the very
start of the script. Configuration files will have been read, as well as
hook files (obviously) and command line options will have been handled at
this point already.
.Sp
This hook may be useful for postprocessing the configuration as well as
for debugging.
.Sp
\&\fIArguments\fR: \fB1:\fR program name, \fB2:\fR its version, \fB3:\fR
configuration hash, \fB4:\fR array of supported tags, \fB5:\fR the program's
argument list
.IP "\fBnormal_quit\fR" 4
.IX Item "normal_quit"
Called at the end of the script. This is reached if nothing fatal happened.
.Sp
\&\fIArguments\fR: \fB1:\fR the program's argument list
.SS "Example"
.IX Subsection "Example"
First, to give you an idea about how argument passing works in \fBarename\fR
hooks, take a look at these two `\fIstartup\fR' hooks:
.PP
.Vb 6
\&  sub print_banner0 {
\&      # Yes, everything handed over to hooks (except for the namespace)
\&      # are references. This gives us simple two way communication, but
\&      # it\*(Aqs also a pretty big responsibility to handle. Think before
\&      # screwing up. :)
\&      my ($ns, $nameref, $verref, $confref, $suptagsref, $argvref) = @_;
\&
\&      print "BANNER! $$nameref $$verref " . $argvref\->[0] . "\en";
\&
\&      # The following actually changes the $NAME variable, used
\&      # in ARename.pm, which doesn\*(Aqt hurt, because it is only the
\&      # name of the program running. For other hook events and variables,
\&      # there might be vital data in one of the references. Be very careful
\&      # before changing values willy\-nilly.
\&      $$nameref =~ s/name/blame/;
\&  }
\&  register_hook(\*(Aqstartup\*(Aq, \e&print_banner0);
\&
\&  sub print_banner1 {
\&      my ($ns, $nameref, $verref, $confref, $suptagsref, $argvref) = @_;
\&
\&      # Since $NAME used to be \*(Aqarename\*(Aq, the substitution
\&      # in print_banner0() will have changed $NAME to \*(Aqareblame\*(Aq,
\&      # which $$nameref below will reveal.
\&      print "ANOTHER BANNER! $$nameref $$verref\en";
\&  }
\&  register_hook(\*(Aqstartup\*(Aq, \e&print_banner1);
.Ve
.PP
After that short introduction, here is something more useful. The following
hook will replace all whitespace with underscores in generated file names.
.PP
.Vb 5
\&  sub replace_spaces_by_underscore {
\&      my ($templateref, $datref) = @_;
\&      $$templateref =~ s/\es+/_/g;
\&  }
\&  register_hook(\*(Aqpost_expand_template\*(Aq, \e&replace_spaces_by_underscore);
.Ve
.PP
This will do the trick, but there is actually an \fBarename\fR extension that is
distributed with the application, which is designed to solve exactly this
problem. See \*(L"\s-1EXTENSIONS\*(R"\s0 below for details on the `\fBReplaceSpaces\fR'
extension module.
.SH "EXTENSIONS"
.IX Header "EXTENSIONS"
\&\fBArename\fR comes with a number of extensions implemented as Perl modules, to
solve a number of more exotic tasks, that are not addressed within the core
Module `ARename.pm'.
.PP
All of these bundled extension modules (which are all children of the `ARename'
namespace) are fully documented within their source files and is accessible by
the `\fBperldoc\fR' utility:
.PP
.Vb 1
\&  % perldoc ARename::ReplaceSpaces
.Ve
.PP
Modules, that implement a hook all feature a convenience subroutine
`\fB\fBregister()\fB\fR', which registers the hook code to the event the author
intended. For example, to use the `\fBRenameSpaces\fR' hook, add the following to
your hooks file:
.PP
.Vb 2
\&  use ARename::ReplaceSpaces;
\&  ARename::ReplaceSpaces::register();
.Ve
.PP
Here is a list of bundled extensions:
.IP "\fBBailOut\fR" 4
.IX Item "BailOut"
This is a hook, to terminate \fBarename\fR after reading all configuration files.
It is designed to help with testing new settings and is probably not very
useful for the average user.
.IP "\fBKillNonASCII\fR" 4
.IX Item "KillNonASCII"
This module implements a hook that removes all non-ascii characters from
generated file names.
.Sp
This is also the extension module you want look at, if you are interested in
writing your own extension modules. It features all code and documentation,
that is required of an extension to make it into the \fBarename\fR package.
.IP "\fBMP3RecodeToUTF8\fR" 4
.IX Item "MP3RecodeToUTF8"
`\fBMP3RecodeToUTF8\fR' is a hook that attempts to cure problems caused by the
different types of mp3 tag versions and the encoding mess that comes along with
it.
.Sp
If you are on an \s-1UTF\-8\s0 based system and wonder why \fBarename\fR produces latin1
characters for mp3 files, that have non-ascii characters in their tags, this
extension may be of help.
.IP "\fBRemoveEmptySubdirs\fR" 4
.IX Item "RemoveEmptySubdirs"
This module tries to remove empty directories that might have emerged due to
files being moved to another directory in the renaming process.
.IP "\fBReplaceSpaces\fR" 4
.IX Item "ReplaceSpaces"
This is a hook that replaces whitespace in generated filenames by a configurable
string, which defaults to a single underscore character \fB\*(L"_\*(R"\fR.
.IP "\fBTemplate::Albumless\fR" 4
.IX Item "Template::Albumless"
Implements a hook to handle tracks with missing `album' tags, by offering to
switch to an entirely different template for these files.
.IP "\fBTNPadAdjustByAlbum\fR" 4
.IX Item "TNPadAdjustByAlbum"
This module allows one to adjust the value of the `\fItnpad\fR' core setting based on
patterns that are matched against a track's `album' tag.
.Sp
The idea is to have proper padding the large audiobooks that contain more than
99 tracks.
.PP
There are a few utility modules, that implement helpful code that is shared
among all bundled extension modules. Some of the code may be useful to user
defined hooks or extension modules, too.
.IP "\fBUtil::Files\fR" 4
.IX Item "Util::Files"
This is a module that contains file-related utilities.
.IP "\fBUtil::IsNumber\fR" 4
.IX Item "Util::IsNumber"
The purpose of this module is to provide helper subroutines, which check if
values look like numbers (integers, unsigned integers, etc.).
.IP "\fBUtil::RegisterModuleHook\fR" 4
.IX Item "Util::RegisterModuleHook"
This implements a helper to quickly create the `\fI\f(BIregister()\fI\fR' subroutine of
hook extension modules.
.IP "\fBUtil::VersionGuard\fR" 4
.IX Item "Util::VersionGuard"
This module implements a subroutine, that is designed to detect version
discrepancies between an extension module and the `ARename.pm' core module.
.SS "User-defined Extensions"
.IX Subsection "User-defined Extensions"
Say you have decided, that the `\fI\f(BIARename::Extension::register()\fI\fR' idea to
encapsulate extensions is a good idea and now you want to do that yourself,
too. Maybe because, you just like to keep your `hooks' file tidy or maybe
because you want to contribute your awesome extension code back to
\&\fBarename\fR. Either way, you will need a place to put your Perl code.
.PP
\&\fBArename\fR does \fB\s-1NOT\s0\fR set such a place by default. But it is very easy to set
it yourself from the `hooks' file:
.PP
.Vb 3
\&  BEGIN {
\&      unshift @INC, $ENV{HOME} . q{/.arename};
\&  }
.Ve
.PP
That way you can place Perl modules into `\fI~/.arename\fR' like this:
.PP
.Vb 1
\&  ~/.arename/ARename/MyAwesomeExtension.pm
.Ve
.PP
And then just use it like the bundled extensions:
.PP
.Vb 2
\&  use ARename::MyAwesomeExtension.pm;
\&  ARename::MyAwesomeExtension::register();
.Ve
.PP
Take a look at the `\fBKillNonASCII.pm.in\fR' file in the `\fBarename\fR' sources,
for details about how to write proper extensions and how to make them
configurable and how to make use of the bundled utilities to make your
extension appropriate for inclusion with `\fBarename\fR'.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fB\fBfind\fB\|(1)\fR, \fB\fBxargs\fB\|(1)\fR, \fB\fBperldoc\fB\|(1)\fR, \fBAudio::Scan\fR.
.PP
\&\fBARename::BailOut\fR, \fBARename::KillNonASCII\fR,
\&\fBARename::MP3RecodeToUTF8\fR, \fBARename::RemoveEmptySubdirs\fR,
\&\fBARename::ReplaceSpaces\fR, \fBARename::TNPadAdjustByAlbum\fR.
.PP
\&\fBARename::Template::Albumless\fR
.PP
\&\fBARename::Util::Files\fR, \fBARename::Util::IsNumber\fR,
\&\fBARename::Util::RegisterModuleHook\fR, \fBARename::Util::VersionGuard\fR.
.SH "VERSION"
.IX Header "VERSION"
This manual describes \fBarename\fR version \fI4.1\fR.
.SH "AUTHOR"
.IX Header "AUTHOR"
Frank Terbeck <ft@bewatermyfriend.org>,
.PP
Please report bugs.
.SH "LICENCE"
.IX Header "LICENCE"
.Vb 2
\& Copyright 2007\-2017
\& Frank Terbeck <ft@bewatermyfriend.org>, All rights reserved.
\&
\& Redistribution and use in source and binary forms, with or without
\& modification, are permitted provided that the following conditions
\& are met:
\&
\&   1. Redistributions of source code must retain the above
\&      copyright notice, this list of conditions and the following
\&      disclaimer.
\&   2. Redistributions in binary form must reproduce the above
\&      copyright notice, this list of conditions and the following
\&      disclaimer in the documentation and/or other materials
\&      provided with the distribution.
\&
\&  THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
\&  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
\&  OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
\&  DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS OF THE
\&  PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
\&  EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
\&  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
\&  PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
\&  OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
\&  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
\&  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.Ve