emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 23.0.60; GNU Emacs does not handle composed characters


From: James Cloos
Subject: Re: 23.0.60; GNU Emacs does not handle composed characters
Date: Sun, 30 Dec 2007 21:50:17 +0000
User-agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux)

I just tried out some file (and file name in dired) where I expected to
find composed character sequences to compare against Peter’s findings.

I didn’t find the composed sequences, but did find that the character
U+1E08 LATIN CAPITAL LETTER C WITH CEDILLA AND ACUTE is being displayed
as the glyph for the character U+013D LATIN CAPITAL LETTER L WITH CARON.

U+013D itself also gets that glyph.

I have the following in my ~/.emacs:

,----[ excerpt from ~/.emacs ]
| (defun jhc-what-font () "" (interactive)
|   (message "%s" (aref (query-font (font-at (point))) 1)))
`----

and that returns my default font, DejaVu Sans Mono, for U+1E08.

The font does have the needed glyph, and it does display correctly
in other apps.

... Does more searching ...

I did find at least one file with a composed sequence.  It contains a
zero followed by U+0338 COMBINING LONG SOLIDUS OVERLAY.  That pair works
correctly for me in Emacs.  The following line also seems to work,
although I cannot say for sure; it does at least look better than it
does in my terminal app:

,----[ mhadmamrajamapt.utf8 ]
| မဟာဓမ္မရာဇာမ္‌ပတ
`----

This one is definitely ok:

,----[ macron.utf8.txt ]
| m̄ M̄ n̄ N̄ ē Ē ō Ō
| U+0304  ̄
`----

That is all I could find.

I run the unicode-2 branch on an x86 gentoo box using X11 frames.

-JimC
-- 
James Cloos <address@hidden>         OpenPGP: 1024D/ED7DAEA6




reply via email to

[Prev in Thread] Current Thread [Next in Thread]