[macemacsjp-english 403] Re: anti-aliasing problem still exists in the Dec '05 version

Back to archive index

Seiji Zenitani zenit****@tkg*****
Sun Dec 11 19:35:07 JST 2005


On 2005/12/11, at 18:24, Peter Dyballa wrote:
>
> Am 11.12.2005 um 01:12 schrieb Seiji Zenitani:
>
>>> The new version of carbon-font.el (1.5.4 - 2005-11-20) does not  
>>> work:
>>>
>>> 	error: No fonts match
>>> `-apple-monaco-medium-r-normal--12-*-*-*-*-*-iso10646-1'
>>>
>>> My system fonts are mostly mac-roman encoded.
>>>
>> At my hand, carbon-font works fine.
>> Panther-specific problem?
>
> No! It's a problem in carbon-font.el:
>
> 	diff /Library/Application\
> Support/Emacs/carbon-font.el_1.5.4-2005-11-20 /Library/Application\
> Support/Emacs/carbon-font.el_1.5.2_2005-11-15
> 	
> 	316c261
> 	<   "-apple-%s-medium-r-normal--%d-*-*-*-*-*-iso10646-1")
> 	---
> 	>   "-apple-%s-medium-r-normal--%d-*-*-*-*-*-mac-roman")

Check if you use in-sync-version of fixed-width-fontset.el.

http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/macemacsjp/fixed-width- 
fontset/


>>> Alt-n does not always produce ~, the tilde character or accent! For
>>> example: C-h k alt-n. German keyboard.
>>
>> Did it work on the last November release?
>
> You can ask clever questions! It already did not work in the November
> release.

Perhaps you mean the well-known problem of Option(alt) + n{i,e,o,u  
etc.} keys. At present, it does not work when mac-key-mode is on,  
while it works when mac-key-mode is off. The situation may be better  
after I will switch to the more recent CVS code which includes key- 
modifier-patch.


-- Seiji





More information about the macemacsjp-english mailing list
Back to archive index