[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: x-symbol package dangerous in multibyte environment

Janusz S. Bień wrote:
Are you on the debian-emacsen list?

Ok, I'm on it now.  Can you please send me a copy of the
files that demonstrate the problem?  And a description of
what happens.

Also, the best way to bring a bug to the attention of the
Debian package maintainer is to file a bug report.  There
is a "reportbug" package that should help you out in the

On Thu, 31 Oct 2002  "Wedler, Christoph" <christoph.wedler@sap.com> wrote:
It's general for all people where ALL of the following conditions are

* they have a non-latin-1 default coding system (or read files with the
  coding: spec) which produces/reads 8bit chars ().

Quite a lot of them.

* they use \usepackage[latinN]{inputenc} where N != 1

The Debian/unstable package handles latin-11 too.

* their system does not have the locale command

The LaTeX commands should be sufficient for a LaTeX documents.

The locale command is in the libc6 package. (In unstable, at least.)

* they don't read the warnings issued by X-Symbol (OK, it's a bit
  hidden with Emacs < 21.4).

GNU Emacs 21.2.1 (from a Debian package) gives no warning at all.

We really should add a system like XEmacs' warning system to

* they don't read carefully the installation instruction while using
  beta software.

The x-symbol is a package from the stable Woody Debian GNU/Linux
distribution. One does not read installation instruction when
installing a Debian package.

FWIW, the package description does state: "Emacs21 support is still BETA".

> This should be remedied as soon as possible, either by you or by the
> Debian package maintainer.

As I said, probably next week.  BTW, you are allowed to send patches.

I can test the corrected Debian package.

Once the issues are reported to me in detail, I'll address them in
unstable, and then we can decide what to do with stable.

I'll definitely add a debconf option to choose whether x-symbol is
enabled globally.  If I have a good classification of where it
runs into problems, I'll tweak it to not turn on in those cases
(until we have a better fix).


Reply to: