 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 24 Jan 2000 05:51:13 -0800, Ken wrote:
>
>
>Marc Schimmler wrote:
>
>> A few months ago I would have disagreed but now I can only support .pdf.
>> It's quite useful as an online doc. I like the official one very much
>> now.
>
>I don't mind .pdf all that much but the only free tool that I know of
>to read them (Adobe Acrobat) really sucks big time in my opinion.
GhostScript can read PDF as well, but I think it's even harder to use,
UI-wise.
--
These are my opinions. I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Just to comment on that, layers aren't supported by many browsers, e.g.
>mozilla does not support this netscape HTML-enhancement.
Oh, I know that... I was just being selfish. <g>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dear Mr.Nathan Kopp
I am a Japanese,and Official manual is very difficult to uderstand for me.
So in my case,
I take out mainly Syntax from manual and put them into header of source file.
And I check Token.c,Parser.c etc. files,
and I add comments(Of cource Japanese) each function,pattern and so on.
Now I make all images of all functions,pattern and so on,
then I can not make pattern of "facets" inside pigments,
so I check source and add only use inside "normal" message like this.
I hope plain text is better.
I attach half way of my manual of functions.
Of cource I put this in source file.
Y.Tanabe
Kobe,Japan
Nathan Kopp wrote:
> What would be the desired format for MegaPov documentation for Windows and
> Unix?
>
> Available formats to choose from:
>
> WordPerfect
> MS Word 97
> MS Word (simple, read by WordPad)
> PostScript
> PDF (only if I can generate it with free tools)
> HTML (export from MS Word)
> Some other format that I could easily generate from a MS Word file using
> free tools.
>
> (Sorry, but I don't have any tools to generate HLP files for Windows.)
>
> -Nathan
Post a reply to this message
Attachments:
Download 'manual.doc.txt' (18 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan Kopp <Nat### [at] Kopp com> wrote ...
>
> What would be the desired format for MegaPov documentation for Windows and
> Unix?
>
I guess I worded that poorly. I was hoping for answers like:
"I use unix, and I'd like _____."
or
"I use Windows, and I'd like ______."
For example, the Windows people might like HLP (if I can figure out how to
use it) or Wordpad, but the unix people might prefer HTML or PS.
Of course, I'll have to figure out some good primary format that both myself
and the Smellenbergh brothers can work on and then export/import to the
other formats.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"I use Windows, and I'd like HLP."
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Glen Berry <7no### [at] ezwvcom> wrote...
> I think it might also be nice to allow end-user modification of the
> help file. If the help file is in a modular HTML format, it would be
> possible for the end-user to add some new pages, correct a typo on an
> existing page, or make whatever personal notes they wanted. It would
> become more of a personalized "workbook" in a sense. I can't do these
> things to a PDF, PostScript, or Windows Help document.
The problem with multiple files is that they are more difficult to maintain
and distribute than a single file that contains the entire document.
> As for Windows users of MegaPov, it might be nice to simply launch a
> Windows Help file, but I can easily live without this if it will be
> too much work to create.
Like I said, if I can get free tools to export from a word processor to HLP,
I'll give it a try. I'll try that tool that Tony recommended.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 24 Jan 2000 06:30:41 -0800, Ken wrote:
> "I use Windows, and I'd like HLP."
I use Windows and Unix, and I'd like DocBook because you can easily transform
it into PDF, HTML, RTF, TeX, and lots of other formats.
--
These are my opinions. I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I use Windows and I prefer HTML.
Jim
--
Nathan Kopp <Nat### [at] Koppcom> wrote in message
news:388b6675@news.povray.org...
>
> What would be the desired format for MegaPov documentation for Windows and
> Unix?
>
> Available formats to choose from:
>
> WordPerfect
> MS Word 97
> MS Word (simple, read by WordPad)
> PostScript
> PDF (only if I can generate it with free tools)
> HTML (export from MS Word)
> Some other format that I could easily generate from a MS Word file using
> free tools.
>
> (Sorry, but I don't have any tools to generate HLP files for Windows.)
>
> -Nathan
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>I am a Japanese,and Official manual is very difficult to uderstand for me.
>So in my case,
>I take out mainly Syntax from manual and put them into header of source
file.
>
>And I check Token.c,Parser.c etc. files,
>and I add comments(Of cource Japanese) each function,pattern and so on.
>Now I make all images of all functions,pattern and so on,
>then I can not make pattern of "facets" inside pigments,
>so I check source and add only use inside "normal" message like this.
>
>I hope plain text is better.
>I attach half way of my manual of functions.
>Of cource I put this in source file.
:O Bakemono!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Win. HTML.
Couldn't some sort of generic html be made as a single page (file)?
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
