On 8/1/21 7:02 AM, William F Pokorny wrote:
> The ini parsing is somehow different than the command line parsing :-(.
> Hmmm. I guess povray doesn't die during the actual ini parsing of the
> string, maybe it just marks the type incorrectly as a float.
OK. After a day banging around in code and wrapper scripts. On my Ubuntu
20.04 system and I expect most unix/linux/osx, you can declare multiple
strings and constants on the command line and in ini files - no matter
the recent >v3.6 branch. Constants (excepting, for now, the upcoming
povr branch) support only single float precision or a little less.
--- The ini files need to look like:
declare='S3=" jumped=up = 2 times "'
--- The command line. Note extra quotes where spaces in string. The back
slash escaped newline characters are not strictly needed and used for
p380b1 +mv3.8 +iFloatAndStrings.inc \
declare=\'S2=\""bump and"\"\' \
declare=\'S3=\""jumped up = 2 times"\"\'
--- The simplifications and complications
The povr branch - for some fix in the past I've not run down - allows
simpler and more conventional command line quoting:
povr +mv3.8 +iFloatAndStrings.inc \
declare=S2=\""bump and"\" \
declare=S3=\""jumped up = two times"\"
There are wrapper script complications which had me chasing my backside
for the better part of yesterday when you have strings with spaces. You
must set the IFS (Internal Field Separator) environment variable in such
scripts to newline characters.
With shell / 'sh' povray wrapper scripts this is done by adding two
lines ahead of the use of the $@ argument passing / pass-through. Note,
there is below, an invisible newline character between the single quotes.
In bash / 'bash' povray wrapper scripts you need to add a similar
setting with a single line ahead of the $@ use:
Expect other shell languages would need adjustments too and there are
probably alternate methods to preserver the spaces. I'm a hack at shell
Post a reply to this message