From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] utf patch needs work, i think
Date: Sat, 30 May 2009 17:59:51 -0700 [thread overview]
Message-ID: <1243731497-sup-5619@entry> (raw)
In-Reply-To: <1243553511-sup-472@ntdws12.chass.utoronto.ca>
Reformatted excerpts from Ben Walton's message of 2009-05-28:
> ...a followup on the list makes me wonder if this isn't actually a sup
> thing, but a weird encoding 'joke' by the poster. Even if the body
> display wasn't a sup bug, the name is still munged up.
I have the same message. I'll play around with it... I suspect there's
something like a tab or a weird character coming out of the decoding
(which appears to be some non-utf16 text claiming a utf16 big-endian
encoding) that is screwing with Ncurses.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-05-31 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 19:32 Ben Walton
2009-05-28 23:32 ` Ben Walton
2009-05-31 0:59 ` William Morgan [this message]
2009-06-02 14:54 ` William Morgan
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1243731497-sup-5619@entry \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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