all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Peter Dyballa <Peter_Dyballa@Freenet.DE>
Cc: 4157@emacsbugs.donarmstrong.com
Subject: bug#4157: Re: bug#4157: 23.1.50; faulty character characterisation for ä
Date: Thu, 27 Aug 2009 15:52:25 +0900	[thread overview]
Message-ID: <tl7ws4p7npy.fsf@m17n.org> (raw)
In-Reply-To: <BB0E3F43-9DA7-42FB-B4F4-63AABC2719DF@Freenet.DE> (message from Peter Dyballa on Wed, 26 Aug 2009 00:19:17 +0200)

In article <BB0E3F43-9DA7-42FB-B4F4-63AABC2719DF@Freenet.DE>, Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> > Please try to load ucs-normalize and set
> > file-name-coding-system to utf-8-hfs.  You should see file
> > names correctly by precomposed characters as "ä".

> When I copy a line from a dired buffer with a composed character  
> taken from another font into *scratch* buffer and then apply on the  
> marked file name ucs-normalize-HFS-NFC-region, then the foreign glyph  
> is changed to one from the default font. Automatically this does not  
> happen in dired buffer, although global-auto-composition-mode and  
> auto-composition-mode are both t.

Strange.  On GNU/Linux, I set file-name-coding-system to
utf-8-hfs, create a new file "ä" by:
  ESC : (write-region "test" nil "ä") RET
I confirmed that the file name is surely the two char
sequence of "a" and "̈" by another emacs.

Then M-x dired shows that file name by precomposed character
"ä" (LATIN SMALL LETTER A WITH DIAERESIS).

That means utf-8-hfs does convert the sequence "a" and "̈"
to/from "ä".  I have no idea why it doesn't work in your
environment.

> And ucs-normalize is auto-loaded!

When is it loaded?

---
Kenichi Handa
handa@m17n.org





  reply	other threads:[~2009-08-27  6:52 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-16  2:19 bug#4157: 23.1.50; faulty character characterisation for ä Peter Dyballa
2009-08-18  1:09 ` Kenichi Handa
2009-08-18 13:40   ` Peter Dyballa
2009-08-19  0:23     ` bug#4157: " Kenichi Handa
2009-08-19 22:47       ` Peter Dyballa
2009-08-24 11:30       ` Peter Dyballa
2009-08-24 12:22         ` bug#4157: " Kenichi Handa
2009-08-24 15:21           ` Peter Dyballa
2009-08-25  0:46             ` bug#4157: " Kenichi Handa
2009-08-25  7:51               ` Peter Dyballa
2009-08-25 22:19           ` Peter Dyballa
2009-08-27  6:52             ` Kenichi Handa [this message]
2009-08-27  8:50               ` bug#4157: " Peter Dyballa
2009-08-27 11:33                 ` bug#4157: " Kenichi Handa
2009-08-27 12:38                   ` Peter Dyballa
2009-08-28 19:27           ` Peter Dyballa
2009-08-31 21:11           ` Peter Dyballa
2009-09-01  0:04             ` Stefan Monnier
2009-09-04  0:58               ` Kenichi Handa
2009-08-22  4:09 ` Stefan Monnier
2009-08-22  8:50   ` Peter Dyballa
2009-08-23  1:49     ` Stefan Monnier
2009-08-23  9:57       ` Peter Dyballa
2019-10-09 14:29 ` Stefan Kangas
2019-10-09 18:48   ` Eli Zaretskii
2019-10-09 19:47   ` Stefan Monnier
2019-10-09 22:42     ` Peter Dyballa
2019-11-11  1:49       ` Stefan Kangas
2019-11-11 16:36         ` Peter Dyballa
2019-10-10  0:10     ` Stefan Kangas
2019-10-10  7:20       ` Eli Zaretskii
2019-10-10 10:36         ` Stefan Kangas
2019-10-10 11:20           ` Eli Zaretskii
2019-10-10 11:52             ` Stefan Kangas
2019-10-10 12:39               ` Stefan Kangas
2019-10-10 12:41                 ` Stefan Kangas
2019-10-10 18:33             ` Peter Dyballa
2019-10-10 18:57               ` Eli Zaretskii
2019-10-10 21:07                 ` Stefan Monnier
2019-10-11 13:33                   ` Stefan Kangas
2019-10-11  7:10               ` Andreas Schwab
2019-10-11  7:23                 ` Peter Dyballa
2019-10-10  8:15       ` Andreas Schwab
2019-10-10 12:54       ` Stefan Monnier
2019-10-10 13:12         ` Stefan Kangas
2019-11-17 20:58           ` Stefan Kangas

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=tl7ws4p7npy.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=4157@emacsbugs.donarmstrong.com \
    --cc=Peter_Dyballa@Freenet.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.
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.