bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Michael Norrish via Bug reports for GNU Emacs, the Swiss army knife of text editors]

After starting with emacs -q, I paste the following into my *scratch* buffer:

;; ; superscripts and subscripts: ¹²³⁴⁵⁶⁷⁸⁹⁰ ₁₂₃₄₅₆₇₈₉₀ ₘₙₚᵣₛₜₜ
(set-fontset-font t '(#x2070 . #x209C) "System Font" nil 'prepend)

There are subscript characters in the comment line above between U+2070
and U+209C. My default font doesn't render them.  I know that MacOS's
"System Font" is capable of rendering them however. When I do C-x C-e at
the end of the set-fontset-font line, nothing changes in emacs, but I
get numerous repeated messages on the Terminal saying things like

  2022-10-06 15:53:44.239 Emacs-arm64-11[19927:6935256] CoreText note: Client requested name ".SFNS-UltraCompressedLightG4", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].

--
Michael



In GNU Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS appkit-2113.00 Version 12.0.1 (Build 21A559))
 of 2022-09-13 built on armbob.lan
Windowing system distributor 'Apple', version 10.3.2113
System Description:  macOS 12.6

Configured using:
 'configure --with-ns '--enable-locallisppath=/Library/Application
 Support/Emacs/${version}/site-lisp:/Library/Application
 Support/Emacs/site-lisp' --with-modules'

Configured features:
ACL GMP GNUTLS JSON LIBXML2 MODULES NOTIFY KQUEUE NS PDUMPER THREADS
TOOLKIT_SCROLL_BARS ZLIB

Important settings:
  value of $LC_CTYPE: en_AU.UTF-8
  value of $LANG: en_AU.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Lisp Interaction

Minor modes in effect:
  tooltip-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  indent-tabs-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug message rmc puny dired dired-loaddefs
rfc822 mml mml-sec epa derived epg rfc6068 epg-config gnus-util rmail
rmail-loaddefs auth-source cl-seq eieio eieio-core cl-macs
eieio-loaddefs password-cache json map text-property-search seq byte-opt
gv bytecomp byte-compile cconv mm-decode mm-bodies mm-encode mail-parse
rfc2231 mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mail-utils time-date subr-x cl-loaddefs
cl-lib iso-transl tooltip eldoc paren electric uniquify ediff-hook
vc-hooks lisp-float-type elisp-mode mwheel term/ns-win ns-win
ucs-normalize mule-util term/common-win tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode lisp-mode
prog-mode register page tab-bar menu-bar rfn-eshadow isearch easymenu
timer select scroll-bar mouse jit-lock font-lock syntax font-core
term/tty-colors frame minibuffer cl-generic cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese eucjp-ms
cp51932 hebrew greek romanian slovak czech european ethiopic indian
cyrillic chinese composite emoji-zwj charscript charprop case-table
epa-hook jka-cmpr-hook help simple abbrev obarray cl-preloaded nadvice
button loaddefs faces cus-face macroexp files window text-properties
overlay sha1 md5 base64 format env code-pages mule custom widget
hashtable-print-readable backquote threads kqueue cocoa ns multi-tty
make-network-process emacs)

Memory information:
((conses 16 62607 13233)
 (symbols 48 6871 1)
 (strings 32 18653 2303)
 (string-bytes 1 615224)
 (vectors 16 19400)
 (vector-slots 8 512457 57028)
 (floats 8 21 35)
 (intervals 56 219 0)
 (buffers 992 11))

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Gerd Möllmann]

Michael Norrish <u4087502@anu.edu.au> writes:

> After starting with emacs -q, I paste the following into my *scratch* buffer:
>
> ;; ; superscripts and subscripts: ¹²³⁴⁵⁶⁷⁸⁹⁰ ₁₂₃₄₅₆₇₈₉₀ ₘₙₚᵣₛₜₜ
> (set-fontset-font t '(#x2070 . #x209C) "System Font" nil 'prepend)

There is no font named "System Font" on my Mac.  You can use Font Book
to see what fonts you have.  Does it work with one of the fonts shown in
Font Book?

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Michael Norrish via Bug reports for GNU Emacs, the Swiss army knife of text editors]

As per the exchange at 

  https://apple.stackexchange.com/questions/431620/how-to-determine-which-font-is-being-used-to-render-a-specific-character-in-term

I am able to paste the subscripts into TextEdit, and when I move my cursor to the relevant character, it tells me that I'm using something called "System Font".

Michael

