all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 12055@debbugs.gnu.org
Subject: bug#12055: Re: Re: Re: bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal
Date: Fri, 27 Jul 2012 00:40:22 +0200	[thread overview]
Message-ID: <CAH8Pv0hAWLB7r8kBjNxme_1bFJwX-srnH=0TL6yRftnRBxqwbQ@mail.gmail.com> (raw)
In-Reply-To: <83k3xqjnns.fsf@gnu.org>

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

FWIW, another experiment that produces unexpected results:

The attached screenshot shows how two Emacs instances (GUI and
non-GUI) show the contents of a test file (previously written by me
and saved to disk).

IIUC, this time the input method is irrelevant, since the text has
been read from a file (not the keyboard).

As you can see in the modelines, both instances of Emacs have selected
the latin-1 coding system, but the non-GUI instance fails to show the
characters correctly (and not only "á" and "é").

I don't know if this problem has the same root than the original.  If
not, I could file a separate bug report.

-- 
Dani Moncayo

[-- Attachment #2: img2.png --]
[-- Type: image/png, Size: 40071 bytes --]

  reply	other threads:[~2012-07-26 22:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 12:13 bug#12055: 24.1.50; Characters "á" and "é" are not correctly displayed on a Windows terminal Dani Moncayo
2012-07-26 16:13 ` Eli Zaretskii
2012-07-26 16:24   ` Juanma Barranquero
2012-07-26 16:42     ` bug#12055: " Eli Zaretskii
2012-07-26 16:49       ` Juanma Barranquero
2012-07-26 17:18         ` bug#12055: " Eli Zaretskii
2012-07-26 18:09           ` Eli Zaretskii
2012-07-26 18:42             ` Juanma Barranquero
2012-07-26 18:29           ` Juanma Barranquero
2012-07-26 20:03             ` bug#12055: " Eli Zaretskii
2012-07-26 22:40               ` Dani Moncayo [this message]
2012-07-27  6:45                 ` bug#12055: " Eli Zaretskii
2012-07-27  8:35                   ` Dani Moncayo
2012-07-27  9:04                     ` bug#12055: " Eli Zaretskii
2012-07-27 15:12                       ` Eli Zaretskii
2012-07-27 16:46                         ` Jason Rumney
2012-07-27 18:03                           ` Eli Zaretskii
2012-07-27 18:22                             ` Eli Zaretskii
2012-07-27 23:45                         ` Juanma Barranquero
2012-07-28  1:12                         ` Dani Moncayo
2012-07-28  8:04                           ` bug#12055: " Eli Zaretskii
2012-07-28 10:06                             ` Eli Zaretskii
2012-07-28 11:55                               ` Dani Moncayo
2012-07-28 12:23                                 ` bug#12055: " Eli Zaretskii
2012-07-28 12:49                                   ` Dani Moncayo
2012-07-28 15:02                                     ` bug#12055: " Eli Zaretskii
2012-07-28 12:30                                 ` bug#12055: " Eli Zaretskii
2012-07-28 13:57                               ` Dani Moncayo
2012-07-28 16:07                                 ` Juanma Barranquero
2012-07-28 16:12                                   ` Dani Moncayo
2012-07-28 16:11                               ` Juanma Barranquero
2012-07-28 16:44                                 ` bug#12055: " Eli Zaretskii
2012-07-28 17:01                                   ` Eli Zaretskii
2012-07-26 16:44     ` Dani Moncayo
2012-07-28 14:12 ` Dani Moncayo
2012-07-28 15:01   ` bug#12055: " Eli Zaretskii
2012-07-28 15:23     ` Dani Moncayo
2012-07-28 15:34       ` Dani Moncayo
2012-07-28 16:27         ` bug#12055: " Eli Zaretskii
2012-07-28 15:35       ` Eli Zaretskii
2012-07-28 15:46         ` Dani Moncayo

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='CAH8Pv0hAWLB7r8kBjNxme_1bFJwX-srnH=0TL6yRftnRBxqwbQ@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=12055@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.