I upgraded to the '268 version and noticed tonight,

Possible Parse Error: Text may not be displayed as expected. Please 
refer to the user manual regarding changes in POV-Ray v3.8 and later.

Can someone point me to the docs for this?

The warning hits on the first 't' in 'text' in this construct I've used 
for decades:

text {
	ttf ArialFont
	label
	0.23,0
	scale 0.02
	translate <-0.080*inches, 0.088*inches, -0.001*inches>
	texture {controlTextureOn}
}

-- 
dik
Rendered 23,533,286,400 of 40,928,716,800 pixels (57%)

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:
> I upgraded to the '268 version and noticed tonight,
>
> Possible Parse Error: Text may not be displayed as expected. Please
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>
> Can someone point me to the docs for this?

The best I could find for this so far were these:

http://news.povray.org/povray.general/thread/%3C5c38071f%241%40news.povray.org%3E/
https://news.povray.org/povray.beta-test/thread/%3C5c2e6746%40news.povray.org%3E/
http://news.povray.org/povray.beta-test/thread/%3C5b17006b%241%40news.povray.org%3E/


I remember there was a lot of stuff going on trying to fix the long-standing
utf-8 bug.

Maybe use that as a hook?   Check bug reports? Flyspray, git, readme, ....

Or just stop breaking POV-Ray.   :D

Post a reply to this message

Op 13/11/2019 om 03:05 schreef Dick Balaska:
> I upgraded to the '268 version and noticed tonight,
> 
> Possible Parse Error: Text may not be displayed as expected. Please 
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
> 
> Can someone point me to the docs for this?
> 
> The warning hits on the first 't' in 'text' in this construct I've used 
> for decades:
> 
> text {
>      ttf ArialFont
>      label
>      0.23,0
>      scale 0.02
>      translate <-0.080*inches, 0.088*inches, -0.001*inches>
>      texture {controlTextureOn}
> }
> 

I am not often using text, so I am probably wrong, but comparing to the 
wiki: http://wiki.povray.org/content/Reference:Text  I miss the double 
quotes. Shouldn't one write: ttf ""ArialFont.ttf" "label"  ?

-- 
Thomas

Post a reply to this message

Op 13/11/2019 om 03:05 schreef Dick Balaska:
> I upgraded to the '268 version and noticed tonight,
> 
> Possible Parse Error: Text may not be displayed as expected. Please 
> refer to the user manual regarding changes in POV-Ray v3.8 and later.
> 
> Can someone point me to the docs for this?
> 
> The warning hits on the first 't' in 'text' in this construct I've used 
> for decades:
> 
> text {
>      ttf ArialFont
>      label
>      0.23,0
>      scale 0.02
>      translate <-0.080*inches, 0.088*inches, -0.001*inches>
>      texture {controlTextureOn}
> }
> 

I am not often using text, so I am probably wrong, but comparing to the 
wiki: http://wiki.povray.org/content/Reference:Text  I miss the double 
quotes. Shouldn't one write: ttf "ArialFont.ttf" "label"  ?

-- 
Thomas

Post a reply to this message

Thomas de Groot <tho### [at] degrootorg> wrote:

> I am not often using text, so I am probably wrong, but comparing to the
> wiki: http://wiki.povray.org/content/Reference:Text  I miss the double
> quotes. Shouldn't one write: ttf "ArialFont.ttf" "label"  ?

Good catch - I read right through that, as "I've been using it for decades"
makes me assume it's not the issue, and so I jump past the surface to something
deeper.

from:
http://wiki.povray.org/content/Reference:Text

The syntax is:

TEXT_OBECT:
  text {
    ttf "fontname.ttf/ttc" "String_of_Text"
    Thickness, <Offset>
    [OBJECT_MODIFIERS...]
    }
Where fontname.ttf or fontname.ttc is the name of the TrueType font file. It is
a quoted string literal or string expression.



Maybe POV-Ray thinks that ArialFont is a string expression - an identifier - and
burps when it's not defined the way it thinks it should be?

Who knows what dark magic lurks in the Balaska scene files...

Post a reply to this message

