Take a Windows machine, go to the c:\windows\fonts, make an archive with all *.ttf files.
Take your archive to OS4 and install all the fonts to your system with TypeManager. And no problem anymore with the fonts (you even will have som extra fonts to play with).
This was all I had to do to get rid of all my troubles with OWB (except the known bug of OWB hanging and eating all the CPU when surfing on certain websites).
Does not seem very fun that you need Microsoft copyrighted material to use the browser. Since that means that it can never be shipped as a default browser with the OS unless Hyperion pays a large sum of money to Microsoft for the right to use them.
Can someone with more understanding of these issues comment? This was found in msttcorefonts debian package.
Edit: Imho, providing the original font file that this linux package dowloads as part of the installation will be sufficient (with the license file I pointed to in the link)
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Does not seem very fun that you need Microsoft copyrighted material to use the browser.
The core fonts are not required to use OWB, if a font a web page is using isn't installed OWB uses the DejaVu fonts included in AmigaOS4 instead.
But nearly all web sites, incl. amigans.net (http://www.amigans.net/themes/klesterjr_hnl/styleNN.css ... TR, TD {font-family: Verdana, Tahoma, Arial; ...), use them and if you have them installed the pages look better and as they were intended.
Quote:
Some free to use fonts should be found instead.
The core fonts are free for personal use, the only problem with them is that you are not even allowed to change the archive format, only distributing them in the unchanged .exe CAB archives, as available on sourceforge.net, is allowed. Although most people read the README_AMIGAOS4 included in OWB with the link to my archive with the .otag files for the core fonts it seems most overlooked the readme in that archive, it includes the link to the download section of the sourceforge.net core fonts projects and explains how to extract and install the core fonts TTF files, you don't have to copy them from a Windows or MacOS system.
There is no documentation for the AmigaOS4 port of OWB yet, would be nice if someone writes something better than my readmes which hardly anyone seems to understand
I think most of the problems comes from not installing the .so files, did every one having problem install the .so files, SDL shard objects and libcu and libsdl.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
It's a bug in OWB itself, for example it happens on linux as well. I've fixed the fonts related infinite loop bug of OWB (www.vg.no, several wikipedia.org pages, etc.) now, but I can't fix all OWB bugs myself, "just" porting it to AmigaOS4 is more than enough work already
I've fixed the fonts related infinite loop bug of OWB (www.vg.no, several wikipedia.org pages, etc.) now, but I can't fix all OWB bugs myself, "just" porting it to AmigaOS4 is more than enough work already
Ooh sweeet! Now I don't have to fire up my (less and less used) windoze machine to read the news. Thanks a ton for your hard work J?rg!
Ooh sweeet! Now I don't have to fire up my (less and less used) windoze machine to read the news. Thanks a ton for your hard work J?rg!
You can test it with OWB 1.13 now. But on www.vg.no OWB is still very slow, unless you disable JavaScript.
It works! With Javascript enabled I get a CPU usage varying between approx. 50-80% after the main page is loaded, but the speed is still acceptable. With Javascript disabled it's faaast!!
What is your plans for it from now on? In terms of bookmarks, url completion and such.
A GUI for the settings instead of the tooltyes and env variables and adding more options (fonts, font sizes, proxies, etc.), adding scroll bars (for the window only, not for frames, iframes, textareas, etc., that's something the OWB developers have to add) and adding support for downloads (unless Andrea is faster implementing it ). Adding a simple bookmark should be no problem either, but since OWB has no disk cache URL completition would be limited to the URLs used in the current session.
BTW: OWB 1.13 is in the AmiUpdate database now, using AmiUpdate to install it is much easier since it automatically installs the new shared objects, etc.