Andreas Jaeger <aj(a)suse.de> writes:
Yoshiki> Then, Gnus wasn't running fine on XEmacs 21.2 for
some
Yoshiki> months? According to the ChangeLog XEmacs 21.2 has
Yoshiki> coding-system-get after 1999-06-28.
No, it should have worked for 21.2 since lisp/mule/mule-charset-el
has: (defalias 'get-charset-property 'get)
Err, sorry, now I understand the problem. I thought it was
(coding-system-get ... 'mime-charset) thing.
Yoshiki> [...]
>> Two problems with the code:
>>
>> The first one is XEmacs:
>> XEmacs now has coding-system-get - but it doesn't have
>> get-charset-property. If we have coding-system-get should we also
>> have get-charset-property?
Yoshiki> Yes, it would be nice if we have them.
Yoshiki> But then again, this is MULE API problem. Some codes are
Yoshiki> synched with FSF and some codes are not. We really really
Yoshiki> really need to define API and stick with them. Until that
Yoshiki> happens, application needs to have workaround. This case,
Yoshiki> Gnus.
Should we move those to 21.2 also?
^^^^
You mean 21.1.
1999-05-26 SL Baur <steve(a)gneiss.etl.go.jp>
* mule/mule-charset.el (charset-after): New function.
(charset-direction): Synch with Mule, update docstring.
(get-charset-property): New function.
(put-charset-property): New function.
(charset-plist): New function.
Probably yes, as we know it makes Gnus happy. Like
coding-system-get, it doesn't behave the way FSF does,
though. This is caused by the two big problems XEmacs/MULE
has: No API, bad interaction between mule-base and core.
I guess this will continue for a while. Sigh.
--
Yoshiki Hayashi