From: jasonr (Jason Rumney) @ f2s.com
Subject: Re: w32 mule status
Date: Mon, 02 Aug 2004 08:49:58 +0100 [thread overview]
Message-ID: <ur7qquggp.fsf@jasonrumney.net> (raw)
In-Reply-To: 10gqr4ppd61pa93@corp.supernews.com
"Edward Casey" <ejmn@cpinternet.com> writes:
> The differences are just in the lines beginning with TAB [. These lines
> are missing from the fontset on the machine that won't display Latin-4
> characters.
So that machine does not have those fonts. Since this is Windows 98,
the default fonts for the US version are Latin-1 only. There is
another set of default fonts, which used to be available from the MS
website, and is also installed by various MS software packages. This
set supports many more encodings. If you do not look closely, it may
appear that the fonts are the same on both machines, but in the font
selection dialog, you have a "Script" dropdown selection, which will
be different on the machines that work compared to the one that
doesn't.
> I still think that the parameters for the fontsets have to be stored
> somewhere.
Only if you set them.
> What does M-x describe-fontset read?
It describes the fontset you specify. But this is a red herring. Emacs
21 displays all characters regardless of whether you use a font or a
fontset. The fontset gives you finer control over which fonts are used
to display which characters.
> Since I messed up one of the machines I have 2 fontsets called
> fonset-default with different settings. This leads me to believe that the
> (create-fontset-from-fontset-spec) function adds the definitions to a list
> somewhere.
If you put that in .emacs, it is saved in .emacs. There is nothing
magic going on behind the scenes.
next prev parent reply other threads:[~2004-08-02 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 2:00 w32 mule status Edward Casey
2004-07-30 7:38 ` Jason Rumney
2004-08-01 19:14 ` Edward Casey
2004-08-01 20:16 ` Jason Rumney
2004-08-01 22:19 ` Edward Casey
2004-08-02 7:49 ` Jason Rumney [this message]
2004-08-02 16:26 ` Edward Casey
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=ur7qquggp.fsf@jasonrumney.net \
--to=jasonr@f2s.com \
/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.
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).