I attempted a SVB check out and got an error regarding UTF-8 encoding conversion.
svn: Can't convert string from 'UTF-8' to native encoding:
svn: q-gears/trunk/output/data/game_data/battle/?\208?\154?\208?\190?\208?\191?\208?\184?\209?\143 battle.lua
Reading a bit through the manual for SVN I found this tid bit
Subversion tries hard not to limit the type of data you can place under version control. The contents of files and property values are
stored and transmitted as binary data, and the section called “File Content Type” tells you how to give Subversion a hint that
“textual” operations don't make sense for a particular file. There are a few places, however, where Subversion places restrictions on
information it stores.
Subversion internally handles certain bits of data—for example, property names, pathnames, and log messages—as UTF-
8-encoded Unicode. This is not to say that all your interactions with Subversion must involve UTF-8, though. As a general rule,
Subversion clients will gracefully and transparently handle conversions between UTF-8 and the encoding system in use on your
computer, if such a conversion can meaningfully be done (which is the case for most common encodings in use today).
In WebDAV exchanges and older versions of some of Subversion's administrative files, paths are used as XML attribute values,
and property names in XML tag names. This means that pathnames can contain only legal XML (1.0) characters, and properties are
further limited to ASCII characters. Subversion also prohibits TAB, CR, and LF characters in path names to prevent paths from be-
ing broken up in diffs or in the output of commands such as svn log or svn status.
While it may seem like a lot to remember, in practice these limitations are rarely a problem. As long as your locale settings are
compatible with UTF-8 and you don't use control characters in path names, you should have no trouble communicating with Sub-
version. The command-line client adds an extra bit of help—to create “legally correct” versions for internal use it will automatic-
ally escape illegal path characters as needed in URLs that you type.
Anyhow one of the file names in the repository gave SVN a hiccup looks like on my end. It appears to be a script file in battle (likely your battle menu). I am using Linux so it may be that my native encoding of text under linux doesn't like whatever file name choice you used.
Cyb