RFC: MULE coding system docs and modeline indicators

I've just completed drafting a revision of the Lispref | Mule documentation aimed at making the coding system documentation more useful. The structure is still pretty bad (I've mostly just added descriptions of various coding systems), and I would appreciate suggestions on improving the organization. Also, a while back somebody (Hrvoje? welcome back!) suggested rationalizing the coding system modeline indicators. Before I start on that, I want to check that (1) nobody else has worked on it, and (2) that using the FSF scheme is the way to go. It seems to me that *very* short and cryptic is the way to go, so I'm thinking about adding (a) balloon help giving full name of the coding system plus (b) the "about the coding system" help function(s) from the Mule menu to the modeline. (a) seems pretty uncontroversial; for (b) should the functions be duplicate, moved, or don't do this? I'm also working on fixing the functions in mule-base/mule-diag.el. Again, if anybody's done anything in that direction, let me know. The current description functions come in a verbose but very incomplete form and a uninterpretably terse but complete form. I don't see any use for the latter; I think that should be verbose, too. Comments? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."