-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 17/07/2011 20:57, Gabriel Kerneis a écrit : > Hi, > > this is a third attempt at using utf-8 whenever possible in darcs send.
I don't understand the point of this bundle: what problems are solved by always assuming the mail content is utf-8? Are we unable to reliably decode encoding, or is there a deeper problem? If it's just a problem of detecting the encoding, I'd rather have: > - if mail is made of ascii characters, send with content-type charset > set to ascii and ignore locale completely, ok > - if mail contains invalid utf-8 characters, propose to either abort > (and save mail content in a file) or ignore the error and send with > content-type charset set to utf-8 anyway (no support for other > charset when sending), ask the user to abort or input the encoding at that point (defaulting to utf-8 or best, locale) > - if mail is valid utf-8, send with content-type charset set to utf-8; > additionnally print a warning if current locale is not recognised as > utf-8 (but do not propose to abort, assuming what looks like utf-8 is > utf-8). > ok if there still is a way to abort at that point by using ctrl-C, else the warning is just a pied-de-nez to the user, and that's undarcsish. Florent -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk4kPMYACgkQTCPcDztjGo4CRACfZWKH0zT/cGlZx+hynbi+2xRc meAAn3BshBsDv2yr787SXvCy0y+dsSgU =rMsj -----END PGP SIGNATURE----- _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
