unofficial mirror of bug-gnu-emacs@gnu.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: Tue, 25 Aug 2009 09:46:50 +0900	[thread overview]
Message-ID: <E1MfkBW-0008TM-Fe@etlken> (raw)
In-Reply-To: <AB00A4BE-E1DF-45F4-8953-23B2F7E551F9@Freenet.DE> (message from Peter Dyballa on Mon, 24 Aug 2009 17:21:09 +0200)

In article <AB00A4BE-E1DF-45F4-8953-23B2F7E551F9@Freenet.DE>, Peter Dyballa <Peter_Dyballa@Freenet.DE> writes:

> The version from three weeks ago does not allow to  
> separate the composed character's components, i.e., the text cursor  
> cannot select this or that component, one step and it has reached the  
> previous or next character.

Even if your buffer has the char sequence "a" and "¨", "¨"
is displayed on top of "a" and cursor movement treats those
two characters atomically as if there's a single character
"ä".

> A difference I can see comes C-u C-x =: the line

>    canonical-combining-class: 0 (Spacing, split, enclosing,  
> reordrant, and Tibetan subjoined)

> is removed from the output.

That's the point.  utf-8-hfs converts the sequence "a" and
"¨" to a single character "ä" on decoding, and breaks down
"ä" to "a" and "¨" on encoding.

> The composed character still is not taken from the default font.  
> Could be one component is missing, ¨ – but it has the precomposed  
> characters I usually use.

Which font is selected for the character "ä"?  It seems to
be a bug if the font is not your default font.

---
Kenichi Handa
handa@m17n.org





  reply	other threads:[~2009-08-25  0:46 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             ` Kenichi Handa [this message]
2009-08-25  7:51               ` Peter Dyballa
2009-08-25 22:19           ` Peter Dyballa
2009-08-27  6:52             ` bug#4157: " Kenichi Handa
2009-08-27  8:50               ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1MfkBW-0008TM-Fe@etlken \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).