Fix whitespace

Merge pull request #68 from philippschaefer/patch-1 ...

Parse SVN log as XML

Add and update Russian translate

Minor cleanup, exception handling for xml parsing, coding guidelines compliance ...

- compliance with coding guidelines
- added exception handling for xml parsing
- removed unnecessary echo </pre> after return logic in import_full
- removed unnecessary loop and checking for numerical return value of process_svn_log_xml (this seems to be not required for a while since the process_svn_log in the current form does not return a numerical value either)

resolved copy paste bug ...

replaced erroneus $$ by $

Use svn log with xml output to resolve encoding issues (as reported in issue #62) ...

As reported in issue #62 there are troubles with svn log and character encoding. It is AFAIK impossible to force an encoding in the svn command line tool for svn log. However, svn log with the --xml option will generate utf-8 encoded output (and is more save and easier to parse IMHO).

Spanish translation

Catalan translation

Added API_KEY to post-commit hook template

Updated contact url

Updated contact email

Update copyrights

Fixed invalid XHTML bits ...

Signed-off-by: Philipp Beckmann <philippbeckmann@pabnet.de>

Don't discard changesets with no branch

Fix #142: Added German translation strings ...

Signed-off-by: John Reese <jreese@leetcode.net>

Fix #135: Added French translation for core+websvn ...

Signed-off-by: John Reese <jreese@leetcode.net>

Fix SVN debugging output to include final </pre>

Separate remote import page from user imports ...

Due to complexities of trying to have both user-initiated imports and
remote imports handled in the same page, the import process has been
split into two separate use cases.  pages/import.php is now specifically
for use by the remote import process, while pages/repo_import_latest.php
remains for usage by authenticated MantisBT users.

This will require that all cronjobs or post-commit hooks that triggered
a remote import be updated to point to the new import url.  Framework
version has been bumped accordingly.

Fix incorrect SVN log parsing regexes ...

When importing a repository with non-standard paths, the parsing regexes
were incorrectly looking for filenames without a leading slash, and also
not looking for filenames with a slash after the branch/tag path.

Also, when importing standard repositories where the trunk/branches/tags
folders were not named in complete lower case, the regexes and logic for
finding those paths has been updated to be case-insensitive, and to
prefer using the same case as found in the repository for trunk.

Fix #126: Sort SVN changesets by numeric revision ...

To better handle merged SVN repositories, it is necessary to retrieve
the latest changeset from the database based on integer revision number
rather than by timestamp.  This will prevent an "infinite loop" of
repeatedly importing the same changesets in cases where the latest
revisions were actually committed before earlier changesets.

Using ANSI SQL's `CAST(? AS DECIMAL)` as it seems to be compatible with
the most database platforms.

Add a bit of debug output for SVN imports/checkins

Fix #109: Add option to use Windows start command

Re-licensed the project under the MIT license

Fix #99: Use svn_binary in svn_check

Fix language string to mention correct SVN version

Fix #86, #94: Added SVN command argument configs ...

Extended the SVN configuration section to include a checkbox for
trusting SSL certificates, as well as a generic textbox to specifying
additional command arguments to the SVN binary.  Together, these two
options should allow repositories to be imported via HTTPS/SSL, as well
as additional flexibility for system admins.

Issue #97: SVN configuration uses new Source API

Fix #97: Refacter core SVN into shared codebase ...

Created base SVN plugin with the shared SVN code from WebSVN and SFSVN
plugins, and then modified the previous plugins to inherit from the new
base plugin.  This will end the previous need to constantly replicate
changes between the two SVN plugins.

Currently, the only way to modify shared SVN configuration is to have
the base SVN plugin installed, but this is a task for a different
commit.