On 11/12/19 9:59 PM, Bald Eagle wrote:
> 
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>> I upgraded to the '268 version and noticed tonight,
>>
>> Possible Parse Error: Text may not be displayed as expected. Please
>> refer to the user manual regarding changes in POV-Ray v3.8 and later.
>>
>> Can someone point me to the docs for this?
> 
> The best I could find for this so far were these:
> 
> http://news.povray.org/povray.general/thread/%3C5c38071f%241%40news.povray.org%3E/
> https://news.povray.org/povray.beta-test/thread/%3C5c2e6746%40news.povray.org%3E/
> http://news.povray.org/povray.beta-test/thread/%3C5b17006b%241%40news.povray.org%3E/
> 
> 
> I remember there was a lot of stuff going on trying to fix the long-standing
> utf-8 bug.
> 
> Maybe use that as a hook?   Check bug reports? Flyspray, git, readme, ....
> 
> Or just stop breaking POV-Ray.   :D
> 
> 

Thanks much for those!
I was off minecrafting last January or I would have chimed in about 
"multiple engines with one gui". (I always wanted to wrap hgpovray with 
my gui.)

Looking at the povray source code, the solution is to change all of my 
files to

#version 3.8;

and leave my text {} objects exactly as they are.

---------------------------------------------------------
On 11/13/19 7:05 AM, Bald Eagle wrote:>
 > Thomas de Groot <tho### [at] degrootorg> wrote:
 >
 >> I am not often using text, so I am probably wrong, but comparing to the
 >> wiki: http://wiki.povray.org/content/Reference:Text  I miss the double
 >> quotes. Shouldn't one write: ttf "ArialFont.ttf" "label"  ?
 >
 > Good catch - I read right through that, as "I've been using it for 
decades"
 > makes me assume it's not the issue, and so I jump past the surface to 
something
 > deeper.


It is double quoted. My bad for not including the defines in my original 
snippet.  I thought it would clutter.

#declare TtRootDir="../"; // because I'm in a subdir


#declare TtCommonDir=concat(TtRootDir, "ttCommon/");
#declare ArialFont=concat(TtCommonDir, "arial.ttf");

equals
     text {
         ttf "../ttCommon/arial.ttf"
     ...

-- 
dik
Rendered 23,657,702,400 of 40,928,716,800 pixels (57%)

Post a reply to this message

On 11/13/19 9:21 AM, Dick Balaska wrote:

> 
> Looking at the povray source code, the solution is to change all of my 
> files to
> 
> #version 3.8;
> 
> and leave my text {} objects exactly as they are.
> 

Well poo.

Changing my SDL from #version 3.7 to 3.8 causes the image to be much darker.
I can't do that.  I'd have to re-render 6 months worth of frames.

(and the annoying not-an-error "possible error" comes through as a 
"mGenericStatus" message (normally the 'Rendered 10 of 20 pixels (50%)' 
messages) so it shows up in the povwin status bar.  This confuses my 
renderfarm progress bars, which resize bigly to display the message that 
shouldn't even be there.)

--
dik
Rendered 23,734,425,600 of 40,928,716,800 pixels (57%)

Post a reply to this message

Dick Balaska <dic### [at] buckosoftcom> wrote:

> (and the annoying not-an-error "possible error" comes through as a
> "mGenericStatus" message (normally the 'Rendered 10 of 20 pixels (50%)'
> messages) so it shows up in the povwin status bar.  This confuses my
> renderfarm progress bars, which resize bigly to display the message that
> shouldn't even be there.)

Isn't there a message pane switch that can be toggled to shut things like that
off?

Post a reply to this message

"Bald Eagle" <cre### [at] netscapenet> wrote:

> Isn't there a message pane switch that can be toggled to shut things like that
> off?

http://wiki.povray.org/content/Reference:Text_Output_Options#Text_Streams

Post a reply to this message

On 11/14/19 2:27 AM, Dick Balaska wrote:
> On 11/13/19 9:21 AM, Dick Balaska wrote:
> 
>>
>> Looking at the povray source code, the solution is to change all of my 
>> files to
>>
>> #version 3.8;
>>
>> and leave my text {} objects exactly as they are.
>>
> 
> Well poo.
> 
> Changing my SDL from #version 3.7 to 3.8 causes the image to be much 
> darker.
> 

One of the changes 3.7 to 3.8 was to take the default ambient to 0.0. 
It's a funky color adder disconnected from gamma handling, and at 0.1, 
it tends to brink near blacks way up in intensity with AG 1.0 - washing 
out the contrast in the images. Your 1.7 AG is already compensating for 
this effect to a large degree.

Have you tried changing the default ambient back to 0.1 when changing 
your version to 3.8?

Bill P.

Post a reply to this message