>I think parameters can be ignored at this level, but as a reader getting
>an overview I'd be interested to know if it's a simple replacement with
>a constant '?' or more like
>
>$ recode utf-8..us <<<‘’“”«»…£€¢
>''""<<>>...lbEURc
Well ... I understand your view, but I still think it's mor
>Ken, should we move the mhparam details to mhparam(1) and then
>add pointers to the three man pages that refer to iconv(3)?
I am thinking ... yes. mhparam(1) should have specific explanations about
things that refer to build-time options, like cyrus-sasl, tls, and (now)
iconv, since they're a li
Hi David,
>The default format used by scan(1) will automatically decode MIME-
>encoded headers. If you have a custom scan format, see the examples
>provided with thenmhdistribution(foundinthe
>"/usr/local/nmh/linux-gnu/etc" direc
Norm wrote:
> Would somebody tell me how to read
>
>http://git.savannah.gnu.org/cgit/nmh.git/tree/man/mh-mime.man
>
> as a man page.
You could get close by downloading that file and viewing it
with: "man [-l] mh-mime.man". But that won't have the
substitutions that nmh does at build t
Download it using the "plain" link, then man ./mh-mime.man
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Would somebody tell me how to read
http://git.savannah.gnu.org/cgit/nmh.git/tree/man/mh-mime.man
as a man page.
Norman Shapiro
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Hi Lyndon,
> >SEE ALSO
> >nmh(7), mhbuild(1), comp(1), repl(1), whatnow(1), mh-format(5)
> >
> > Missing full stop.
>
> It has never been the convention to include a period on the end of a
> SEE ALSO list of that type.
I did go and check first.
$ curl -sS http://www.plan9.bell-la
Hi Ken,
> > In this case a substitution character will be used for the
> > characters that cannot be converted.
> >
> > It's always the same character used for all ones that couldn't be
> > converted? Or does it mean turning “” into ""?
>
> Weeell … I didn't want to get TOO specific, but
