unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: doc/emacs/mule.texi questions
Date: Mon, 16 Apr 2012 13:37:59 -0400	[thread overview]
Message-ID: <2vpqb7pog8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <873983rdrg.fsf@gnu.org> (Jason Rumney's message of "Mon, 16 Apr 2012 21:45:55 +0800")

Jason Rumney wrote:

> I think standard-fontset-spec is a leftover from Emacs 22 before a font
> backend existed that could automatically sort through the fonts
> available on the user's system. This fontset spec was designed to match
> the fonts in the GNU intlfonts package.  The default fontset is probably
> a leftover too, Emacs displays most international characters out of the
> box now whether you specify a fontset or just a simple font. 

I know very little about fontsets (so it would be great if someone other
than me would proof-read this part of the manual...), but reading those
parts of mule.texi I got the general impression that some of it seems
old.

For example, the GNU intlfonts tarfile is 9 years old. Does anyone still
need to install that, as opposed to just their distribution's font
packages for international characters?

The installation instructions (in mule.texi) refer to "xset fp+". I
guess (?) that still works, but aren't fontconfig files the way to do
that nowadays?

The fontsets docs refer mainly to the old-style font specs like

   -*-fixed-medium-r-normal-*-16-*-*-*-*-*-fontset-standard

I still use those, but I get the impression that most people have moved
on to things like "DejaVu Sans Mono-12" instead. There is little mention
of that in mule.texi.

> No, this is very out of date advice. Mule was stable enough to use in
> elisp files by 20.3 at latest.

Many things related to unibyte were declared obsolete.
Should the "unibyte: t" spec (meaning, load or compile this file of Lisp
code in unibyte mode) be another?



  reply	other threads:[~2012-04-16 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-14 19:25 doc/emacs/mule.texi questions Glenn Morris
2012-04-14 19:29 ` Eli Zaretskii
2012-04-16 13:45 ` Jason Rumney
2012-04-16 17:37   ` Glenn Morris [this message]
2012-04-17  1:54     ` Glenn Morris
2012-04-17 17:44     ` Stefan Monnier
2012-04-18 16:34       ` Glenn Morris
2012-04-18 21:47         ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2vpqb7pog8.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).