Just off the top of my head, I would look into these:
1) When files are added to your area, you can probably get the source system
from the HTTP header info. Rename the files to UTF-8 names based on this
setting.
2) Rename all files to encode >127 chars as %xx (like a URL encoding), then
you should not having any problems with subversion trying to convert file
names to UTF8. Or, just strip out all highbit characters from the names.
There are many options.
On Sun, Nov 22, 2009 at 6:55 AM, Peter Koellner <peter_at_asgalon.net> wrote:
> Hi!
>
> I have a medium size Drupal web application project the PHP source part of
> which I am managing with subversion. The application is running on a
> SuSE 10 server which I unfortunately can't upgrade at present for some
> other compatibility reasons, so I seem to be stuck with subvrsion
> 1.4.4 if I do not want to replace the packaged version with a
> standalone version compiled from latest sources.
>
> The trouble seems to be:
>
> There is a public upload directory named "files" in the web
> application root directory. People will upload their files to this
> directory from all types of client systems, especially the crappy ones
> from MS. Filenames therefore vary hugely and do not follow any
> conventions or standards.
>
> So everytime I do something with subversion in the root directory, I
> get a message such as:
>
> svn: Valid UTF-8 data
> (hex: 31 2e 46 43 5f 4e 75)
> followed by invalid UTF-8 sequence
> (hex: df 62 61 75)
>
> which is perfectly expectabla when files come with obscure filename
> encodings from hell. The files directory naturally is NOT kept under
> version control.
>
> Of course I tried to add the files directory to svn:ignore, but it does
> not work. svn complains about the UTF-8 problems anyway. I guess the
> "ignore" part comes at a later stage after looking into the directory
> and stumbling over the filenames.
>
> So normally I resolve to do something like
>
> svn update [^f]*
>
> to do the update on all sane directories, but now I
> have to switch the branch from trunk to something else on the live
> system. With svn switch, this trick does not seem to work.
>
> Does anybody have any idea how to resolve this? Could I make this work with
> a
> recent version of subversion?
>
>
> --
> peter koellner <peter_at_asgalon.net>
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423047
>
> Please start new threads on the <users_at_subversion.apache.org> mailing
> list.
> To subscribe to the new list, send an empty e-mail to <
> users-subscribe_at_subversion.apache.org>.
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423099
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-22 20:44:13 CET