POV-Ray : Newsgroups : povray.binaries.images : New Characters for Master of Puppets Font Server Time
28 Mar 2024 14:10:50 EDT (-0400)
  New Characters for Master of Puppets Font (Message 8 to 17 of 27)  
<<< Previous 7 Messages Goto Latest 10 Messages Next 10 Messages >>>
From: Alain Martel
Subject: Re: New Characters for Master of Puppets Font
Date: 6 Apr 2022 10:01:36
Message: <624d9d40$1@news.povray.org>
Le 2022-04-06 à 08:27, jr a écrit :
> hi,
> 
> "Dave Blandston" <IsN### [at] protonmailch> wrote:
>> ...
>> #declare MOP_UseFrenchQuoteMarks = yes;
>>
>> Let me know if I didn't do it right...
> 
> you didn't do it right !!  :-)
> 
> File 'mopfont.inc' line 3704: Parse Error: Unable to file seek in macro.
> Fatal error in parser: Cannot parse input.
> Render failed
> 
> attached renders fine until enabling the new quotes.
> 
> 
> regards, jr.

When I try to render your scene, I get this error on line 520 of 
MasterOfPuppetsFont.inc :

«Parse error: No matching }, ; found instead.»
          #local A1 = 2 * ComputeCornerLength (180 + A_A0, 0, R, 
CornerRadius); //Width of flat part


Post a reply to this message

From: Alain Martel
Subject: Re: New Characters for Master of Puppets Font
Date: 6 Apr 2022 10:07:24
Message: <624d9e9c$1@news.povray.org>
Le 2022-04-05 à 22:14, Dave Blandston a écrit :
> Alain Martel <kua### [at] videotronca> wrote:
>> How about the French quotes ? « »
> 
> 
> That was a great idea! Support for French quotes has been implemented. Just set
> this variable in your scene file:
> 
> #declare MOP_UseFrenchQuoteMarks = yes;
> 
> Let me know if I didn't do it right...
> 
> Kind regards,
> Dave Blandston
> 

Sorry, but, I can't use your font.
I get this error on line 520 of MasterOfPuppetsFont.inc :

«Parse error: No matching }, ; found instead.»
          #local A1 = 2 * ComputeCornerLength (180 + A_A0, 0, R, 
CornerRadius); //Width of flat part

Latest official version 3.8 under Windows 11.


Post a reply to this message

From: jr
Subject: Re: New Characters for Master of Puppets Font
Date: 6 Apr 2022 10:50:00
Message: <web.624da6b580354cb3fc0c8de6cde94f1@news.povray.org>
hi,

Alain Martel <kua### [at] videotronca> wrote:
> > ...
> > File 'mopfont.inc' line 3704: Parse Error: Unable to file seek in macro.
> > ...
>
> When I try to render your scene, I get this error on line 520 of
> MasterOfPuppetsFont.inc :
>
>           #local A1 = 2 * ComputeCornerLength (180 + A_A0, 0, R,
> CornerRadius); //Width of flat part

> Latest official version 3.8 under Windows 11.

my bad, the above was using alpha.9945627.  tried 'beta.1' and 'beta.2', both
same as the alpha, all on a Slackware GNU/Linux box.  interestingly, WFP's
'povr' sees same/similar error as yours, but on a different line.  </grin>

File 'mopfont.inc' line 578:
Parse Warning:
Should have at least 2 objects in csg.
File 'mopfont.inc' line 577:
Possible Parse Error:
Unmatched {
File 'mopfont.inc' line 578:
Parse Error:
No matching }, ; found instead


regards, jr.


Post a reply to this message

From: Dave Blandston
Subject: Re: New Characters for Master of Puppets Font
Date: 6 Apr 2022 16:30:00
Message: <web.624df77580354cb3ee1b05ae607c1b34@news.povray.org>
"jr" <cre### [at] gmailcom> wrote:
> hi,
>
> you didn't do it right !!  :-)
>
> File 'mopfont.inc' line 3704: Parse Error: Unable to file seek in macro.
> Fatal error in parser: Cannot parse input.
> Render failed
>
> attached renders fine until enabling the new quotes.
>
>
> regards, jr.


