bug#2806: characters from unicode-sip coderange still not displaying properly

bug#2806: characters from unicode-sip coderange still not displaying properly

[Christian Wittern]

Hi there,

I just confirmed with the released version 23.1 that this problem is
still existing.  It is very disappointing and keeps all Mac users I
know from upgrading to the otherwise wonderful release 23.  Is there
anything I can do to help getting this issue fixed?

All the best,

Christian

-- 
Christian Wittern, Kyoto

bug#2806: characters from unicode-sip coderange still not displaying properly

[Christian Wittern]

Thank you Handa-san.  Shortly after sending this message, I found out 
that Yamamoto Mitsuharu-san in Chiba has a patch [1] that provides the 
functionality I needed.  I succeeded in applying this patch and have 
used the resulting Emacs.app for about a month now without any 
problems.  It would surely be great if that patch could be incorporated 
into the Emacs source.
All the best,  Christian

[1] ftp://ftp.math.s.chiba-u.ac.jp/emacs/emacs-23.1.90-mac-1.95.tar.gz

On 2009-12-15 14:56, Kenichi Handa wrote:
> In article<5268d87d0912141704k5eb7ae24p777096a93cbbc0d2@mail.gmail.com>, Christian Wittern<cwittern@gmail.com>  writes:
>
>    
>> I just confirmed with the released version 23.1 that this problem is
>> still existing.  It is very disappointing and keeps all Mac users I
>> know from upgrading to the otherwise wonderful release 23.  Is there
>> anything I can do to help getting this issue fixed?
>>      
> Emacs supports unicode-sip displaying at least on Unix/Linux
> where we can use fontconfig and freetype.  See the attached
> image (result of M-x list-charset-chars RET unicode-sip
> RET).  Emacs asks a font-backend to get a font whose
> registry is "unicode-sip", and fontconfig backend searches
> for fonts that support at least U+20000 for such a request.
>
> Perhaps, Mac's font-backend is not doing that.
>
>    
>
>
>
> ---
> Kenichi Handa
> handa@m17n.org
>    


-- 
  Christian Wittern
  Institute for Research in Humanities, Kyoto University
  47 Higashiogura-cho, Kitashirakawa, Sakyo-ku, Kyoto 606-8265, JAPAN

bug#2806: characters from unicode-sip coderange still not displaying properly

[Kenichi Handa]

In article <4B5E7017.8050505@gmail.com>, Christian Wittern <cwittern@gmail.com> writes:

> Thank you Handa-san.  Shortly after sending this message, I found out 
> that Yamamoto Mitsuharu-san in Chiba has a patch [1] that provides the 
> functionality I needed.  I succeeded in applying this patch and have 
> used the resulting Emacs.app for about a month now without any 
> problems.  It would surely be great if that patch could be incorporated 
> into the Emacs source.
> All the best,  Christian

> [1] ftp://ftp.math.s.chiba-u.ac.jp/emacs/emacs-23.1.90-mac-1.95.tar.gz

I have no knowledge about Mac, and can't find which part of
the above file is necessary for supporting unicode-sip
displaying.

Could someone working on Mac port please DTRT?

---
Kenichi Handa
handa@m17n.org

bug#2806: characters from unicode-sip coderange still not displaying properly

[YAMAMOTO Mitsuharu]

>>>>> On Tue, 26 Jan 2010 20:08:13 +0900, Kenichi Handa <handa@m17n.org> said:

> In article <4B5E7017.8050505@gmail.com>, Christian Wittern
> <cwittern@gmail.com> writes:
>> Thank you Handa-san.  Shortly after sending this message, I found
>> out that Yamamoto Mitsuharu-san in Chiba has a patch [1] that
>> provides the functionality I needed.  I succeeded in applying this
>> patch and have used the resulting Emacs.app for about a month now
>> without any problems.  It would surely be great if that patch could
>> be incorporated into the Emacs source.  All the best, Christian

>> [1]
>> ftp://ftp.math.s.chiba-u.ac.jp/emacs/emacs-23.1.90-mac-1.95.tar.gz

> I have no knowledge about Mac, and can't find which part of the
> above file is necessary for supporting unicode-sip displaying.

> Could someone working on Mac port please DTRT?

Someone working on the NS port, which is supposed to be a first-class
official port, should DTRT.  The Mac port is neither a patch for nor a
distribution on top of the NS port, but a completely independent port
created with a different policy and design.

I didn't do anything special about unicode-sip for the font backend
drivers on the Mac port.  They are created by porting xftfont.c and
ftfont.c straightforwardly, and perhaps that might give a good result
for this matter.

				     YAMAMOTO Mitsuharu
				mituharu@math.s.chiba-u.ac.jp