Github messages for mblaze
 help / color / mirror / Atom feed
Subject: Re: mshow/mflow doesn’t display EBCDIC-encoded bodies correctly
Date: Sun, 23 Jun 2019 19:49:46 +0200	[thread overview]
Message-ID: <20190623174946._dZzTkaE-JgDUUsaLNEhzOMraEGXf-zGfkTKZvvOR9g@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

New comment by qsuscs on mblaze repository
I just realized that as of commit 6710fd9 (which is older than this issue), this should not happen.  Unless one uses filters: in that case, mshow does not convert its output to UTF-8.  So indeed, when one uses e. g. mflow as filter for text/plain, mrecode should be added to the filter chain.

I’m not sure whether mshow _should_ behave this way, but it does, anyway.

           reply	other threads:[~2019-06-23 17:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190623174946._dZzTkaE-JgDUUsaLNEhzOMraEGXf-zGfkTKZvvOR9g@z \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).