Oh my, I think this may be an issue with different versions of POV-Ray. I'm
still using version 3.7. Those error messages that you guys are getting don't
seem to make sense but I don't have version 3.8 installed to duplicate the
problem. I tried your scene without any changes except I put the version back to
3.7 and added a plain white texture to the objects and here's what I got:

(I really like the quote, by the way!)


Post a reply to this message


Attachments:
Download 'quote1.png' (35 KB)

Preview of image 'quote1.png'
quote1.png


 

From: Dave Blandston
Subject: Re: New Characters for Master of Puppets Font
Date: 6 Apr 2022 16:30:00
Message: <web.624df7bf80354cb3ee1b05ae607c1b34@news.povray.org>
And enabling the French quotes:


Post a reply to this message


Attachments:
Download 'quote2.png' (35 KB)

Preview of image 'quote2.png'
quote2.png


 

From: jr
Subject: Re: New Characters for Master of Puppets Font
Date: 7 Apr 2022 09:30:00
Message: <web.624ee63d80354cb35834ab476cde94f1@news.povray.org>
hi,

"Dave Blandston" <IsN### [at] protonmailch> wrote:
> Oh my, I think this may be an issue with different versions of POV-Ray. I'm
> still using version 3.7. Those error messages that you guys are getting don't
> seem to make sense but I don't have version 3.8 installed to duplicate the
> problem. I tried your scene without any changes except I put the version back to
> 3.7 and added a plain white texture to the objects and here's what I got:

same here, v3.7.0.8 works when making those changes.  it would be useful to hear
a developer's view.  (is there a reason you do not want to run v3.8?)


> (I really like the quote, by the way!)

"ancient wisdom"  ;-)


regards, jr.


Post a reply to this message

From: Alain Martel
Subject: Re: New Characters for Master of Puppets Font
Date: 7 Apr 2022 10:38:39
Message: <624ef76f$1@news.povray.org>
Le 2022-04-06 à 16:26, Dave Blandston a écrit :
> "jr" <cre### [at] gmailcom> wrote:
>> hi,
>>
>> you didn't do it right !!  :-)
>>
>> File 'mopfont.inc' line 3704: Parse Error: Unable to file seek in macro.
>> Fatal error in parser: Cannot parse input.
>> Render failed
>>
>> attached renders fine until enabling the new quotes.
>>
>>
>> regards, jr.
> 
> 
> Oh my, I think this may be an issue with different versions of POV-Ray. I'm
> still using version 3.7. Those error messages that you guys are getting don't
> seem to make sense but I don't have version 3.8 installed to duplicate the
> problem. I tried your scene without any changes except I put the version back to
> 3.7 and added a plain white texture to the objects and here's what I got:
> 
> (I really like the quote, by the way!)
Yes. It works using version 3.7, but not when using version 3.8.
Strange...


Post a reply to this message

From: William F Pokorny
Subject: Re: New Characters for Master of Puppets Font
Date: 7 Apr 2022 11:02:27
Message: <624efd03$1@news.povray.org>
On 4/6/22 10:44, jr wrote:
> my bad, the above was using alpha.9945627.  tried 'beta.1' and 'beta.2', both
> same as the alpha, all on a Slackware GNU/Linux box.  interestingly, WFP's
> 'povr' sees same/similar error as yours, but on a different line.  </grin>
> 
> File 'mopfont.inc' line 578:
> Parse Warning:
> Should have at least 2 objects in csg.
> File 'mopfont.inc' line 577:
> Possible Parse Error:
> Unmatched {
> File 'mopfont.inc' line 578:
> Parse Error:
> No matching }, ; found instead

The issue is the newer versions of the parser see the second of two 
semicolons - ';;' - as meaningful.

