bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#2218: marked as done (23.0.90; current cvs fails with message "Inval


From: Emacs bug Tracking System
Subject: bug#2218: marked as done (23.0.90; current cvs fails with message "Invalid script or charset name: mathematical-bold")
Date: Fri, 13 Feb 2009 13:35:05 +0000

Your message dated Fri, 13 Feb 2009 15:33:08 +0200
with message-id <address@hidden>
and subject line Closing, worked around
has caused the Emacs bug report #2218,
regarding 23.0.90; current cvs fails with message "Invalid script or charset 
name: mathematical-bold"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
2218: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2218
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.90; current cvs fails with message "Invalid script or charset name: mathematical-bold" Date: Fri, 6 Feb 2009 12:51:00 +0800 Current CVS fails to start on OS X; no Emacs windows appears and the following message appears in the shell:

~/Source/gnu/emacs[master]$ nextstep/Emacs.app/Contents/MacOS/Emacs -Q
Invalid script or charset name: mathematical-bold

Reverting to git version 99d9b340834cc7c5588e623aace85bf98feb27ad
gives me a working version, so I suspect this commit:

2009-02-05  Kenichi Handa  <address@hidden>

    * international/fontset.el (script-representative-chars): Remove
    mathematical.
    (setup-default-fontset): Add entries for each subgroup of
    mathematical script.



--- End Message ---
--- Begin Message --- Subject: Closing, worked around Date: Fri, 13 Feb 2009 15:33:08 +0200 I committed a work-around fix to nsfont.m for now. The real solution probably involves modification to ..._list() and ..._match() methods of the NS font backend, but this work-around may be kept anyway unless the handling of sub-scripts by the font backend core is changed.



--- End Message ---

reply via email to

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