From: tyberius_prime@coonabibba.de (Tyberius Prime)
Subject: [sup-talk] UTF-8 woes
Date: Thu, 22 Jan 2009 17:16:27 +0100 [thread overview]
Message-ID: <1232640702-sup-1568@h984274.serverkompetenz.net> (raw)
In-Reply-To: <1232602097-sup-3993@traj>
Hi,
I'm also struck by Sup's UTF-8 weirdnesses,
and can't get German szetz to display correctly
(and they mess with the line width as well).
The other umlauts work though, and I don't know why.
I'd also appreciate work on sending utf-8,
though subject encoding is a weird beast.
(And my ruby skills are 'by transfer' only as well).
So long,
Tyberius Prime
> 2. something about the message text, probably missing
> "Content-Transfer-Encoding: 8bit" makes my emails with latvian
> characters explode with ugliness for my poor recipients on Outlook;
>
> 3. The minor glitch that the Sup's display is slightly messed up, if
> the message contains multi-byte characters in headers -- fixed either
> very nicely by extending String with length_utf8 (and substr_utf8, and
> others as needed) function, and replacing s.length with s.length_utf8
> in lib/sup/buffer.rb or by going the ugly way of assuming that all
> strings are and will be utf-8 and dropping a horrendous monkeypatch
> into the lib/sup/util.rb with
>
> class String
> + def length
> + self.scan(/./u).size
> + end
>
>
> To see what exactly is wrong with the sending of mails I compared of
> how the same mail is sent by mutt and how -- by sup. You can see the
> mails here: http://spicausis.lv/sup/ where mail-mutt.txt is good,
> mail-sup.txt is bad.
>
> My ruby skills are non-existant yet, but I guess I'll try to whip up
> patches for these things today, if somebody with more ruby and sup and
> mta shizzle don't beat me to that.
>
>
> Cheers,
>
> Einar Lielmanis
prev parent reply other threads:[~2009-01-22 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 6:02 Einars Lielmanis
2009-01-22 16:16 ` Tyberius Prime [this message]
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=1232640702-sup-1568@h984274.serverkompetenz.net \
--to=tyberius_prime@coonabibba.de \
/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