|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Looks like file names are causing problems on Macintosh, and perhaps
other platforms too (all platforms allowing spaces as first character in
file names).
We are aware that this is more an inconvenience than realy a bug but we
might have a solution.
For example if your input file is ' scene.pov' (notice the space in
front) POV-Ray is unable to find that file because while parsing the
option 'Input_File= scene.pov', the space is thrown away.
Why not not change the option parser in a way that options can be
enclosed like this:
Input_File=" scene.pov" and Version="3.1" ,......
Or perhaps allowing it only for library paths, input files, output
files, ..... all options relating to file names.
If an option is enclosed, the parser should take *all* characters,
including spaces.
Would it be hard to implement?
Yvo Smellenbergh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
with pov 3.1a, win95 there is anothr bug here(the same)
//Spider
smellenbergh wrote:
>
> Looks like file names are causing problems on Macintosh, and perhaps
> other platforms too (all platforms allowing spaces as first character in
> file names).
>
> We are aware that this is more an inconvenience than realy a bug but we
> might have a solution.
>
> For example if your input file is ' scene.pov' (notice the space in
> front) POV-Ray is unable to find that file because while parsing the
> option 'Input_File= scene.pov', the space is thrown away.
>
> Why not not change the option parser in a way that options can be
> enclosed like this:
> Input_File=" scene.pov" and Version="3.1" ,......
>
> Or perhaps allowing it only for library paths, input files, output
> files, ..... all options relating to file names.
> If an option is enclosed, the parser should take *all* characters,
> including spaces.
>
> Would it be hard to implement?
>
> Yvo Smellenbergh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
That, i believe, might be because POV-Ray is documented as only supporting US-ASCII,
and
the o-umlaut is outside of that range.
So, how do you specify that character in a POV file so that you can include things
successfully? In theory, you can't use it.
Spider wrote:
> with pov 3.1a, win95 there is anothr bug here(the same)
>
> //Spider
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|