Re: 100% Java Subversion client library

Hi Patrick,

> Not really, Everything is just UTF, since thats how subversion and java handles texts.

Well, I guess, the text file content is not tunneled through the
java-bindings. So how I can tell it what encoding the text is written? I
could configure a decent text editor (or IDE) to write the text in quite
any encoding. How the java-bindings (or subversion) knows it?

> See above. I have never tried japanese file names, but I see no reason why that should not work.

The problem in CVS is, that the file names are tunnelled byte-wise to
the CVS server (1 byte == 1 character). The question is, when I commit a
file "äöüÄÖÜß.txt" (German umlauts) on Windows and check it out on Unix,
  Mac OS or OS/2, will I get the same file name or a crippled one?

> Only implementing the svn:// protocol will make the library much less usefull, since many public svn repositories are only accessable via http:// and https://

Please see my comments in a previous mail.

Just curious, what port svn:// is using?

--
Best regards,
Thomas Singer
_____________
smartcvs.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org