The Megapov demo files, esp. the ones from the Smelehnberg compile
have spaces in the names. I understand that Nathan, Rene and Yvo work
on Windows and Mac and this is no problem for them, but it is a slight
annoyance for Linux users especially if one tries to batch render them
(unless I've missed something :) ). I ended up writing a bash script
to rename them so that all spaces became underscores and it should not
be a problem for me anymore, but still, can you please correct this
small issue in the upcoming release of 0.4? Thanks in advance.

I now have a working set of bash scripts which renders all demo files,
converts them to jpg, creates jpg thumbnails, and makes a web page
with thumbnails and filenames linking to full res images, as well as
the output streams (fatal, render, warning and debug) for the file
currently being rendered, as well as access to the file where verbose
information is being piped. If you're interested (esp. Mark) I will
post it here.


Peter Popov
pet### [at] usanet
ICQ: 15002700

Post a reply to this message

Peter Popov wrote:

> I now have a working set of bash scripts which renders all demo files,
> converts them to jpg, creates jpg thumbnails, and makes a web page
> with thumbnails and filenames linking to full res images, as well as
> the output streams (fatal, render, warning and debug) for the file
> currently being rendered, as well as access to the file where verbose
> information is being piped. If you're interested (esp. Mark) I will
> post it here.

I'm certainly interested in your script.  I had problems with these
files as well and just renamed them rather than mess around with quotes;
I hadn't realized the extent of the problem.

Assuming your script is fairly generic (i.e. useful outside the context
of MegaPov), it might belong in povray.unix.

-Mark Gordon

Post a reply to this message

% cat "File names with spaces can be quoted.txt" > /dev/null

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

On 24 Jan 2000 04:22:55 -0500, Nieminen Juha
<war### [at] punarastascstutfi> wrote:

>% cat "File names with spaces can be quoted.txt" > /dev/null

# b="File names with spaces can be quoted.txt"
# megapov /usr/local/lib/povray31/povray.ini -i"$b"

INI file error.
Bad option syntax or error opening .INI/.DEF file 'with'.

Quoted, but how?!


Peter Popov
pet### [at] usanet
ICQ: 15002700

Post a reply to this message

Peter Popov <pet### [at] usanet> wrote:

> The Megapov demo files, esp. the ones from the Smelehnberg compile
> have spaces in the names. I understand that Nathan, Rene and Yvo work
> on Windows and Mac and this is no problem for them, but it is a slight
> annoyance for Linux users especially if one tries to batch render them
> (unless I've missed something :) ). 

If we get the time, we will go over all example files and do our best to
make them usable on all platforms. 
To do this, please tell the limitations of unix, dos and windows. Is dos
still limited to 8.3 and if so must we keep names so small?

Which platform does allow for spaces, what is the maximum length of a
file name and, if applicable the length of the extention.
Even if an extention is not realy supported on a Mac, we do try to add
for every scene file the extention .pov, this makes things easier to
recognise.

Smellenbergh,



-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

On Mon, 24 Jan 2000 22:11:25 +0100, sme### [at] skynetbe
(smellenbergh) wrote:

>If we get the time, we will go over all example files and do our best to
>make them usable on all platforms. 

Thanks.

>To do this, please tell the limitations of unix, dos and windows. Is dos
>still limited to 8.3 and if so must we keep names so small?

DOS is still 8.3, yes, but DOS 7.0 supports long file names, I think.
I am not sure if Windows of DOS 7.0 itself does the LFN-to-8.3
conversion for "smart short names".

>Which platform does allow for spaces, what is the maximum length of a
>file name and, if applicable the length of the extention.
>Even if an extention is not realy supported on a Mac, we do try to add
>for every scene file the extention .pov, this makes things easier to
>recognise.

On Unix there are no limitations but I think the way POV interprets
the input file name causes a problem. I informed Mark about it and if
the bug is indeed in POV and he is able to fix it then you can apply
the fix in 0.4 instead of going for the filename workaround <grin>

I haven't noticed problems with filenames in Windows.


Peter Popov
pet### [at] usanet
ICQ: 15002700

Post a reply to this message

Peter Popov wrote:

>I haven't noticed problems with filenames in Windows.

Doubleclick a .pov file in explorer. Pov starts but does not load the file. 
This only happens when there is a space in the pov-file. (NT4)


Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/

Post a reply to this message

ingo <ing### [at] homenl> wrote in message
news:8EC64EEEBseed7@204.213.191.228...
> Doubleclick a .pov file in explorer. Pov starts but does not load the
file.
> This only happens when there is a space in the pov-file. (NT4)
>
>
> Ingo
>

Can you confirm this - under win95 there is a no problem double clicking on
long filenames with spaces, but if pov is set for single instance, double
clicking on a file once pov is running does no good (ie it doesn't open). If
pov is not set for single instance, then the file will open up in a second
instance of pov. I wonder if you have mistaken this for your reported
problem?

Post a reply to this message

Tom Melly wrote:

>
>ingo <ing### [at] homenl> wrote in message
>news:8EC64EEEBseed7@204.213.191.228...
>> Doubleclick a .pov file in explorer. Pov starts but does not load the
>file.
>> This only happens when there is a space in the pov-file. (NT4)

>Can you confirm this - under win95 there is a no problem double clicking
>on long filenames with spaces, but if pov is set for single instance,
>double clicking on a file once pov is running does no good ...

This is not the case for me. Pov-Ray is closed when I doubleclick the file 
so Pov should always load it.

Take the file "Bic Patch.pov", in messages is an INI file error:
Bad option syntax or error opening .INI/.DEF file 'Patch.pov'
A tab for a new file is opened with the title 'Bic'

I have the feeling it's a problem with th file association. In application 
for the action I have the line:
D:\Graphics\POV-Ray\bin\pvengine.exe /EDIT

(should have mentioned this in the first post, wasn't realy awake this 
morning)

Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/

Post a reply to this message

On 25 Jan 2000 01:23:17 -0500, ing### [at] homenl (ingo) wrote:

>Doubleclick a .pov file in explorer. Pov starts but does not load the file. 
>This only happens when there is a space in the pov-file. (NT4)
>
>Ingo

It works under Win98.


Peter Popov
pet### [at] usanet
ICQ: 15002700

Post a reply to this message