Hrvoje> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp&gt; writes: Hrvoje> Can't we just /debug/ those cases when they show up rather No. The particular one I mentioned would most likely simply show up as "bad HTML" in the W3 mode line. It's not my job to debug someone else's bad HTML, and I don't. Even if I went after it, the symptom would be bogus characters left in the file; only Bill Perry would be able to notice that and maybe figure out what was going on. The Ebola warning gets my attention, and localizes the problem. Hrvoje> than flashing the warnings in my face (which is especially Hrvoje> annoying on TTY's)? I know they're on by default only in Hrvoje> debugging builds, but it doesn't justify them if they're Hrvoje> only there to catch an occasional bug. I want them; I don't see why you should have to suffer them. I would be happy with an additional debug option to configure. (I don't know configure magic, so I can't do this myself.) I suspect that they're more likely to show up in Mule-using environments (since we're still at the stage of tracking FSF development); maybe the warnings could be turned on by default only in --with-mule builds. A better alternative yet would be to see if we can figure out what "spurious" Ebola warnings look like and trap them. -- 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."