On 6/10/2022, 19:44, "Gerd Möllmann" <gerd.moellmann@gmail.com> wrote:

    Michael Norrish <u4087502@anu.edu.au> writes:

    > After starting with emacs -q, I paste the following into my *scratch* buffer:
    >
    > ;; ; superscripts and subscripts: ¹²³⁴⁵⁶⁷⁸⁹⁰ ₁₂₃₄₅₆₇₈₉₀ ₘₙₚᵣₛₜₜ
    > (set-fontset-font t '(#x2070 . #x209C) "System Font" nil 'prepend)

    There is no font named "System Font" on my Mac.  You can use Font Book
    to see what fonts you have.  Does it work with one of the fonts shown in
    Font Book?

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Gerd Möllmann]

Michael Norrish <u4087502@anu.edu.au> writes:

> As per the exchange at 
>
>   https://apple.stackexchange.com/questions/431620/how-to-determine-which-font-is-being-used-to-render-a-specific-character-in-term
>
> I am able to paste the subscripts into TextEdit, and when I move my
> cursor to the relevant character, it tells me that I'm using something
> called "System Font".

Well, I don't know what TextEdit does, and why.

But you didn't say if Font Book says about which fonts are there.  You
can start Font Book with Spotlight - Command-Space, enter font book, and
return.  Is there a font named "System Font".  If not, Emacs won't be
able to load that font.

If you want to know what font Terminal is using, start Terminal, invoke
Terminal > Preferences from the menu bar, select "Profiles" in the
dialog box, and the "Text" tab on the right side.  There you find it
under "Font".

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Michael Norrish via Bug reports for GNU Emacs, the Swiss army knife of text editors]

On 7/10/2022, 16:01, "Gerd Möllmann" <gerd.moellmann@gmail.com> wrote:

    Michael Norrish <u4087502@anu.edu.au> writes:

    >
    > I am able to paste the subscripts into TextEdit, and when I move my
    > cursor to the relevant character, it tells me that I'm using something
    > called "System Font".

    Well, I don't know what TextEdit does, and why.

    But you didn't say if Font Book says about which fonts are there.  You
    can start Font Book with Spotlight - Command-Space, enter font book, and
    return.  Is there a font named "System Font".  If not, Emacs won't be
    able to load that font.

    If you want to know what font Terminal is using, start Terminal, invoke
    Terminal > Preferences from the menu bar, select "Profiles" in the
    dialog box, and the "Text" tab on the right side.  There you find it
    under "Font".

Both Terminal (and TextEdit) appear to be substituting in another font when the chosen font is not available for the given characters.  In particular, I set my font profile in Terminal to use Inconsolata, but it does not have those subscript characters, so I guess it falls back to the system font (it's pretty obvious that this is happening visually). Various sources indicate that this font (apparently also called San Francisco) is deliberately not available through font-pickers. See, for example,

   apple.stackexchange.com/questions/208849/is-there-a-user-font-for-san-francisco-in-el-capitan

Nonetheless, this used to work, and the error message indicates that whatever code Emacs is using is now deprecated, and that it should be doing something else. I appreciate that special-casing this particular font "name" might be a bit much to ask for.  (In the meantime, I will use DejaVu Sans Mono instead.)

Thanks,
Michael

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Gerd Möllmann]

Michael Norrish <u4087502@anu.edu.au> writes:

>
>    apple.stackexchange.com/questions/208849/is-there-a-user-font-for-san-francisco-in-el-capitan

Thanks.

> Nonetheless, this used to work, and the error message indicates that
> whatever code Emacs is using is now deprecated, and that it should be
> doing something else. I appreciate that special-casing this particular
> font "name" might be a bit much to ask for.  (In the meantime, I will
> use DejaVu Sans Mono instead.)

Can you check if this still occurs with Emacs 29?  I think
this might actually have been cjamged already.

I believe Emacs HEAD can be installed with Homebrew, if you are using
brew.

bug#58328: 28.2; can't select MacOS "System Font" using set-fontset-font

[Stefan Kangas]

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Michael Norrish <u4087502@anu.edu.au> writes:
>
>>
>>    apple.stackexchange.com/questions/208849/is-there-a-user-font-for-san-francisco-in-el-capitan
>
> Thanks.
>
>> Nonetheless, this used to work, and the error message indicates that
>> whatever code Emacs is using is now deprecated, and that it should be
>> doing something else. I appreciate that special-casing this particular
>> font "name" might be a bit much to ask for.  (In the meantime, I will
>> use DejaVu Sans Mono instead.)
>
> Can you check if this still occurs with Emacs 29?  I think
> this might actually have been cjamged already.
>
> I believe Emacs HEAD can be installed with Homebrew, if you are using
> brew.

No further updates within 9 months, so I'm going to assume this is
fixed.  I'm therefore closing this bug report.

If this conclusion is incorrect and this is still an issue, please reply
to this email (use "Reply to all" in your email client) and we can
reopen the bug report.