On Tue, Feb 26, 2008 at 08:46:15PM +0100, Nicolas Mailhot wrote: > > Also consider that package names define the file set that is to > > bemirrored and you thus need to assume that all mirrors properly > > support utf on their filesystems and their ftp/web/rsync servers. > > Is this really a problem? File systems do not interpret file names, so > they are going to store byte strings as they get them. Which is the problem. Since this is not any metadata you store anywhere it is something defined locally. And if you mirror the raw UTF8 filenames onto a mirror that has set local policy to be latin1 the web server will serve funny ~A names. There are many issues with filename encoding otherwise there wouldn't exist any tools like convmv which seems to be still widely used and had an update release just a month ago: http://www.j3e.de/linux/convmv/man/ BTW it quotes NFS4 and JFS as being encoding aware. -- Axel.Thimm at ATrpms.net
Attachment:
pgpuDmAG3bJwm.pgp
Description: PGP signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
