the web page server is for displaying them in a way my screen reader can handle. didn't you pay attention in my posting? I mentioned being blind.
as for editing man pages using a text editor, frankly, that is a bit tedious as there is a lot of text attributes and other invisible "features" embedded in the man pages themselves. btw, for me, this is not a simple no step process. I doubt you understand the constraints I operate under here. So, I will just leave it at that anyway, I think this thread is going a bit far afield from its intended topic. -eric On Jul 26, 2012, at 11:34 AM, bert wrote: > On Thu, Jul 26, 2012 at 10:54:25AM -0700, Eric Oyen wrote: >> well, I am wondering what packages I can use to edit man pages. also, I may > > What's your favorite text editor? > >> 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. >> >> There was a web page converter that would take man pages and convert them to >> web content. it required installing a specific package, starting a local web >> server and then typing in a URL bar in a web client the command: "man: <man >> page here>". I was never entirely able to get that to work on either OS X or >> linux. I may have to look for the same package in ports (once I remember its >> name). > > Why in the hell do you need a web browser to edit man pages? Why does > the world insist on 7 steps for a no-step process? > >> >> anyway, there are those of us out here willing to do the work, but would >> appreciate some preliminary documentation from DEVS as to what goes where. > > man roof
