On Thu, Sep 8, 2011 at 1:49 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Thu, Sep 8, 2011 at 2:30 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>> On Thu, Sep 8, 2011 at 2:27 PM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>>> Why does the command-line client work? Does it not also use the locale
>>> encoding for its diff headers? At any rate, consistency between the
>>> behaviors of the relevant Java and C APIs seems like a reasonable goal.
>> I have not tested exhaustively, but my OSX Terminal says UTF-8 is the
>> default encoding. Maybe that is why I do not see it from command
> FWIW, even if I explicitly set LANG=en_US.UTF-8 before launching Java,
> and even if I change all of the JVM properties to make UTF-8 the
> default encoding for files for the JVM, I still get this error. So
> JavaHL does not seem to pickup the environment in the same ways as the
> command line.
FWIW, JavaHL is just using SVN_APR_LOCALE_CHARSET, which is a magic
number inside of APR. I've no idea what it actually does.
uberSVN: Apache Subversion Made Easy
Received on 2011-09-08 21:24:40 CEST