[Owncloud] special characters in filenames

[Jan-Christoph Borchardt]

The discussion seems to have veered off the original question.

How it should be handled (regardless of any technical implementation
difficulties):
»Don’t sync at all« is not an option. Neither is not letting people
upload files with special characters or warn them about it.
Can the ownCloud server have a database in the backend, mapping
converted filenames to actual filenames? So that supported systems are
synced the whole filename, and unsupported ones are given the
appropriate converted one? Does that make sense? Or does it not work
because WebDAV, FTP etc does not go through the database?

The thing with WebDAV, FTP and all that stuff is – we should
discourage people from using WebDAV or FTP or anything manually. Just
use the web interface or the clients.



On Thu, Aug 2, 2012 at 6:22 AM, Frank Karlitschek <frank at owncloud.org> wrote:
> Hi everyone,
>
> we have an interesting question where I would love to get some more opinions.
>
> The question is how ownCloud should handle special characters in filenames. ownCloud itself should work always with UTF8 and do proper encoding so that ownCloud can work with all possible characters.
> The problems are the underlying filesystems.
>
> So the ownCloud server can run on Windows/Linux/Mac servers with lot´s of different filesystems and we have clients for Windows/Linux/Mac/iOS/Android with more different filesystems. All this filesystems have limitation for allowed characters and handling of uppercase/lowercase filenames.
>
> So what can/should ownCloud do if someone want´s to sync a file with a special character that´s supported on one platform but not on another?
> Should be change the filename? Or don´t sync at all?
>
> What do you think?
>
> Frank
>
>
>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud