Re: Intent package mule2 and custom-mule
In article <E11eKWd-0000fFfirstname.lastname@example.org>
email@example.com (Takao KAWAMURA) writes:
> > What I want to say is,
> > "Good native language support is very important for Debian itself".
> Yor are right. My words should be corrected. However,
> hasty decisions should not be made for the beautiful words.
> Potato is not the last release of Debian, isn't it?
Thank you for your sincere consideration. I appreciate your correction.
and sure, coming potato must not be the last release, we should do
the effort to make release more frequently, at least more than one
per a year. (6 - 9 months are just for my taste, but you feels may vary)
# Well, there were discussion about release interval several months ago.
> I believed mule2 was a hasty decision. However, your
> explanations about mule2 disturb my self-confidence.
I have heard from an emacs-lisper that he needs the mule2 to debug
his elisp code, becuase emacs20 (20.2 in hamm at that time) has some bugs
in handling buffer data, compression / decompression or so.
I am agree with you, I am also afraid that if the users are satisfied
with that mule2, and if they would not to use emacs20, then their report
about bugs and missing features in emacs20 would be lost.
But if that mule2 is used as a reference for developers to check
the features and bugs in emacs20, then it will be benefitical to debug
the current GNU emacs and xemacs and feedback the patches to their maintainers
I myself am not convinced wheter that mule2 package will be harmfull or
benefitical for the further development on emacs and xemacs. I know that
KITAME have worked on xemacs development now, and I think that he can do
some contribution for it.
The important point, I think, is to comunicate and discuss enough with
the maintainers of related packages. I am dissapointed to know that
the maintainer of the mailcrypt package has not been informed.
I think the good communication in the members of our Debian project
is VERY important, as well as the communication to our upstreams.
# I am sorry to have done wrong in this point by myself. I have learned
# from my experience, and I wish others not to step the wrong way.
Taketoshi Sano: <firstname.lastname@example.org>,<email@example.com>,<firstname.lastname@example.org>