Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: contrib/ucs-tables.el obsolete for Emacs 21.3
Date: Fri, 09 May 2003 09:18:03 +0200	[thread overview]
Message-ID: <84bryc8u6s.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <rzqsmrpujc3.fsf@albion.dl.ac.uk>

Dave Love <d.love@dl.ac.uk> writes:

> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>> Additionally, `ucs-tables.el' without using a newer version of
>> `utf-8.el' (replacing the pre-dumped code) isn't so useful in Emacs
>> 21.[1-2].
>
> I disagree.  It precisely solves the unification issue that people
> continually complained about (and normally claimed was impossible to
> solve).  I'm currently using it in Emacs 21.2.

Didn't you say previously that ucs-tables.el would benefit from an
improved utf-8.el?  But thay may have been with 21.1, and the
utf-8.el in 21.2 might include the necessary facilities already.

I'm slightly confused now.

> Without wishing to sound rude:
>
>  * If the documentation is unclear, or there are problems with the
>    code, it would be nice to get bug reports.  It may well be
>    difficult to use, but I'm not sure how -- it's just loading one or
>    two compiled files.

The version that's now in the Gnus contrib directory has
unify-8859-on-{de,en}coding-mode which need to be called.

A short installation section mentioning this might be nice.  It would
be just two lines.

>  * What's wrong with the version I've distributed, which is what I
>    actually use in 21.2?

The problem is that people aren't using that version.  They are using
other versions.

If the version that's now in Gnus' contrib directory is not the one
you distributed, it would be really great if you could give it to us
again.  It was probably me who goofed up and got the wrong file,
somehow.  I apologize.

>  * I don't know about this `latin-unity' thing, but XEmacs can't do
>    the same -- it simply doesn't have the necessary facilities.
>
> Things like that file which will clash with future versions should be
> installed in the version-specific site-lisp directory, which is what
> it's there for.  Have people been recommending something else?

Yes.  There was a recommendation to add the Gnus contrib directory to
load-path.  Or even to move the files to the Gnus lisp directory.

It's the wrong approach.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)



  reply	other threads:[~2003-05-09  7:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 18:21 Reiner Steib
2003-05-07 23:41 ` Xavier Maillard
2003-05-08  8:01 ` Kai Großjohann
2003-05-08 13:31   ` Ted Zlatanov
2003-05-08 14:13     ` Kai Großjohann
2003-05-11 14:03     ` Dave Love
2003-05-08 23:09 ` Dave Love
2003-05-09  7:18   ` Kai Großjohann [this message]
2003-05-11 14:04     ` Dave Love
2003-05-12 15:39       ` Kai Großjohann

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

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

  git send-email \
    --in-reply-to=84bryc8u6s.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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 NNTP newsgroup(s).