[23 Apr 2010] Hollywood 4.7 now available!

Contains all messages from the Hollywood mailing list between 01/2006 and 08/2012
User avatar
airsoftsoftwair
Posts: 5830
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[27 Apr 2010] Re: Re: Hollywood 4.7 now available!

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Tue, 27 Apr 2010 22:21:17 +0200
Hi!

The catalog was updated? If the answer is positive, can you send me... I would like to update the spanish catalog :)
Yes, here are the new translation files for Hollywood 4.7. Also included are updated German catalogs done by me. I forgot to include these in the Update4_7.lha archive, so the German Hollywood users might want to install them manually.
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[29 Apr 2010] Re: Hollywood 4.7 now available!

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 29 Apr 2010 19:55:14 +0200

I did it!

hehe .. my presentation yeserday was done with "hwbeamer" and Hollywood! (I'm doing my Phd in computer science). Everything went really well and the visualisazion of my algorithm was simply cool (in my opinion). But they all looked at me as if i was insane as i told them that this was done with an Amiga (most of the audience most likely didn't even know what an amiga is) and unfortunately, they weren't too impressed by my hobby itself. Anyway, somehow one gets used to the fact that people smile at you when you mention "Amiga". However, they liked the presentation itself and the visualisation was superior to any powerpoint presentation :-)

The only thing which makes still problems are the TrueType fonts in AmigaOS3.x (I used euae on linux to give the presentation). It looks better on AOS4 and especially,"Open Type Fonts", which should be compatible with TrueType fonts, look wrong on AOS3.x (the font is always too small, looks always "bold", and irregular in the size of each letter), TrueType support is done via ttf.library (version 0.8.5) on AOS3.x.

I know, I could have compiled a binary on AOS4 for AOS3 with Hollywood 4.7, but then i couldn't have done "last minute changes".

Unfortunately, there's still a lot of work to do until others could use hwbeamer.

Nevertheless, I had fun and so, I have to thank Andreas for Hollywood -- it's really a great piece of software.

Tom
User avatar
airsoftsoftwair
Posts: 5830
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[01 May 2010] Re: Re: Hollywood 4.7 now available!

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 01 May 2010 22:33:20 +0200
I did it!

hehe .. my presentation yeserday was done with "hwbeamer" and Hollywood! (I'm doing my Phd in computer science). Everything went really well and the visualisazion of my algorithm was simply cool (in my opinion). But they all looked at me as if i was insane as i told them that this was done with an Amiga (most of the audience most likely didn't even know what an amiga is) and unfortunately, they weren't too impressed by my hobby itself. Anyway, somehow one gets used to the fact that people smile at you when you mention "Amiga". However, they liked the presentation itself and the visualisation was superior to any powerpoint presentation :-)
Great, good to hear :)
The only thing which makes still problems are the TrueType fonts in AmigaOS3.x (I used euae on linux to give the presentation). It looks better on AOS4 and especially,"Open Type Fonts", which should be compatible with TrueType fonts, look wrong on AOS3.x (the font is always too small, looks always "bold", and irregular in the size of each letter), TrueType support is done via ttf.library (version 0.8.5) on AOS3.x.
Yes, but these problems should all be gone now with Hollywood 4.7's new platform independent font engine. Just use #FONTENGINE_INBUILT and fonts will look *exactly* the same everywhere.
I know, I could have compiled a binary on AOS4 for AOS3 with Hollywood 4.7, but then i couldn't have done "last minute changes".

Unfortunately, there's still a lot of work to do until others could use hwbeamer.

Nevertheless, I had fun and so, I have to thank Andreas for Hollywood -- it's really a great piece of software.
Thanks alot *bows*
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[02 May 2010] Re: Hollywood 4.7 now available!

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sun, 02 May 2010 12:41:44 +0200
Yes, but these problems should all be gone now with Hollywood 4.7's new platform independent font engine. Just use #FONTENGINE_INBUILT and fonts will look *exactly* the same everywhere.
I now have looked into the new documentation and indeed, it's even better than i thought, it is :-)

However, Open Type Fonts still don't fully work correctly. It seems that they cannot freely scaled with hollywood? In my application (tested now on AOS4.1update2), I get for that line of code:

Code: Select all

