> We'd like to use SVN in a Macintosh/Windows environment.
> We'd need two kind of client side conversion that's currently not
> supported by SVN:
> 1. Some kind of codepage translation, because some non ASCII characters
> are represented differenty on the platforms.
> 2. MacOS binary files contains metadata that have to be encoded.
I'm not certain about #1, but are you referring to Resource Forks in
#2? If so, I'm -1 on accepting any patches for that--it's my
understanding that resource forks are being used less and less these
days.
> I think that probably both changes would be too proprietary to become
> part of the standard SVN. If there would be an API in libsvn_wc to add
> such translations that would be more than fine for us.
> [ Note that most MacOS CVS clients has some sort of translation that
> equivalent to (1) and (2) ]
Ah, I see that you've already suggested to keep your change out of the
mainline Subversion. In that case, we're back to the client-side hooks
discussion which I'll defer to Greg Hudson.
> Ther's already some client side translation done in SVN:
> - keyword substitution,
> - lineend translation,
> - unix execution bit translation to svn metadata
>
> Is there any plan to unify these kind of client side translations? For
> example: local encoding -> UTF-8 conversion could be done in such
> translator.
>
> I'd imagine something like the API bellow in translate.h:
>
> translate_client_to_server
> translate_server_to_client
> add_new_translation (client_to_server_callback,
> server_to_client_callback)
>
> Is there any plan to do this thing? Would it be a welcomed change?
> (Post svn 1.0)
Not that I know of.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 29 15:22:01 2002