unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Edward Casey" <ejmn@cpinternet.com>
Subject: Re: w32 mule status
Date: Sun, 1 Aug 2004 14:14:05 -0500	[thread overview]
Message-ID: <10gqg8ba4ptgedd@corp.supernews.com> (raw)
In-Reply-To: uk6wm3pxn.fsf@jasonrumney.net


<jasonr (Jason Rumney) @ f2s.com> wrote in message
news:uk6wm3pxn.fsf@jasonrumney.net...
> "Edward Casey" <ejmn@cpinternet.com> writes:
>
> > Does any of you know where the info reported by Options> Mule > Show
all
> > of Mule status, is stored between emacs sessions?
>
> It's not stored, unless you explicitly save it to a file with C-x C-w.
>
> > I have a satisfactory setup on one machine that I am not able to
> > emulate on another. I have compared all the w32-* variables and they
> > are the same on both machines.  The problem must have something to
> > do with fontsets or extended character mappings. Help!
>
> You haven't described the problem, so I don't know how valid that
> assumption is. I assume you wanted to compare the two files to see
> what is different?

Excuse my tardiness in replying but I have been trying to educate myself
enough so that I can frame the problem clearly, but without success. The
symptom is that out of 3 installations of emacnt 21.3.1 only one of them
is able to display Latin-4 characters. All of them are using the same
operating system win98, all have the same TTF fonts, all have the same
version of the macronize character routine that you wrote for me. This
routine is the only thing in my .emacs. Apparently I got one system
working by sheer luck (that is by copy-pasting and then evaluating
snippets of lisp culled from the web). If the state information is not
being saved by emacs then it is being saved by Windows since I can cold
boot each machine, set exactly the same options in the Mule environment,
and get different results. Apparently fontsets are used in both X and
ntemacs but can't be changed via S-mouse1 under the latter O.S.  I ran an
ediff on the outputs of Show all of mule status on two machines and the
differences (all under fontset default and all the indented entries
starting with [ ) were:

     [-outline-Courier
New-normal-i-normal-normal-13-97-96-96-c-80-iso8859-1]
     [-outline-Courier New-bold-r-normal-normal-13-97-96-96-c-80-iso8859-1
]
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-1]
latin-iso8859-1  -*-iso8859-1
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-1]
latin-iso8859-2  -*-iso8859-2
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-2]
latin-iso8859-3  -*-iso8859-3
latin-iso8859-4  -*-iso8859-4
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-4]
thai-tis620  -*-*-*-tis620-*
     [-outline-Tahoma-normal-r-normal-normal-13-97-96-96-p-60-tis620*-*]
greek-iso8859-7  -*-*-*-iso8859-7
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-7]
arabic-iso8859-6 -*-*-*-iso8859-6
hebrew-iso8859-8 -*-*-*-iso8859-8
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-8]
katakana-jisx0201 -*-*-*-jisx0208-sjis
     [-outline-Caslon-bold-r-normal-normal-13-97-96-96-p-80-jisx0208-sjis]
latin-jisx0201  -*-*-*-jisx0208-sjis
cyrillic-iso8859-5 -*-*-*-iso8859-5
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-5]
latin-iso8859-9  -*-iso8859-9
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-9]
latin-iso8859-15 -*-iso8859-15
latin-iso8859-14 -*-iso8859-14
japanese-jisx0208-1978 -*-*-*-jisx0208-sjis
chinese-gb2312  -*-*-*-gb2312.1980-*
     [-outline-SimSun-normal-r-normal-normal-13-97-96-96-p-70-gb2312*-*]
japanese-jisx0208 -*-*-*-jisx0208-sjis
     [-outline-Caslon-bold-r-normal-normal-13-97-96-96-p-80-jisx0208-sjis]
korean-ksc5601  -*-*-*-ksc5601.1989-*
     [-outline-Arial Unicode
MS-normal-r-normal-normal-13-97-96-96-p-60-ksc5601.1987*-*]
japanese-jisx0212 -*-*-*-jisx0212-*
chinese-cns11643-1 -*-*-*-cns11643.1992-1
chinese-cns11643-2 -*-*-*-cns11643.1992-2
japanese-jisx0213-1 -*-*-*-jisx0213.2000-1
chinese-big5-1  -*-*-*-big5-*
     [-outline-MingLiU-normal-r-normal-normal-13-97-96-96-c-70-big5*-*]
chinese-big5-2  -*-*-*-big5-*
chinese-sisheng  -*-sisheng_cwnn-*
ipa   -*-muleipa-*
vietnamese-viscii-lower -*-viscii1.1-*
vietnamese-viscii-upper -*-viscii1.1-*
arabic-digit  -*-*-*-mulearabic-0
arabic-1-column  -*-*-*-mulearabic-1
ascii-right-to-left -*-iso8859-1
lao   -*-*-*-mulelao-1
arabic-2-column  -*-*-*-mulearabic-2
indian-is13194  -*-*-*-is13194-devanagari
indian-1-column  -*-*-*-muleindian-1
tibetan-1-column -*-*-*-muletibetan-1
mule-unicode-2500-33ff -*-iso10646-1
mule-unicode-e000-ffff -*-iso10646-1
mule-unicode-0100-24ff -*-iso10646-1
     [-outline-Courier
New-normal-r-normal-normal-13-97-96-96-c-80-iso10646-1]

Is it possible that the "functions unify-8859-on-encoding-mode and
unify-8859-on-decoding-mode to turn on conversion between UTF-8 and
ISO-8859" (from your answer to the Cyrillic font problem) could be part of
the solution? I assume that the entry:

  [-outline-Courier New-normal-r-normal-normal-13-97-96-96-c-80-iso8859-4]

is the only one relevant to my immediate purposes. For instance, I
certainly don't need Thai, but somehow I got it.

Thanks,

Ed

  reply	other threads:[~2004-08-01 19:14 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 [this message]
2004-08-01 20:16     ` Jason Rumney
2004-08-01 22:19       ` Edward Casey
2004-08-02  7:49         ` Jason Rumney
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=10gqg8ba4ptgedd@corp.supernews.com \
    --to=ejmn@cpinternet.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).