We should accept here, that Thorsten has put a lot of time and work in the
POV-project,
while we "nebies" just come here and do get all things "on the silver
plate".

I can understand that this is sometimes annoying for him.

However Thorsten, we are grateful for you efforts and patience.

--Theo


"Scott Moore" <sdm### [at] zoomcouk> schrieb im Newsbeitrag
news:kgonlugsq8g3erdttrhqmbrgv9ai2armiv@4ax.com...
> On Thu, 15 Aug 2002 16:40:33 +0200, "Thorsten Froehlich"
> <tho### [at] trfde> wrote:
>
> >In article <9qanluo85j0pnd96u407t97do34eneupr3@4ax.com> , Scott Moore
> ><sdm### [at] zoomcouk>  wrote:
> >
> >> Does this mean the docs need to be updated to mention that spaces in
> >> the filename aren't allowed?
> >>
> >> (BTW. As I'm mentioning the docs, do all platforms build the source to
> >> pvengine or povray? On Windows the .exe is pvengine - but the docs, as
> >> shown above, suggest it's povray.exe - do the docs need updating for
> >> this also?)
> >
> >The documentation is clear that it is about the command-line version of
> >POV-Ray, not the GUI versions and it does refer you to the GUI version
> >documentation for specifics of those versions.  Where?  Well, in the
> >introduction of the command-line options in section 5 in case you missed
it.
> >
> >If you don't read the documentation carefully and get burned that is not
a
> >bug in POV-Ray but in your method of reading the documentation.  The
> >suggested way to read it is from section 1 to the last section.  It is
not
> >recommended to use it for reference purposes only.  That way you _will_
miss
> >very important details!
> >
> >    Thorsten
>
> I never said there was a bug - I merely asked two questions ... the
> answer of which were no. I guess it's a problem with your method of
> reading emails 8o)
>
> Cheers,
>
> Scott
>

Post a reply to this message