[Owncloud] special characters in filenames

Thomas Müller thomas.mueller at tmit.eu
Thu Aug 2 13:31:38 UTC 2012


Am Donnerstag, dem 02.08.2012 um 15:22 schrieb Frank Karlitschek:
> 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?
>

On the server:
We could save the real file name and path in the database together with a unique identifier (e.g. GUID).
This GUID can be used to save the file on the server's file system.

On the client:
Well we can convert the file name as close as possible to the original file name. (I know this sounds easier than it actually is ;-) )
Because of the file name is no longer the identifier this should be of lesser problem if the file name cannot be used properly.

Side effects:
The files on the server actually become totally useless.
E.g. some people access the files via ftp.
>From my point of view this is okay as nobody should mess around with the files under OC control.
But we might get some bad feedback.

Tom
 
> What do you think?
> 
> Frank
> 
> 
> 
> 
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud



More information about the Owncloud mailing list