This partly due parser optimizations / changes. It's also a good idea 
for ';;' to cause parse errors as the extra semicolons - from macros 
especially - can cause difficult to understand behavior where unluckily 
positioned in the SDL.

---
The definition of the ComputeCornerLength macro ends with:

abs (L0 * cos (radians (MiddleAngle)));

It should be something like:

(abs (L0 * cos (radians (MiddleAngle))))

given it's calculating a return value.

Bill P.


Aside: My current povr issues warnings for the bounded_by usage in the 
include file. This user bounding is likely getting stripped given +UR 
now long the default. My v3.7 and v3.8 official versions issue no 
warnings at all(a). I don't remember making any changes specifically to 
get the warnings - FWIW.

(a) - Despite claims all user bounding is getting stripped by default, 
there are a few obscure exceptions in the official versions of POV-Ray 
where user bounds are respected no matter the +ur/-ur settings. The povr 
fork changed the code so +ur/-ur always strips the user bounding, or 
not, on the +ur/-ur setting. It might be the difference in warnings here 
is due bounded_by usage that happens to be one of the v3.7/v3.8, 
official release, 'hidden / always use a user's bounded_by' exceptions. 
I didn't investigate.


Post a reply to this message

From: Dave Blandston
Subject: Re: New Characters for Master of Puppets Font
Date: 7 Apr 2022 15:30:00
Message: <web.624f3ad380354cb3ee1b05ae607c1b34@news.povray.org>
William F Pokorny <ano### [at] anonymousorg> wrote:
> The definition of the ComputeCornerLength macro ends with:
>
> abs (L0 * cos (radians (MiddleAngle)));
>
> It should be something like:
>
> (abs (L0 * cos (radians (MiddleAngle))))
>
> given it's calculating a return value.


Thank you Bill! That works for version 3.7 and I hope it works for everyone else
as well. I posted the updated file. It's been my experience that different
macros seem to need to return values in different ways, and each macro requires
some experimentation to figure what will work for that particular one. Sometimes
the semicolon needs to be inside the macro, sometimes it needs to be outside,
sometimes the parenthesis method works and sometimes not, and I even have one
macro that I use regularly that can't seem to return a value at all - I have to
assign the value to a global variable inside the macro then access that
variable. I guess that's one of the charms of the particular build of POV-Ray
that I'm using.

Regarding the bounded_by feature, I made that particular object so long ago that
I don't even remember if I was using the command line switches or not. The
Metallica logo was the first object I made with POV-Ray about thirty years ago.

Have a wonderful day everyone!

Kind regards,
Dave Blandston


Post a reply to this message

From: Cousin Ricky
Subject: Re: New Characters for Master of Puppets Font
Date: 7 Apr 2022 22:54:32
Message: <624fa3e8$1@news.povray.org>
On 2022-04-07 11:02 (-4), William F Pokorny wrote:
> 
> Aside: My current povr issues warnings for the bounded_by usage in the
> include file. This user bounding is likely getting stripped given +UR
> now long the default. My v3.7 and v3.8 official versions issue no
> warnings at all(a). I don't remember making any changes specifically to
> get the warnings - FWIW.
> 
> (a) - Despite claims all user bounding is getting stripped by default,
> there are a few obscure exceptions in the official versions of POV-Ray
> where user bounds are respected no matter the +ur/-ur settings. The povr
> fork changed the code so +ur/-ur always strips the user bounding, or
> not, on the +ur/-ur setting. It might be the difference in warnings here
> is due bounded_by usage that happens to be one of the v3.7/v3.8,
> official release, 'hidden / always use a user's bounded_by' exceptions.
> I didn't investigate.

I decided long ago to sidestep bounded_by issues by avoiding bounded_by
altogether. When I need to bound something manually, I just do an
intersection with the bounding shape.


Post a reply to this message

<<< Previous 7 Messages Goto Latest 10 Messages Next 10 Messages >>>

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.