Re: check process state before accessing coding_stream (fix PR#1061)

>>>>> "dv" == Didier Verna <didier(a)epita.fr&gt; writes: dv> Martin R Buchholz wrote: >> We already have menubar translations via X resources, albeit poorly >> documented and incomplete. But there is certainly work left to do >> there for interested translators that involves no programming. dv> I'm very sceptical about working on X resources for anything, dv> even for translations of the menubar. We have already too much control over dv> too many features with the X resources. X resources are a not very good dv> mechanism which, what's more, works only under X. The gettext'ization of the dv> Lisp strings should be something generic, not depending on the platform your dv> XEmacs frame is on. It's true that our translations should be window-system independent. The current implementation of menubar translations using X resources exists because the original implementor was lazy. Of course, those translations could be used in any future X-independent translation format. My point is that there is already a database of translations available for translation. Until we have a situation where contributors have run out of material for translation, I don't think we should expend undue effort on translating random strings within XEmacs. If we do decide to go beyond menubar translations, we can enable translations specifically for docstrings, which should be safe enough. But today we have no active translators. Given the right kind of project leadership, that could change, but it would take someone with better management skills than we have shown lately. Do *you* run with menubars translated into your language? Why not? Martin