> I would be interested in your usecase though since a ':' is a > reserved character > in just about everything that could think of that would be exposed > as a "name". This is data coming from our older legacy repository, which doesn't use namespaces. I'll just use %3A for now.
i see...
For general use when eg importing existing filesystem data, I guess it would be appropriate to use URLEncode on filenames.
well, that's certainly a simple way to deal with it. the only drawback is that you automatically encode characters that do not need encoding. since i would not expect ':''s in (windows & mac) filesystems the problem should not exist in a typical filesystem import. regards, david
