Just today, before I read this exchange, I was running 'info' in an ASCII environment (LC_ALL='C' on Fedora 15). And just before *that*, I was reading documentation under Emacs info mode (my normal way of reading documentation). As a developer, I rarely read Emacs manuals using HTML, or using PDF, or using 'info' under UTF-8; Emacs beats all those formats.
>From my point of view, we shouldn't design manuals that are hard to read under Emacs. The cost simply outweighs any benefits. And I don't see why we should make manuals hard to read under ASCII 'info' either. On 11/09/11 15:10, Bruno Haible wrote: > I'll trust that if enough people are working in these environments, these > problems will get fixed. That doesn't sound realistic. People who are working in ASCII or other single-byte environments by and large are not interested in getting them "fixed", as they don't consider them "broken". It'd be unwise to try to use our documentation as a device to get them to change their opinions -- more likely, they'll just assume that our documentation is busted. Whatever minor advantage we might get from using no-break space characters in documentation, does not appear to be worth all this hassle. Let's just leave things be.
