I implemented the suggestion about turning off UTF-8 support, and now vim speaks perfectly. I also found that speakup still reads the correct character names on the console. For instance when pressing alt+234 on numpad, speakup still reads "e circumflex" so it seams one can just as well turn UTF-8 off. From what I know speakup can anyway not read characters above code 255. Thanks, Rynhardt * Steve Holmes <steve at holmesgrown.com> [100804 04:09]: > This is an interesting area but isn't utf-8 becoming the defacto > standard and the ultimately better way to go? I know when I switched > to utf-8 in elinks, some of the characters over 127 represent better > in elinks and speakup handles them quite well with proper descriptions > instead of those stupid %222 type symbols all over the place. I > especially like this improvement while reading HTML type messages > inside of mutt. > > On Tue, Aug 03, 2010 at 08:02:24PM -0500, Adam Myrow wrote: > > These problems with vim seem to be related to UTF-8. I have UTF-8 > > disabled in Slackware, and vim works properly. To disable UTF-8, > > you have to pass "vt.default_utf8=0" to the kernel at boot time. > > Then, set your LANG environment variable to "en_US." This is a > > non-UTF-8 version of English. In Slackware, this is the default, > > but my understanding is that it is not in most other Linux > > distributions. > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup
