Re: [Nmh-workers] iCalendar support

[Oliver Kiddle]

David Levine wrote:
> 
> 2) For each switch, repl puts one pseudoheader in the draft of form:
> 
>        Nmh-mhbuild-TYPE: [ARGSTRING] file://FILE

What is the URL style file:// syntax needed for? Is it sometimes http or
something?

> Example 1, text/calendar:
> 1) repl switch           -converterarg text/calendar '-reply accept'
> 2) pseudoheader:         Nmh-mhbuild-text/calendar: -reply accept file://FILE
> 3) mhn.defaults entry:   mhbuild-converter-text/calendar: | mhical
> 4) mhbuild filters thru: mhical -reply accept
 
Is mhical generating a mime part to indiate acceptance of the
invitation to the originator once they receive your reply? Is adding the
appointment to your own calendar something you handle as part of mhshow?

Is such a long pseudoheader necessary, didn't we switch to just 'Attach'
for attachments. How about substituting the command instead of including
the mime-type in the header name:
  GenAttach: mhical -reply accept FILE

And what is the mime type of the converted file? Would it use file like
for normal attachments? text/calendar is what it matched in the message
being replied to; I don't know what calendar acceptances use but for the
feature to be flexible, the type of the converted text might need to be
different.

> Example 2, text/html:
> 1) (no repl switch)
> 2) pseudoheader:         Nmh-mhbuild-text/html: file://FILE
> 3) mhn.defaults entry:   mhbuild-converter-text/html: charset=%{charset}; w3m 
> -dump ${charset:+-I "$charset"} -O utf-8 -T text/html -cols 70 %F | par
> 4) mhbuild handles with: w3m -dump ${charset:+-I "$charset"} -O utf-8 -T 
> text/html -cols 70 FILE | par

For html or text parts, it'd be more useful to have the processing as
part of repl/forw itself when it prepares the initial draft and not in
mhbuild. If I want parts attached with mhbuild, I'd have no need to
convert them. repl needs to add the '> ' quotes and it could do the
iconv stuff internally.

Oliver