emacs-devel
[Top][All Lists]
Advanced

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

Re: Something wrong in language/devan-util.el


From: Kenichi Handa
Subject: Re: Something wrong in language/devan-util.el
Date: Tue, 27 Nov 2001 09:14:04 +0900 (JST)
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI)

Richard Stallman <address@hidden> writes:
>     The file you put in the repository is at least correct in
>     the encoding.  But, it seems that you commented out all
>     variable and function definitions that contains devanagari
>     characters.  I've just uncomment them and installed a new
>     version.

> I commented them out because compiling the file got an error.  Looking
> at the file, it seemed to be full of bad syntax--doublequote
> characters inside strings, without backslashes to quote them.

> I figured those doublequote characters were really supposed to be part
> of a multibyte encoding which had somehow gone wrong.  But I had
> no way to figure out what was wrong with it--I could only ask you.

> Unfortunately I don't remember now whether I did the compilation
> with make bootstrap or using an old Emacs.

I suspect that you compiled it with an old Emacs, because
with newly made Emacs (by bootstrapping), I encountered no
problem.

Anyway, now, as Pavel has installed this change:

2001-11-26  Pavel Janík  <address@hidden>

        * international/quail.el (quail-help): Require help-mode in
        top-level instead.

make bootstrap should work well.

> Now it looks like Gerd just encountered the same problem, but fixed it
> by inserting backslashes.  If those strings are supposed to use a
> multibyte coding, the backslashes may have screwed them up.  Would you
> take a look?

I've just committed this change:

2001-11-27  Kenichi Handa  <address@hidden>

        * language/devan-util.el: Undo 2001-11-26 change.

We should somehow force bootstrapping if something is
changed in mule-conf.el to avoid this kind of error in the
future.

---
Ken'ichi HANDA
address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]