SetLayerStyle("title",{FontSize=1.5*#DEFFONTSIZE})   
the following error message:

"Kann Schrift Latin Modern Sans 17 Regular in Größe 36 nicht öffnen" (Can't open Latin Modern Sans 17 Regular in size 36)

While it works for size 24 and it also works with OS3.1/ttf.library (although ugly) or on AOS4.

The font can be found here:

http://www.gust.org.pl/projects/e-found ... n/download

(Latex uses this kind of font)

regards, Tom
User avatar
airsoftsoftwair
Posts: 5830
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[07 May 2010] Re: Re: Hollywood 4.7 now available!

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Fri, 07 May 2010 22:13:42 +0200
While it works for size 24 and it also works with OS3.1/ttf.library (although ugly) or on AOS4.

The font can be found here:

http://www.gust.org.pl/projects/e-found ... n/download

(Latex uses this kind of font)
Hmm, does this only happen on OS4 or also on Windows?
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[08 May 2010] Re: Hollywood 4.7 now available!

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 10:04:48 +0200
Hmm, does this only happen on OS4 or also on Windows?
I don't know :-) Tell me! I don't have Hollywood for windows and don't use a windows system anyway. At least on AOS4 and AOS3, it seems with #FONTENGINE_INBUILT *every* OpenTypeFont can't be scalled with the command:

Code: Select all

SetLayerStyle(ID,{FontSize=SomeSizeDifferentFromDefault})  
There's no problem with TrueTypeFonts.

Greetings, Tom
User avatar
airsoftsoftwair
Posts: 5830
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[08 May 2010] Re: Re: Hollywood 4.7 now available!

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 11:47:51 +0200
I don't know :-) Tell me! I don't have Hollywood for windows and don't use a windows system anyway. At least on AOS4 and AOS3, it seems with #FONTENGINE_INBUILT *every* OpenTypeFont can't be scalled with the command:

SetLayerStyle(ID,{FontSize=SomeSizeDifferentFromDefault})

There's no problem with TrueTypeFonts.
Here it works fine. I think the error is on your side because you have specified a wrong font name. You have to keep in mind that when using #FONTENGINE_INBUILT Hollywood will read the family name directly from the *.otf/*.ttf file. When you use #FONTENGINE_NATIVE on the other hand, Hollywood will use the name provided by the host system (in your case OS4 or OS3). The TrueType font implementation on OS4/OS3/MOS/ AROS is extremely awkward because it basically allows you to install a font under a random name. For example, you could install Arial.ttf under the name "Bla bla font" without any problems. It's extremely awkward that the OS makes such things user-configurable. So the wisest thing is to always use #FONTENGINE_INBUILT :-)

Now, when looking at the LM sans fonts, you will see that there is no such font as "Latin Modern Sans Regular". Instead, an additional number is part of the family name, e.g.:

Code: Select all

Latin Modern Sans 8 Regular
Latin Modern Sans 10 Regular
Latin Modern Sans 12 Regular
Latin Modern Sans 17 Regular
etc.
So the following will work just fine:

Code: Select all

EnableLayers
SetFont("Latin Modern Sans 9 Regular", 24, {engine = #FONTENGINE_INBUILT})
SetFontStyle(#ANTIALIAS)
TextOut(0, 0, "Title", {Name = "Bla bla bla"})
WaitLeftMouse
SetLayerStyle("title",{FontSize=36})
WaitLeftMouse
End
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[08 May 2010] Re: Hollywood 4.7 now available!

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Sat, 08 May 2010 12:55:18 +0200

I'll try to check that, but the path to the otf-font, was given as an absolute paht "Work:Hollywood/projects/fonts/fontname.otf" and then only the INBUILT-Engine should be used?

But I'll double check it tonight (hopefully).

regards, Tom
User avatar
airsoftsoftwair
Posts: 5830
Joined: Fri Feb 12, 2010 2:33 pm
Location: Germany
Contact:

[10 May 2010] Re: Re: Hollywood 4.7 now available!

Post by airsoftsoftwair »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Mon, 10 May 2010 11:14:19 +0200
I'll try to check that, but the path to the otf-font, was given as an absolute paht "Work:Hollywood/projects/fonts/fontname.otf" and then only the INBUILT-Engine should be used?
Yes, absolute font specifications are only allowed when using the inbuilt engine.
nexus
Posts: 150
Joined: Sun Mar 07, 2010 11:54 am

[13 May 2010] Re: Hollywood 4.7 now available!

Post by nexus »

Note: This is an archived post that was originally sent to the Hollywood mailing list on Thu, 13 May 2010 10:17:32 +0200

Sorry, It took a while until i found the time to more deeply investigate the Problem and now, I found out why .otf AND .ttf Fonts do not always work with the inbuilt engine in Hollywood.

Attached is a test scripts. In "settings.hws", there are four lines for "Const #DEFFONTFAM=.." with different examples when the font works and when not. Please *move* (not copy) the included font to the appropriate location!

It seems the problem is related to the subdir location of fonts. If the font is located in "project-Dir/fonts/somefont.ttf", everything works fine. If the font is located in "project-Dir/fonts/subdir/somefont.ttf",it does not work anymore! Weird! Even more weird, the following command still works:

Code: Select all

SetFont("fonts/subdir/somefont.ttf",24,{Engine=#FONTENGINE_INBUILT})
But the script fails then at that command:

Code: Select all

SetLayerStyle("\\title",{FontSize=1.5*24})
with the error message: "Can't open somefont in size 36"

Moreover, a pitfall is here (and made finding this problem pretty difficult), if you ever have installed "somefont.ttf" in AOS4 in "Fonts:". Then AOS4 has the following files installed:

Code: Select all

Fonts:somefont.font,
Fonts:somefont.otag
Fonts:_TrueType/somefont.ttf 
And the Problem does not arise even if you delete Fonts:somefont.font and Fonts:somefont.otag (also not with a cold reboot)! The problem only appears, if you also delete Fonts:_TrueType/somefont.ttf (or if you never have installed "somefont.ttf" in AOS4!)

Thats the most weird thing because it's a complete different path than specified in the script!

regards, Tom
Locked