unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: mule@m17n.org, rms@gnu.org, tats@vega.ocn.ne.jp, emacs-devel@gnu.org
Subject: Re: Mule-UCS 0.84 (KOUGETSUDAI) release.
Date: 09 Dec 2002 18:57:41 +0000	[thread overview]
Message-ID: <rzqisy3m34q.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: 20021207.085958.92564095.wl@gnu.org

Werner LEMBERG <wl@gnu.org> writes:

> I'm not sure whether Emacs without Mule-UCS can satisfy my needs yet:
> I want to map UTF8 input to the many ETL fonts (which are in various
> encodings) for displaying.

I assumed this was about CJK, but perhaps not.  Anyhow, you can
certainly display the mule-unicode charsets with any fonts you can map
onto them with CCL.  (See `utf-translate-cjk' if the issue really is
CJK in utf-8/16.)

> According to the documentation of unify-8859-on-decoding-mode, it does
> exactly the opposite.

That's really unrelated to display (there was an obsolete comment in
there).  See `utf-fragment-on-decoding' actually to decode into
different charsets (which would need an updated table), or you should
be able to do like ccl-encode-unicode-font in fontset.el but with the
reverse mapping.

> The real problem with Mule-UCS for me is that the configuration of
> this mapping has never worked (besides the fact that it has never been
> documented);

I've certainly configured Mule-UCS (at build time) to change the
precedence of the charsets into which it decodes.  I thought I'd also
changed the font mapping orthogonally, but I don't remember clearly.

> I don't have enough time currently to test Emacs-Unicode which will
> eventually support what I want AFAIK.

I'm not sure quite what you want, or why the internal representation
is relevant.  The fontset mechanism has been changed, but I haven't
finished a user interface for it and I think you don't want to use
that code for real work.


  parent reply	other threads:[~2002-12-09 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021104.103826.71116326.05@tats.iris.ne.jp>
     [not found] ` <20021105.202038.18871060.05@tats.iris.ne.jp>
     [not found]   ` <20021129.215347.74727519.05@tats.iris.ne.jp>
2002-12-02 16:51     ` Mule-UCS 0.84 (KOUGETSUDAI) release Werner LEMBERG
2002-12-04 11:06       ` Richard Stallman
2002-12-04 13:43         ` Werner LEMBERG
2002-12-06 13:32           ` Richard Stallman
2002-12-06 16:58           ` Dave Love
     [not found]             ` <20021207.085958.92564095.wl@gnu.org>
2002-12-09 18:57               ` Dave Love [this message]
2002-12-05  8:15       ` Kenichi Handa
2002-12-05 10:47         ` Andreas Schwab
2002-12-05 11:25           ` Kenichi Handa
2002-12-05 12:16             ` Andreas Schwab
2002-12-05 14:47               ` Stefan Monnier
2002-12-05 16:32             ` Dan Discipulo
2002-12-05 16:26         ` MIYASHITA Hisashi
2002-12-06  7:36           ` Kenichi Handa
2002-12-06 18:47             ` Dan Discipulo
     [not found]               ` <200212070342.FMLAAB12353.mule@m17n.org>
2002-12-06 19:15                 ` You dan@wilshire.com are not member (mule ML) Dan Discipulo

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=rzqisy3m34q.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=mule@m17n.org \
    --cc=rms@gnu.org \
    --cc=tats@vega.ocn.ne.jp \
    /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).