From: Ruthard Baudach <ruthard.baudach@web.de>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Characters not properly displayed
Date: Mon, 03 Nov 2014 16:20:53 +0100 [thread overview]
Message-ID: <1415027752-sup-8158@ruthard-lappi> (raw)
In-Reply-To: <969efaf62c026a8cfe961b16d8f72c@ip-10-0-3-28>
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
>== Auszüge aus der Nachricht von Guillaume Brogi vom 2014-11-03 05:39:
> Hello all
> I hope this issue hasn't been reported yet. I don't have access to a
> browser so I couldn't look on github, I went on irc though and no one had
> seen this issue before. Thanks a lot to sankey who took the time to check
> github issues for me.
> The issue appears in inbox-mode and thread-view-mode for drafts. I haven't
> seen it for proper mails. Accented characters are displayed as filled in
> losanges with a question mark inside. There are two losanges per accented
> character. This is typical of encoding problems. In the editor and in
> resume-mode, the characters are displayed properly. Japanese and Korean
> glyphs are also affected.
> Steps to reproduce:
> Compose a message with accented characters in the subject or at the
> beginning of mail. Save as draft and go back to inbox mode. Observe weird
> characters. Go to thread-view-mode. Observe weird characters again.
> If there's any questions, I'm also present on the irc channel as guiniol
> --
> guiniol
>
Yes, I observed the same for German umlauts. Incoming mails are
displayed correctly, this affects *only* drafts as long as they are
drafts. after sending them, they are displayed properly.
--
Emails bitte verschlüsseln und signieren.
Meine PGP-Id: AC5AC6C2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-03 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 4:39 Guillaume Brogi
2014-11-03 15:20 ` Ruthard Baudach [this message]
2014-11-03 20:04 ` [sup] " Matthieu Rakotojaona
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=1415027752-sup-8158@ruthard-lappi \
--to=ruthard.baudach@web.de \
--cc=supmua@googlegroups.com \
/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