> Uday,
>
> I think John's comments summed up things better then my attempt. However,
> note that there are two issues here for me. I can get use to the new
> behavior or rebind the key. However, there is also an issue with the MIME
> part VM is selecting to send as plain text which may need improvements as
> well.
As I mentioned in my response to John, it does look like
`vm-forwarding-digest-type' should be respected by `vm-forward-message'.
As for the calendar issues, can you open a new bug report and attach the
message that you would like to forward?
(There are some anomalies with the `text/calendar' MIME type because it is
inconsistent. text types are meant to be displayed to the user but
`text/calendar' is meant to be processed by a program. It should have really
been named `applicationc/calendar'.)
As for Google producing bad `text/plain' content, please do complain to them
if there is a way to do so!
Tim Cross writes:
> Uday,
>
> I think John's comments summed up things better then my attempt. However,
> note that there are two issues here for me. I can get use to the new
> behavior or rebind the key. However, there is also an issue with the MIME
> part VM is selecting to send as plain text which may need improvements as
> well.
As I mentioned in my response to John, it does look like digest- type' should be respected by `vm-forward- message' .
`vm-forwarding-
As for the calendar issues, can you open a new bug report and attach the
message that you would like to forward?
(There are some anomalies with the `text/calendar' MIME type because it is calendar' .)
inconsistent. text types are meant to be displayed to the user but
`text/calendar' is meant to be processed by a program. It should have really
been named `applicationc/
As for Google producing bad `text/plain' content, please do complain to them
if there is a way to do so!
Cheers,
Uday