well, I can give that a whirl. you should hear how those text attributes sound in my screen reader. its much the same as trying to pick out an object at range among a bunch of moving scenery.
the man piped through more scheme is the biggest part of the problem, especially on remote sessions. As an aside, I have tried looking at some man pages placed on the net. to say they are a model of readability given all the other links and associated crapola is anything but true. In some cases, its confusing to the point of not wanting to deal with. anyway, back to reading and thanks for some of the suggestions. -eric On Jul 26, 2012, at 12:14 PM, Ted Unangst wrote: > On Thu, Jul 26, 2012 at 10:54, Eric Oyen wrote: >> well, I am wondering what packages I can use to edit man pages. also, I may >> have to change how a man page would be laid out because my screen reader >> (both >> in linux and OS X) seem to have trouble handling the change in content when I >> navigate through a man page in a terminal session. > > man typically pipes the output through more (or less). But if you > plan to edit the page, you feed the input through mandoc. There are > several supported output formats, but the default is ascii text. One > thing to note is that the output renders bold text as > letter-backspace-letter, which looks really funny in a text editor, > but works ok for terminals and more. You probably want to read the > mandoc man page itself carefully, you may be able to build a better > interface to man pages if the man/more combo isn't good for you.
