From: marko.myllymaki@iki.fi (Marko Myllymäki)
Subject: [sup-talk] char. encoding problems - garbled output
Date: Fri, 25 Jan 2008 14:09:53 +0200 [thread overview]
Message-ID: <1201262947-sup-9132@sieni> (raw)
In-Reply-To: <1200763427-sup-2564@south>
Excerpts from William Morgan's message of Sat Jan 19 19:25:00 +0200 2008:
> Does the following patch help?
Sorry, I'm really Sup-newbie and I don't know how to apply these patches yet :)
... figuring it out later.
I think the problems are mainly caused by the wide characters (whatever that
means, I guess multibyte codes). I'm using Sup as my main email-client now, 0.4
works quite nicely. When I have time I try to dig into these character things
and read more your devel notes.
next prev parent reply other threads:[~2008-01-25 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 12:51 Marko Myllymäki
2008-01-19 17:25 ` William Morgan
2008-01-25 12:09 ` Marko Myllymäki [this message]
2008-01-30 17:24 ` 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=1201262947-sup-9132@sieni \
--to=marko.myllymaki@iki.fi \
/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