diff --git a/README.txt b/README.txt
deleted file mode 100644
index c93ca33f78023a8f381eb479542df0fd3acd3a4a..0000000000000000000000000000000000000000
--- a/README.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-This is a Subversion repository; use the 'svnadmin' tool to examine
-it.  Do not add, delete, or modify files here unless you know how
-to avoid corrupting the repository.
-
-Visit http://subversion.tigris.org/ for more information.
diff --git a/conf/authz b/conf/authz
deleted file mode 100644
index 3407445f097aa4005456cd397df23c07e7100b07..0000000000000000000000000000000000000000
--- a/conf/authz
+++ /dev/null
@@ -1,21 +0,0 @@
-### This file is an example authorization file for svnserve.
-### Its format is identical to that of mod_authz_svn authorization
-### files.
-### As shown below each section defines authorizations for the path and
-### (optional) repository specified by the section name.
-### The authorizations follow. An authorization line can refer to a
-### single user, to a group of users defined in a special [groups]
-### section, or to anyone using the '*' wildcard.  Each definition can
-### grant read ('r') access, read-write ('rw') access, or no access
-### ('').
-
-[groups]
-# harry_and_sally = harry,sally
-
-# [/foo/bar]
-# harry = rw
-# * =
-
-# [repository:/baz/fuz]
-# @harry_and_sally = rw
-# * = r
diff --git a/conf/passwd b/conf/passwd
deleted file mode 100644
index d22bafc5be1d69951740cc3effc180e8078ab402..0000000000000000000000000000000000000000
--- a/conf/passwd
+++ /dev/null
@@ -1,8 +0,0 @@
-### This file is an example password file for svnserve.
-### Its format is similar to that of svnserve.conf. As shown in the
-### example below it contains one section labelled [users].
-### The name and password for each user follow, one account per line.
-
-[users]
-# harry = harryssecret
-# sally = sallyssecret
diff --git a/conf/svnserve.conf b/conf/svnserve.conf
deleted file mode 100644
index 089b0d0ecd6163c4f1b9a33ef552c3e0145fdda8..0000000000000000000000000000000000000000
--- a/conf/svnserve.conf
+++ /dev/null
@@ -1,30 +0,0 @@
-### This file controls the configuration of the svnserve daemon, if you
-### use it to allow access to this repository.  (If you only allow
-### access through http: and/or file: URLs, then this file is
-### irrelevant.)
-
-### Visit http://subversion.tigris.org/ for more information.
-
-[general]
-### These options control access to the repository for unauthenticated
-### and authenticated users.  Valid values are "write", "read",
-### and "none".  The sample settings below are the defaults.
-# anon-access = read
-# auth-access = write
-### The password-db option controls the location of the password
-### database file.  Unless you specify a path starting with a /,
-### the file's location is relative to the conf directory.
-### Uncomment the line below to use the default password file.
-# password-db = passwd
-### The authz-db option controls the location of the authorization
-### rules for path-based access control.  Unless you specify a path
-### starting with a /, the file's location is relative to the conf
-### directory.  If you don't specify an authz-db, no path-based access
-### control is done.
-### Uncomment the line below to use the default authorization file.
-# authz-db = authz
-### This option specifies the authentication realm of the repository.
-### If two repositories have the same authentication realm, they should
-### have the same password database, and vice versa.  The default realm
-### is repository's uuid.
-# realm = My First Repository
diff --git a/db/current b/db/current
deleted file mode 100644
index c435b766cd0da671d14c2fd05ddf41eeac5e5b87..0000000000000000000000000000000000000000
--- a/db/current
+++ /dev/null
@@ -1 +0,0 @@
-0 1 1
diff --git a/db/format b/db/format
deleted file mode 100644
index 0cfbf08886fca9a91cb753ec8734c84fcbe52c9f..0000000000000000000000000000000000000000
--- a/db/format
+++ /dev/null
@@ -1 +0,0 @@
-2
diff --git a/db/fs-type b/db/fs-type
deleted file mode 100644
index 4fdd95313fe9f357cbaf861c9df01344935c42d9..0000000000000000000000000000000000000000
--- a/db/fs-type
+++ /dev/null
@@ -1 +0,0 @@
-fsfs
diff --git a/db/revprops/0 b/db/revprops/0
deleted file mode 100644
index b98531c49ff842b8be3a6c09a12d8a4d1801659d..0000000000000000000000000000000000000000
--- a/db/revprops/0
+++ /dev/null
@@ -1,5 +0,0 @@
-K 8
-svn:date
-V 27
-2008-03-12T08:27:04.109375Z
-END
diff --git a/db/revs/0 b/db/revs/0
deleted file mode 100644
index 10f5c45f9d886c5389c80f53780c969759bc24d3..0000000000000000000000000000000000000000
--- a/db/revs/0
+++ /dev/null
@@ -1,11 +0,0 @@
-PLAIN
-END
-ENDREP
-id: 0.0.r0/17
-type: dir
-count: 0
-text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
-cpath: /
-
-
-17 107
diff --git a/db/uuid b/db/uuid
deleted file mode 100644
index 447e3b9c18af8a69b540a25553f7e75040629a48..0000000000000000000000000000000000000000
--- a/db/uuid
+++ /dev/null
@@ -1 +0,0 @@
-0fabb406-36e8-374a-a0f3-cc3ced6fbdc5
diff --git a/db/write-lock b/db/write-lock
deleted file mode 100644
index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..0000000000000000000000000000000000000000
diff --git a/format b/format
deleted file mode 100644
index 7ed6ff82de6bcc2a78243fc9c54d3ef5ac14da69..0000000000000000000000000000000000000000
--- a/format
+++ /dev/null
@@ -1 +0,0 @@
-5
diff --git a/hooks/post-commit.tmpl b/hooks/post-commit.tmpl
deleted file mode 100644
index c1bfc3556fc0edbf79ddc408301ba8867bd16d31..0000000000000000000000000000000000000000
--- a/hooks/post-commit.tmpl
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/bin/sh
-
-# POST-COMMIT HOOK
-#
-# The post-commit hook is invoked after a commit.  Subversion runs
-# this hook by invoking a program (script, executable, binary, etc.)
-# named 'post-commit' (for which this file is a template) with the 
-# following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] REV          (the number of the revision just committed)
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# Because the commit has already completed and cannot be undone,
-# the exit code of the hook program is ignored.  The hook program
-# can use the 'svnlook' utility to help it examine the
-# newly-committed tree.
-#
-# On a Unix system, the normal procedure is to have 'post-commit'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'post-commit' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'post-commit.bat' or 'post-commit.exe',
-# but the basic idea is the same.
-# 
-# The hook program typically does not inherit the environment of
-# its parent process.  For example, a common problem is for the
-# PATH environment variable to not be set to its usual value, so
-# that subprograms fail to launch unless invoked via absolute path.
-# If you're having unexpected problems with a hook program, the
-# culprit may be unusual (or missing) environment variables.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter.
-# For more examples and pre-written hooks, see those in
-# the Subversion repository at
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
-
-
-REPOS="$1"
-REV="$2"
-
-commit-email.pl "$REPOS" "$REV" commit-watchers@example.org
-log-commit.py --repository "$REPOS" --revision "$REV"
diff --git a/hooks/post-lock.tmpl b/hooks/post-lock.tmpl
deleted file mode 100644
index 65a7d40eadc1080eba2ce546a3a608723473069e..0000000000000000000000000000000000000000
--- a/hooks/post-lock.tmpl
+++ /dev/null
@@ -1,44 +0,0 @@
-#!/bin/sh
-
-# POST-LOCK HOOK
-#
-# The post-lock hook is run after a path is locked.  Subversion runs
-# this hook by invoking a program (script, executable, binary, etc.)
-# named 'post-lock' (for which this file is a template) with the 
-# following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] USER         (the user who created the lock)
-#
-# The paths that were just locked are passed to the hook via STDIN (as
-# of Subversion 1.2, only one path is passed per invocation, but the
-# plan is to pass all locked paths at once, so the hook program
-# should be written accordingly).
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# Because the lock has already been created and cannot be undone,
-# the exit code of the hook program is ignored.  The hook program
-# can use the 'svnlook' utility to help it examine the
-# newly-created lock.
-#
-# On a Unix system, the normal procedure is to have 'post-lock'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'post-lock' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'post-lock.bat' or 'post-lock.exe',
-# but the basic idea is the same.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter:
-
-REPOS="$1"
-USER="$2"
-
-# Send email to interested parties, let them know a lock was created:
-mailer.py lock "$REPOS" "$USER" /path/to/mailer.conf
diff --git a/hooks/post-revprop-change.tmpl b/hooks/post-revprop-change.tmpl
deleted file mode 100644
index 395201a91853cf4549b517b2e39c924cb1780993..0000000000000000000000000000000000000000
--- a/hooks/post-revprop-change.tmpl
+++ /dev/null
@@ -1,56 +0,0 @@
-#!/bin/sh
-
-# POST-REVPROP-CHANGE HOOK
-#
-# The post-revprop-change hook is invoked after a revision property
-# has been added, modified or deleted.  Subversion runs this hook by
-# invoking a program (script, executable, binary, etc.) named
-# 'post-revprop-change' (for which this file is a template), with the
-# following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] REV          (the revision that was tweaked)
-#   [3] USER         (the username of the person tweaking the property)
-#   [4] PROPNAME     (the property that was changed)
-#   [5] ACTION       (the property was 'A'dded, 'M'odified, or 'D'eleted)
-#
-#   [STDIN] PROPVAL  ** the old property value is passed via STDIN.
-#
-# Because the propchange has already completed and cannot be undone,
-# the exit code of the hook program is ignored.  The hook program
-# can use the 'svnlook' utility to help it examine the
-# new property value.
-#
-# On a Unix system, the normal procedure is to have 'post-revprop-change'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'post-revprop-change' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'post-revprop-change.bat' or 'post-revprop-change.exe',
-# but the basic idea is the same.
-# 
-# The hook program typically does not inherit the environment of
-# its parent process.  For example, a common problem is for the
-# PATH environment variable to not be set to its usual value, so
-# that subprograms fail to launch unless invoked via absolute path.
-# If you're having unexpected problems with a hook program, the
-# culprit may be unusual (or missing) environment variables.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter.
-# For more examples and pre-written hooks, see those in
-# the Subversion repository at
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
-
-
-REPOS="$1"
-REV="$2"
-USER="$3"
-PROPNAME="$4"
-ACTION="$5"
-
-propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org
diff --git a/hooks/post-unlock.tmpl b/hooks/post-unlock.tmpl
deleted file mode 100644
index 5821be83e15a7d1bc869b6d94e5ff7eb86688818..0000000000000000000000000000000000000000
--- a/hooks/post-unlock.tmpl
+++ /dev/null
@@ -1,42 +0,0 @@
-#!/bin/sh
-
-# POST-UNLOCK HOOK
-#
-# The post-unlock hook runs after a path is unlocked.  Subversion runs
-# this hook by invoking a program (script, executable, binary, etc.)
-# named 'post-unlock' (for which this file is a template) with the 
-# following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] USER         (the user who destroyed the lock)
-#
-# The paths that were just unlocked are passed to the hook via STDIN
-# (as of Subversion 1.2, only one path is passed per invocation, but
-# the plan is to pass all unlocked paths at once, so the hook program
-# should be written accordingly).
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# Because the lock has already been destroyed and cannot be undone,
-# the exit code of the hook program is ignored.
-#
-# On a Unix system, the normal procedure is to have 'post-unlock'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'post-unlock' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'post-unlock.bat' or 'post-unlock.exe',
-# but the basic idea is the same.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter:
-
-REPOS="$1"
-USER="$2"
-
-# Send email to interested parties, let them know a lock was removed:
-mailer.py unlock "$REPOS" "$USER" /path/to/mailer.conf
diff --git a/hooks/pre-commit.tmpl b/hooks/pre-commit.tmpl
deleted file mode 100644
index 4ac8669ea7150c5dfb48233c8714e639800e68a0..0000000000000000000000000000000000000000
--- a/hooks/pre-commit.tmpl
+++ /dev/null
@@ -1,70 +0,0 @@
-#!/bin/sh
-
-# PRE-COMMIT HOOK
-#
-# The pre-commit hook is invoked before a Subversion txn is
-# committed.  Subversion runs this hook by invoking a program
-# (script, executable, binary, etc.) named 'pre-commit' (for which
-# this file is a template), with the following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] TXN-NAME     (the name of the txn about to be committed)
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# If the hook program exits with success, the txn is committed; but
-# if it exits with failure (non-zero), the txn is aborted, no commit
-# takes place, and STDERR is returned to the client.   The hook
-# program can use the 'svnlook' utility to help it examine the txn.
-#
-# On a Unix system, the normal procedure is to have 'pre-commit'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-#   ***  NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT  ***
-#   ***  FOR REVISION PROPERTIES (like svn:log or svn:author).   ***
-#
-#   This is why we recommend using the read-only 'svnlook' utility.
-#   In the future, Subversion may enforce the rule that pre-commit
-#   hooks should not modify the versioned data in txns, or else come
-#   up with a mechanism to make it safe to do so (by informing the
-#   committing client of the changes).  However, right now neither
-#   mechanism is implemented, so hook writers just have to be careful.
-#
-# Note that 'pre-commit' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'pre-commit.bat' or 'pre-commit.exe',
-# but the basic idea is the same.
-#
-# The hook program typically does not inherit the environment of
-# its parent process.  For example, a common problem is for the
-# PATH environment variable to not be set to its usual value, so
-# that subprograms fail to launch unless invoked via absolute path.
-# If you're having unexpected problems with a hook program, the
-# culprit may be unusual (or missing) environment variables.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter.
-# For more examples and pre-written hooks, see those in
-# the Subversion repository at
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
-
-
-REPOS="$1"
-TXN="$2"
-
-# Make sure that the log message contains some text.
-SVNLOOK=/usr/local/bin/svnlook
-$SVNLOOK log -t "$TXN" "$REPOS" | \
-   grep "[a-zA-Z0-9]" > /dev/null || exit 1
-
-# Check that the author of this commit has the rights to perform
-# the commit on the files and directories being modified.
-commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1
-
-# All checks passed, so allow the commit.
-exit 0
diff --git a/hooks/pre-lock.tmpl b/hooks/pre-lock.tmpl
deleted file mode 100644
index f4c43d25d56bd4aea630abf40ee347e6347e1832..0000000000000000000000000000000000000000
--- a/hooks/pre-lock.tmpl
+++ /dev/null
@@ -1,64 +0,0 @@
-#!/bin/sh
-
-# PRE-LOCK HOOK
-#
-# The pre-lock hook is invoked before an exclusive lock is
-# created.  Subversion runs this hook by invoking a program 
-# (script, executable, binary, etc.) named 'pre-lock' (for which
-# this file is a template), with the following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] PATH         (the path in the repository about to be locked)
-#   [3] USER         (the user creating the lock)
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# If the hook program exits with success, the lock is created; but
-# if it exits with failure (non-zero), the lock action is aborted
-# and STDERR is returned to the client.
-
-# On a Unix system, the normal procedure is to have 'pre-lock'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'pre-lock' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'pre-lock.bat' or 'pre-lock.exe',
-# but the basic idea is the same.
-#
-# Here is an example hook script, for a Unix /bin/sh interpreter:
-
-REPOS="$1"
-PATH="$2"
-USER="$3"
-
-# If a lock exists and is owned by a different person, don't allow it
-# to be stolen (e.g., with 'svn lock --force ...').
-
-# (Maybe this script could send email to the lock owner?)
-SVNLOOK=/usr/local/bin/svnlook
-GREP=/bin/grep
-SED=/bin/sed
-
-LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \
-            $GREP '^Owner: ' | $SED 's/Owner: //'`
-
-# If we get no result from svnlook, there's no lock, allow the lock to
-# happen:
-if [ "$LOCK_OWNER" = "" ]; then
-  exit 0
-fi
-
-# If the person locking matches the lock's owner, allow the lock to
-# happen:
-if [ "$LOCK_OWNER" = "$USER" ]; then
-  exit 0
-fi
-
-# Otherwise, we've got an owner mismatch, so return failure:
-echo "Error: $PATH already locked by ${LOCK_OWNER}." 1>&2
-exit 1
diff --git a/hooks/pre-revprop-change.tmpl b/hooks/pre-revprop-change.tmpl
deleted file mode 100644
index 9e284a917d099a31d807f21fdcd0f09425cd9b55..0000000000000000000000000000000000000000
--- a/hooks/pre-revprop-change.tmpl
+++ /dev/null
@@ -1,66 +0,0 @@
-#!/bin/sh
-
-# PRE-REVPROP-CHANGE HOOK
-#
-# The pre-revprop-change hook is invoked before a revision property
-# is added, modified or deleted.  Subversion runs this hook by invoking
-# a program (script, executable, binary, etc.) named 'pre-revprop-change'
-# (for which this file is a template), with the following ordered
-# arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] REVISION     (the revision being tweaked)
-#   [3] USER         (the username of the person tweaking the property)
-#   [4] PROPNAME     (the property being set on the revision)
-#   [5] ACTION       (the property is being 'A'dded, 'M'odified, or 'D'eleted)
-#
-#   [STDIN] PROPVAL  ** the new property value is passed via STDIN.
-#
-# If the hook program exits with success, the propchange happens; but
-# if it exits with failure (non-zero), the propchange doesn't happen.
-# The hook program can use the 'svnlook' utility to examine the 
-# existing value of the revision property.
-#
-# WARNING: unlike other hooks, this hook MUST exist for revision
-# properties to be changed.  If the hook does not exist, Subversion 
-# will behave as if the hook were present, but failed.  The reason
-# for this is that revision properties are UNVERSIONED, meaning that
-# a successful propchange is destructive;  the old value is gone
-# forever.  We recommend the hook back up the old value somewhere.
-#
-# On a Unix system, the normal procedure is to have 'pre-revprop-change'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'pre-revprop-change' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'pre-revprop-change.bat' or 'pre-revprop-change.exe',
-# but the basic idea is the same.
-#
-# The hook program typically does not inherit the environment of
-# its parent process.  For example, a common problem is for the
-# PATH environment variable to not be set to its usual value, so
-# that subprograms fail to launch unless invoked via absolute path.
-# If you're having unexpected problems with a hook program, the
-# culprit may be unusual (or missing) environment variables.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter.
-# For more examples and pre-written hooks, see those in
-# the Subversion repository at
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
-
-
-REPOS="$1"
-REV="$2"
-USER="$3"
-PROPNAME="$4"
-ACTION="$5"
-
-if [ "$ACTION" = "M" -a "$PROPNAME" = "svn:log" ]; then exit 0; fi
-
-echo "Changing revision properties other than svn:log is prohibited" >&2
-exit 1
diff --git a/hooks/pre-unlock.tmpl b/hooks/pre-unlock.tmpl
deleted file mode 100644
index 1298e8050263f095e27638565d202ed24a1e5841..0000000000000000000000000000000000000000
--- a/hooks/pre-unlock.tmpl
+++ /dev/null
@@ -1,60 +0,0 @@
-#!/bin/sh
-
-# PRE-UNLOCK HOOK
-#
-# The pre-unlock hook is invoked before an exclusive lock is
-# destroyed.  Subversion runs this hook by invoking a program 
-# (script, executable, binary, etc.) named 'pre-unlock' (for which
-# this file is a template), with the following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] PATH         (the path in the repository about to be unlocked)
-#   [3] USER         (the user destroying the lock)
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# If the hook program exits with success, the lock is destroyed; but
-# if it exits with failure (non-zero), the unlock action is aborted
-# and STDERR is returned to the client.
-
-# On a Unix system, the normal procedure is to have 'pre-unlock'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'pre-unlock' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'pre-unlock.bat' or 'pre-unlock.exe',
-# but the basic idea is the same.
-#
-# Here is an example hook script, for a Unix /bin/sh interpreter:
-
-REPOS="$1"
-PATH="$2"
-USER="$3"
-
-# If a lock is owned by a different person, don't allow it be broken.
-# (Maybe this script could send email to the lock owner?)
-
-SVNLOOK=/usr/local/bin/svnlook
-GREP=/bin/grep
-SED=/bin/sed
-
-LOCK_OWNER=`$SVNLOOK lock "$REPOS" "$PATH" | \
-            $GREP '^Owner: ' | $SED 's/Owner: //'`
-
-# If we get no result from svnlook, there's no lock, return success:
-if [ "$LOCK_OWNER" = "" ]; then
-  exit 0
-fi
-# If the person unlocking matches the lock's owner, return success:
-if [ "$LOCK_OWNER" = "$USER" ]; then
-  exit 0
-fi
-
-# Otherwise, we've got an owner mismatch, so return failure:
-echo "Error: $PATH locked by ${LOCK_OWNER}." 1>&2
-exit 1
diff --git a/hooks/start-commit.tmpl b/hooks/start-commit.tmpl
deleted file mode 100644
index e7707482b491d87345aab54fb3056f5b2f3d06c4..0000000000000000000000000000000000000000
--- a/hooks/start-commit.tmpl
+++ /dev/null
@@ -1,54 +0,0 @@
-#!/bin/sh
-
-# START-COMMIT HOOK
-#
-# The start-commit hook is invoked before a Subversion txn is created
-# in the process of doing a commit.  Subversion runs this hook
-# by invoking a program (script, executable, binary, etc.) named
-# 'start-commit' (for which this file is a template)
-# with the following ordered arguments:
-#
-#   [1] REPOS-PATH   (the path to this repository)
-#   [2] USER         (the authenticated user attempting to commit)
-#
-# The default working directory for the invocation is undefined, so
-# the program should set one explicitly if it cares.
-#
-# If the hook program exits with success, the commit continues; but
-# if it exits with failure (non-zero), the commit is stopped before
-# a Subversion txn is created, and STDERR is returned to the client.
-#
-# On a Unix system, the normal procedure is to have 'start-commit'
-# invoke other programs to do the real work, though it may do the
-# work itself too.
-#
-# Note that 'start-commit' must be executable by the user(s) who will
-# invoke it (typically the user httpd runs as), and that user must
-# have filesystem-level permission to access the repository.
-#
-# On a Windows system, you should name the hook program
-# 'start-commit.bat' or 'start-commit.exe',
-# but the basic idea is the same.
-# 
-# The hook program typically does not inherit the environment of
-# its parent process.  For example, a common problem is for the
-# PATH environment variable to not be set to its usual value, so
-# that subprograms fail to launch unless invoked via absolute path.
-# If you're having unexpected problems with a hook program, the
-# culprit may be unusual (or missing) environment variables.
-# 
-# Here is an example hook script, for a Unix /bin/sh interpreter.
-# For more examples and pre-written hooks, see those in
-# the Subversion repository at
-# http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/ and
-# http://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/
-
-
-REPOS="$1"
-USER="$2"
-
-commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1
-special-auth-check.py --user "$USER" --auth-level 3 || exit 1
-
-# All checks passed, so allow the commit.
-exit 0
diff --git a/interface/lib/lang/de.lng b/interface/lib/lang/de.lng
index db49eeae2cacbcf8f68a6b0377e24b9c66e7999e..b4aba435337c3d63928b8d00b7bd0a753524c254 100644
--- a/interface/lib/lang/de.lng
+++ b/interface/lib/lang/de.lng
@@ -1,21 +1,12 @@
-<?php
-
-// Globale Error Messages
-$wb[301] = 'Modul für User nicht erlaubt.';
-$wb[302] = 'Modul ungültig.';
-// Satz für deutsche Reiterkarten
-$wb[303] = '&nbsp;';
-// Satz für englische Reiterkarten
-$wb[304] = ' Dieses Formular dient zum Anlegen eines englischsprachigen Eintrags zusätzlich zu Ihrem deutschen Eintrag. Bitte vervollständigen Sie die Daten, soweit erforderlich, in Englisch - die Inhalte aus den Drop-Down-Menüs werden automatisch übersetzt:';
-
-$wb[1001] = 'Der Benutzername und das Passwort dürfen nicht leer sein!';
-$wb[1002] = 'Der Benutzername und/oder das Passwort sind nicht korrekt!';
-$wb[1003] = 'Der Benutzername ist deaktiviert!';
-
-$wb['delete_confirmation'] = 'Wollen Sie den Datensatz wirklich löschen?';
-
-$wb['error_no_view_permission'] = 'Sie haben nicht die Berechtigung, den Datensatz zu lesen, oder der Datensatz existiert nicht!';
-$wb['error_no_delete_permission'] = 'Sie haben nicht die Berechtigung, den Datensatz zu löschen!';
-
-
-?>
\ No newline at end of file
+<?php
+$wb['301'] = 'Modul fÞr User nicht erlaubt.';
+$wb['302'] = 'Modul ungïŋ―ltig.';
+$wb['303'] = ' ';
+$wb['304'] = ' Dieses Formular dient zum Anlegen eines englischsprachigen Eintrags zusïŋ―tzlich zu Ihrem deutschen Eintrag. Bitte vervollstïŋ―ndigen Sie die Daten, soweit erforderlich, in Englisch - die Inhalte aus den Drop-Down-Menïŋ―s werden automatisch ïŋ―bersetzt:';
+$wb['1001'] = 'Der Benutzername und das Passwort dïŋ―rfen nicht leer sein!';
+$wb['1002'] = 'Der Benutzername und/oder das Passwort sind nicht korrekt!';
+$wb['1003'] = 'Der Benutzername ist deaktiviert!';
+$wb['delete_confirmation'] = 'Wollen Sie den Datensatz wirklich lïŋ―schen?';
+$wb['error_no_view_permission'] = 'Sie haben nicht die Berechtigung, den Datensatz zu lesen, oder der Datensatz existiert nicht!';
+$wb['error_no_delete_permission'] = 'Sie haben nicht die Berechtigung, den Datensatz zu lïŋ―schen!';
+?>
diff --git a/interface/lib/lang/en.lng b/interface/lib/lang/en.lng
index 3c2811924c6bfd6f872bcd65f57cb72b0e7f34c6..724ac0df28143e005e38004904fb542e60400307 100644
--- a/interface/lib/lang/en.lng
+++ b/interface/lib/lang/en.lng
@@ -1,16 +1,10 @@
-<?php
-
-//* Global Error Messages
-$wb[301] = 'Module not permitted for the current user.';
-$wb[302] = 'Module invalid.';
-
-$wb[1001] = 'The username and password cannot be empty !';
-$wb[1002] = 'The username and/or password are not correct !';
-$wb[1003] = 'The username is deactivated!';
-
-$wb['delete_confirmation'] = 'Do you really want to delete this record?';
-
-$wb['error_no_view_permission'] = 'You don\'t have the permission to view this record or this record does not exist!';
-$wb['error_no_delete_permission'] = 'You don\'t have the permission to delete this record!';
-
-?>
\ No newline at end of file
+<?php
+$wb['301'] = 'Module not permitted for the current user.';
+$wb['302'] = 'Module invalid.';
+$wb['1001'] = 'The username and password cannot be empty !';
+$wb['1002'] = 'The username and/or password are not correct !';
+$wb['1003'] = 'The username is deactivated!';
+$wb['delete_confirmation'] = 'Do you really want to delete this record?';
+$wb['error_no_view_permission'] = 'You dont have the permission to view this record or this record does not exist!';
+$wb['error_no_delete_permission'] = 'You dont have the permission to delete this record!';
+?>
diff --git a/interface/web/admin/language_add.php b/interface/web/admin/language_add.php
index 3b66fb6efe9722b9e3fb5c67bb9aeb43884d591b..5d1d34cba3faba872695a3fbc093480b6fb1c0c1 100644
--- a/interface/web/admin/language_add.php
+++ b/interface/web/admin/language_add.php
@@ -49,6 +49,8 @@ $language_option = '';
 $error = '';
 $msg = '';
 $selected_language = (isset($_REQUEST['lng_select']))?substr($_REQUEST['lng_select'],0,2):'en';
+if(!preg_match("/^[a-z]{2}$/i", $selected_language)) die('unallowed characters in selected language name.');
+
 $handle = opendir(ISPC_ROOT_PATH.'/lib/lang/'); 
 while ($file = readdir ($handle)) { 
     if ($file != '.' && $file != '..') {
@@ -68,6 +70,7 @@ if(isset($_POST['lng_new']) && strlen($_POST['lng_new']) == 2 && $error == '') {
 	if(!preg_match("/^[a-z]{2}$/i", $lng_new)) die('unallowed characters in language name.');
 	
 	//* Make a copy of every language file
+	copy(ISPC_WEB_PATH."/$module/lib/lang/$selected_language.lng",ISPC_WEB_PATH."/$module/lib/lang/$lng_new.lng");
 	$bgcolor = '#FFFFFF';
 	$language_files_list = array();
 	$handle = @opendir(ISPC_WEB_PATH); 
diff --git a/interface/web/admin/language_edit.php b/interface/web/admin/language_edit.php
index 63293391535c98acdff7a6ded2ef7ad0319cb0b6..f2b7be5e1c439d98ac1b2be8fcd8473da85ccf36 100644
--- a/interface/web/admin/language_edit.php
+++ b/interface/web/admin/language_edit.php
@@ -65,13 +65,21 @@ if(isset($_POST['records']) && is_array($_POST['records'])) {
 		$msg = 'File saved.';
 	}
 	$file_content .= "?>\n";
-	file_put_contents(ISPC_WEB_PATH."/$module/lib/lang/$lang_file" ,$file_content);
+	if($module == 'global') {
+		file_put_contents(ISPC_LIB_PATH."/lang/$lang_file" ,$file_content);
+	} else {
+		file_put_contents(ISPC_WEB_PATH."/$module/lib/lang/$lang_file" ,$file_content);
+	}
 }
 
 
 $app->tpl->setVar(array('module' => $module,'lang_file' => $lang_file, 'lang' => $lang, 'msg' => $msg));
 
-include(ISPC_WEB_PATH."/$module/lib/lang/$lang_file");
+if($module == 'global') {
+	include(ISPC_LIB_PATH."/lang/$lang_file");
+} else {
+	include(ISPC_WEB_PATH."/$module/lib/lang/$lang_file");
+}
 
 $keyword_list = array();
 if(isset($wb) && is_array($wb)) {
diff --git a/interface/web/admin/language_list.php b/interface/web/admin/language_list.php
index 17eab0ef1be3100adacd8db950e84c41b5bc4636..47368c58f7ed477d86349b94d5d6b5b34f0969bc 100644
--- a/interface/web/admin/language_list.php
+++ b/interface/web/admin/language_list.php
@@ -44,6 +44,8 @@ $app->uses('tpl');
 $app->tpl->newTemplate('form.tpl.htm');
 $app->tpl->setInclude('content_tpl', 'templates/language_list.htm');
 
+$language_files_list = array();
+$bgcolor = '#FFFFFF';
 
 //* reading languages
 $language_option = '';
@@ -55,6 +57,16 @@ while ($file = readdir ($handle)) {
 		if($tmp_lng !='') {
 			$selected = ($tmp_lng == $selected_language)?'SELECTED':'';
 			$language_option .= "<option value='$tmp_lng' $selected>$tmp_lng</option>";
+			
+			//$bgcolor = ($bgcolor == '#FFFFFF') ? '#EEEEEE' : '#FFFFFF';
+			if($file == $selected_language.'.lng') {
+			$language_files_list[] = array(	'module' => 'global',
+											'lang_file' => $file,
+											'bgcolor'  => $bgcolor,
+											'lang' => $selected_language);
+			}
+			
+			
 		}
 	}
 }
@@ -62,8 +74,6 @@ $app->tpl->setVar('language_option',$language_option);
 // $app->tpl->setLoop('records', $language_list);
 
 //* list all language files of the selected language
-$bgcolor = '#FFFFFF';
-$language_files_list = array();
 $handle = @opendir(ISPC_WEB_PATH); 
 while ($file = @readdir ($handle)) { 
     if ($file != '.' && $file != '..') {
diff --git a/interface/web/themes/default/style.css b/interface/web/themes/default/style.css
index 46303b0050a15832e8c1873fc63e15a4b8d99f8f..af57b5fac31d13cf2a848dc326319d726ce4222a 100644
--- a/interface/web/themes/default/style.css
+++ b/interface/web/themes/default/style.css
@@ -1,5 +1,11 @@
+html, body{
+	height: 100%;
+	margin: 0;
+	padding: 0;
+}
+
 body{
-    margin: 0px auto;
+    /*margin: 0px auto;*/
     background-color: #ffffff;
     font-family: sans-serif;    
 }
diff --git a/locks/db-logs.lock b/locks/db-logs.lock
deleted file mode 100644
index 536ac36a73f12d992a0ac21f6523036a990b935e..0000000000000000000000000000000000000000
--- a/locks/db-logs.lock
+++ /dev/null
@@ -1,3 +0,0 @@
-This file is not used by Subversion 1.3.x or later.
-However, its existence is required for compatibility with
-Subversion 1.2.x or earlier.
diff --git a/locks/db.lock b/locks/db.lock
deleted file mode 100644
index 536ac36a73f12d992a0ac21f6523036a990b935e..0000000000000000000000000000000000000000
--- a/locks/db.lock
+++ /dev/null
@@ -1,3 +0,0 @@
-This file is not used by Subversion 1.3.x or later.
-However, its existence is required for compatibility with
-Subversion 1.2.x or earlier.