Alain M. wrote:
Most of the tme I use DOSEMU, so I can use Firefox, but I once tested
the htmlhelp for some freedos docs and it is good enough!
I think, you didn't get the point: Reading even the smallest manual
would always require HTMLHELP then. Yes, you could also use type or
more, but HTML
Robert Riebisch escreveu:
Most of the tme I use DOSEMU, so I can use Firefox, but I once tested
the htmlhelp for some freedos docs and it is good enough!
I think, you didn't get the point: Reading even the smallest manual
would always require HTMLHELP then. Yes, you could also use type or
Alain M. wrote:
I think, you didn't get the point: Reading even the smallest manual
would always require HTMLHELP then. Yes, you could also use type or
more, but HTML tag can be very annoying. So I don't like the idea.
I don't understand why you disagree...
I told you above.
Using
Alain M. wrote:
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.
Please find a consensus now with Eric! :-)
I vote
Robert Riebisch escreveu:
Alain M. wrote:
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.
Please find a consensus now
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
Hi Robert,
Of course, all have documentation in standard man pages. ;-)
That is not standard, that is Unix ;-)
AFAIK FreeDOS doesn't come with a man page reader. So what's
the best method to make documentation accessible to DOS users?
We have the HTMLHELP system. You should contact Fritz
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
Eric Auer wrote:
AFAIK FreeDOS doesn't come with a man page reader. So what's
the best method to make documentation accessible to DOS users?
We have the HTMLHELP system. You should contact Fritz Mueller
Is fritz.mueller [at] mail.com still valid?
to have your pages integrated into the
Jim Hall wrote:
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
Sorry, my mistake: I don't want to strip (CR)LF line feeds, but reverse
line feeds (control characters).
underlined text appear as normal
Is fritz.mueller [at] mail.com still valid?
Yes, but why not ask off-list?
What zip contents?
HTMLHELP can show HTML pages directly while they are still in a ZIP.
But of course you can override by putting unzipped HTMLs on disk.
be okay to have the ASCII version in doc/PACKAGENAME/*.txt
Eric Auer wrote:
Is fritz.mueller [at] mail.com still valid?
Yes, but why not ask off-list?
In contrast to you, I don't like off-list discussions. ;-)
What zip contents?
HTMLHELP can show HTML pages directly while they are still in a ZIP.
But of course you can override by putting
Robert Riebisch escreveu:
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.
Please find a consensus now with Eric! :-)
I
Just tested it on my Linux system (don't have FreeDOS loaded at the mo') using
groff -man -Thtml .1 .html
..then viewing with elinks (text-only web browser.) You get a table of
contents at the top of the page, but the page itself is very readable.
Looks great.
-jh
On Wed, Apr 9,
14 matches
Mail list logo
