You wrote: > i noticed that the provided mhl.* and scan.* and repl*comps aren't > uniform in their use of "decode" for address fields. for instance, To > and Cc headers don't ever use it, and From and Reply-to are > inconsistent as well. is there any reason not to simply use it > everywhere?
We probably don't really want to use decode when constructing replies because they would need to be reencoded when constructing the final header for the reply: the headers need to be ASCII and nmh has no support for encoding. Even with support for encoding, we would be decoding to the current locale which may not support the characters required. Perhaps not something to worry about with UTF-8 being more common but I'd prefer to have to see the unencoded string in my editor than for the name of my recipient to get mangled. Oliver _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers