[nSLUG] Removing spaces from file names - note, long lines
odoepner at gmail.com
Fri Nov 14 11:21:04 AST 2014
I have to qualify what I meant regarding "localized file names":
I meant any kind of auto-magic transcoding or even auto-translation (using
locale dependent resource bundles) of file names based on the current users
locale. That would be a nightmare in so many ways.
What can make sense however is to allow the users to name files using
characters from their locale's default charset. And that is already
implemented in all Linux filesystems that I know of (maybe with some
limitations for older reverse-engineered ones).
But even with non-ASCII file names I would be very cautious.
For easy exchange and robustness, I would stick to ASCII only filenames.
And always use UTF-8 locales.
On Fri, Nov 14, 2014 at 11:13 AM, Oliver Doepner <odoepner at gmail.com> wrote:
> The only area where I know Linux desktops / userland does something like
> "user friendly file name translation" are the "logical" folder names from
> the Freedesktop.org set of standard user folders ("Documents", "Downloads",
> But that is purely a desktop environment level thing, not on the file
> system level.
> On Fri, Nov 14, 2014 at 11:09 AM, Oliver Doepner <odoepner at gmail.com>
>> Localized file names? Are you kidding?
>> I am sure Linus will never accept such non-sense into his kernel tree.
>> Which lets me sleep soundly at night. :o)
>> On Thu, Nov 13, 2014 at 10:49 AM, George N. White III <gnwiii at gmail.com>
>>> On Wed, Nov 12, 2014 at 10:41 PM, Hatem Nassrat <hnassrat at gmail.com>
>>>> Hi Vlado,
>>>> On Wed Nov 12 2014 at 10:32:22 PM Vlado Keselj <vlado at dnlp.ca> wrote:
>>>>> This one-liner does not do the same operation. My main goal was
>>>>> to turn one or any chosen filenames that look like:
>>>>> Joe, Jack & Jane's document (version # 1) [draft].doc
>>>>> into something like:
>>>> Saw your perl, honestly didn't mentally fully compile it, but it seems
>>>> like it would do the transformation as described. What is the reasoning /
>>>> requirements for the use of this kind of transformation, is it so you can
>>>> revert back to the original name?
>>> It might be useful to mention the possibility of replacing the file name
>>> with the inode number or (as in git) SHA-1 hashes. You can keep a
>>> database to associate all sorts of metadata with inode numbers or hashes,
>>> including "original_name", "8dot3_name", "ascii_name", "UTF-8_name", etc.
>>> Many years ago mainframes were limited to short filenames and about 64
>>> characters (uppercase, numbers, and a few punctuation symbols). Libraries
>>> to support ASCII names began to appear, so you could live in an "ASCII"
>>> namespace while the system used simple names. This did require a translation
>>> tool to figure out the ASCII version of a name mentioned in system logs.
>>> In many environments it would be helpful to allow the filenames visible
>>> to users change with the locale.
>>> George N. White III <aa056 at chebucto.ns.ca>
>>> Head of St. Margarets Bay, Nova Scotia
>>> nSLUG mailing list
>>> nSLUG at nslug.ns.ca
>> Oliver Doepner
>> Software Engineer
> Oliver Doepner
> Software Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG