Re: [Gnu-arch-users] Re: How does arch/tla handle encodings?

[Esben Mose Hansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 28 August 2004 00:31, Michael Poole wrote:

Having lurked at this discussion for some time (I sometimes have to use 
EBCDIC, the worst encoding ever invented). So I wanted to throw my "solution" 
on the table :)

This is what we need, in my opinion.

1. Filesystem support for extended attributes (many file systems support this)
2. Standard utilities support for extended attributes (cp copies EA etc., tar 
stores EA, etc.)
3. A standard for specifying encoding in EA.
4. Make diff, patch and friends aware of this and act accordingly.
5. Make tla store these extended attributes and changes together with the 
files and changessets.

So in short, tla's job would be 5). As I believe tla would need to do 5) in 
any case, this should not be so atrocious, no? And then those of us who have 
to deal with these issues can work with getting 3 and 4 happen :)

For extra point, one could sit down and think about 
6) tla handles conflicting encodings.

In my humble opinion, 6) should be handled by providing an appropriate hook 
(which would be configured to either ignore, convert or refuse, I suppose.)

- -- 
regards, Esben

Homepage: http://www.mosehansen.dk
Signature fingerprint at http://www.mosehansen.dk/about
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBMFYvrfnftt13wXIRArEgAJ9EEzEjV0OaAz6aVSFgckPEZ4nZCACfdt4T
7v7KxIFYE2vu8Y8WdsMiz+k=
=OEGn
-----END PGP SIGNATURE-----