I think you have two options: 1. process the man files using roff, with output as text. I wouldn't strip linefeeds - instead, I'd convert the ^H output so that bold and underlined text appear as normal text (the FreeDOS MORE program and other DOS "pager" programs do not interpret ^H backspacing to do bold and underline.) I had once written a tool to automatically strip out backspaced characters (for example, "_^HH_^He_^Hl_^Hl_^Ho" becomes "Hello") but it's not hard to write your own. As you suggest, the output from this could go in the "DOC" folder with the other READMEs.
2. groff has an option to generate html output (not sure if djgpp's groff can do this, though.) So I suppose you could process the man files using groff's html output generator, and include those as "html Help" pages. -jh On Wed, Apr 9, 2008 at 3:32 AM, Robert Riebisch <[EMAIL PROTECTED]> wrote: > Hi! > > I'm porting some small tools to (Free)DOS using latest Open Watcom > C/C++. Of course, all have documentation in standard man pages. ;-) > AFAIK FreeDOS doesn't come with a man page reader. So what's the best > method to make documentation accessible to DOS users? > > My idea is to put original groff files to the "doc" folder (along with > other READMEs). Additionally I'd like to preprocess such files with > DJGPP's groff, strip line feeds from (to make a simple ASCII file) and > put these new files to the "help" folder. > > What do you think? > > Robert Riebisch ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
