From: Simon Josefsson <jas@extundo.com>
Subject: Re: UTF-8 support has stopped working
Date: Mon, 14 Apr 2003 21:55:28 +0200 [thread overview]
Message-ID: <iluznmsdfbj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87brz8di50.fsf@doohan.bang.priv.no> (Steinar Bang's message of "Mon, 14 Apr 2003 20:54:35 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Simon Josefsson <jas@extundo.com>:
>
>> I tried mule-ucs in unstable now with both Emacs 20 and XEmacs 21
>> and had no problems with UTF-8.
>
> xemacs21-mule in testing is 21.4.6-8, while unstable is 21.4.12-1(*).
> mule-ucs in testing is 0.84.99rc3-1, while unstable is 0.84.99rc3-2.
I used Emacs 20 and XEmacs 21 from stable, actually, only mule-ucs was
unstable.
> Perhaps I should yank a new xemacs21 and mule-ucs in from unstable?
> Can you confirm that the above deb package version numbers for
> unstable, are the same as the ones that works for you?
I was using XEmacs 21.4.6-8 and mule-ucs 0.84.99rc3-2.
> (*) BTW is the third version number of the upstream version, ie. the
> number following the second dot, a real version number? Or is it like
> GNU Emacs in the old days, the number of times emacs is built from the
> same unpacked and configured source?
Emacs uses the old version scheme, but for XEmacs it is real upstream
version numbers.
next prev parent reply other threads:[~2003-04-14 19:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 19:57 Steinar Bang
2003-04-13 13:27 ` Lars Magne Ingebrigtsen
2003-04-13 19:45 ` Steinar Bang
2003-04-13 20:34 ` Steinar Bang
2003-04-14 6:11 ` Kai Großjohann
2003-04-14 11:29 ` Steinar Bang
2003-04-14 13:05 ` Simon Josefsson
2003-04-14 18:54 ` Steinar Bang
2003-04-14 19:55 ` Simon Josefsson [this message]
2003-04-14 21:03 ` Steinar Bang
2003-04-14 21:09 ` Steinar Bang
2003-04-14 21:57 ` Reiner Steib
2003-04-15 5:28 ` Steinar Bang
2003-04-15 14:23 ` Reiner Steib
2003-04-19 11:35 ` Simon Josefsson
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=iluznmsdfbj.fsf@latte.josefsson.org \
--to=jas@extundo.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 NNTP newsgroup(s).