Two possible bugs.

Hello everyone, My first potential contributions since joining the mailing list follow a short introduction. My original exposure to emacs as a user took place in 1980 with the Gosling variant of the original beast. In those heady years (some would say hairy), the net was the size of a nut in the minds and winds (not like air, like twist) of a few. I migrated to xemacs about the time of 19.12 and currently run Emerald in its xemacs-20.4-1.i386.rpm incarnation. Most of my work involves editing and typesetting books and other long documents (via groff and lout) in English and Spanish. Writing accented characters (upper ascii) with the x-compose package involves sequences such as 'a to obtain á, etc. So far, so good, but when commands such as `downcase-word' or `upcase-word' are used, this takes place: Downcase-word: «MAÑANA» becomes «maÑana» instead of «mañana» In like fashion: Upcase-word: «mañana» becomes «MAñANA» instead of «MAÑANA» This involves all accented vowels and consonants. I know next to nothing about lisp coding, but would venture that it may not be too hard to fix . . . (FSF emacs performs the correct 8-bit replacements since 19.20). Another bug probably involves the masking of commands such as ^X^S (write-file). If you key in a typesetting command for groff such as `move vertically ½ line' ( \v'.5' ) followed immediately by ^X^S, you'll get: \v'.5'x -- in addition to write-file execution The second apostrophe keystroke is interpreted as the `deadkey accent' character of the two-character upper ascii generating sequence, while the ^X portion of ^X^S becomes a literal lower case `x' in the text. Oddly, (at least to this layman) the write-file command is executed properly in spite of its putative involvement with the final (previous) apostrophe. This behavior takes place with any deadkey that would normally raise the eighth bit when followed by any vowel (upper or lower case) or suitable Latin-1 consonant such as ` ÿ '. One can avoid the problem by remembering to strike the spacebar before typing ^X^S, but this is less than convenient as it requires an additional `protective' keystroke that is easily forgotten when needed and becomes a nuisance space character when not. Obviously, the spacebar keystroke is necessary to write a real apostrophe prior to an `unrelated' vowel, etc., but I should hope that a way can be found to mask control character sequences such as ^X^S to preserve their exclusive functionality regardless of what may have been written immediately before. Though in small measure, I believe these changes would usefully improve the remarkable xemacs working environment. THREE LOUD CHEERS FOR ALL WHO MAKE IT WORK! I don't know how you do it, but I sure appreciate the results . . . Hey, Bill Gates, get a life . . . elsewhere!