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

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

Re: Problems with Emacs CVS Head in MacOS (Carbon)


From: Alberto Simões
Subject: Re: Problems with Emacs CVS Head in MacOS (Carbon)
Date: Fri, 24 Jun 2005 14:55:25 +0100
User-agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)

Hi, again.
Got some time for tests, and these are my problems:

. I didn't understand if I should choose from one of the second approach. I tried the second one, adding to my .emacs:

(create-fontset-from-mac-roman-font "-*-bitstream vera sans mono-medium-r-*-*-9-*-*-*-*-*-mac-roman" nil "09pt_Bitstream") (create-fontset-from-mac-roman-font "-*-bitstream vera sans mono-medium-r-*-*-10-*-*-*-*-*-mac-roman" nil "10pt_Bitstream") (create-fontset-from-mac-roman-font "-*-bitstream vera sans mono-medium-r-*-*-11-*-*-*-*-*-mac-roman" nil "11pt_Bitstream")

(defvar scalable-fonts-allowed t)

But now, I do not know what to do with these fontsets to activate them

Thanks
Alberto

Peter Dyballa wrote:

Am 16.06.2005 um 12:26 schrieb Alberto Manuel Brandão Simões:

No. Is there any way where I can find a howto or tutorial?


Not yet, because Carbon Emacs is an impasse (Unicode Emacs 23 will use ATSUI). Generally you check the functions' documentation and get lost in it. (After years of this abuse you might feel different.)

First you'll need to know what your Mac is offering: M-x set-frame-font TAB TAB and go to the *Completions* buffer. Save it to a name you've checked and even better: set and put into a register before (if you try to expand some file name the *Completions* buffer's contents will be overwritten with new contents).

Now you can start to write an Elisp file with a contents like (notice the two different functions):

    (create-fontset-from-fontset-spec
    "-*-andale mono-medium-r-*-*-0-*-*-*-*-*-fontset-10pt_andale_mono,
latin-iso8859-1:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-2:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-3:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-4:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, cyrillic-iso8859-5:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, arabic-iso8859-6:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, greek-iso8859-7:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, hebrew-iso8859-8:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-9:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-12:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-13:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-14:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-15:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, latin-iso8859-16:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, mac-roman-lower:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, mac-roman-upper:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, mule-unicode-0100-24ff:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, mule-unicode-2500-33ff:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, mule-unicode-e000-ffff:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, iso10646-1:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman, ascii:-*-andale mono-medium-r-normal--10-100-75-75-m-100-mac-roman" )
;
(create-fontset-from-mac-roman-font "-*-monaco-medium-r-*-*-9-*-*-*-*-*-mac-roman" nil "09pt_Mmonaco") (create-fontset-from-mac-roman-font "-*-monaco-medium-r-*-*-10-*-*-*-*-*-mac-roman" nil "10pt_Mmonaco") (create-fontset-from-mac-roman-font "-*-monaco-medium-r-*-*-11-*-*-*-*-*-mac-roman" nil "11pt_Mmonaco")

The first function only uses the bitmaps provided in the font suitcases (.dfont files in Mac OS X), i.e. you can set different size values but in the end you have always the same size on screen -- except Carbon Emacs chooses to take some non-existing glyph from another font! This one can be right-sized then. This function was intended to support non-Mac encodings, but it fails IMO.

The second function does a better job in sizes. It too fails for non-Mac encodings. The ``M´´ in the fontset names was chosen to make them distinct and to see immediately how they were defined (with Minimal effort). Could be you need to set for these to work

    (defvar scalable-fonts-allowed t)

Finish the Elisp file with

    (provide 'site-fontsets-carbon)

put it in the load-path (C-h v load-path RET) outside the application bundle and put into .emacs:

    (require 'site-fontsets-carbon)

in a clause for not launching it in Terminal. GNU Emacs compiled for X11 supports Unicode glyphs *much* better! Have you found transparancy? (setq mac-transparency-alpha 80)


There is also this (archive is slow):

------------------------------- Info --------------------------------
List Post: <mailto:macosx-emacs@email.esm.psu.edu>
List Archives: <http://www.esm.psu.edu/mac-tex/MacOSX-Emacs-Digests/>


--
Greetings

  Pete

Real Time, adj.:
Here and now, as opposed to fake time, which only occurs there and then.


--
Alberto Simões - Departamento de Informática - Universidade do Minho
                 Campus de Gualtar - 4710-057 Braga - Portugal




reply via email to

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