I don't remember how I managed to do it, but somehow my font in TW has been changed to some type of musical score notes. Needless to say it makes TW impossible to use and very difficult to find the way to change it back. Does anyone know of an easy fix for this? I've gone as far as to completely delete every trace of TW from my system and reinstall it, but the font remains the same...
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
Open the Tools menu, then Options/Content/Advanced. I have "allow pages to choose their own font" checked & Western (ISO-8859-1) chosen.
TW seems to have a problem with cache write, crash on quit. I wrote protected the 0-F cache files, so they never get updated, solved the quit crash for me. In the beginning, we were told TW works best on FFS, this has been proven true by me & at least one other. Auto scroll is my only issue now. Posted from TW.
Look, only one leg, count em, one! X1000/PA6T@1800MHz/2Gb/Radeon 4850
That's too bad because for me it's very fast, fairly robust, and if it weren't for the current font problem, I'd be using it as my main browser. Only because we don't have a port of Google Chrome.
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
It does not, I was thinking it was wast of time, there are other web browser that are fast and stable. Odyssey (MuiOWB), and NetSurf, so if you can't get TimerWolf to work stable its not some to cry about.
@Sundown
Quote:
I wrote protected the 0-F cache files, so they never get updated, solved the quit crash for me.
Interesting fix, I have not tried it yet, but I will try to write protect the cache files to see if problem disappear, thanks. I use SFS2, because FFS is slow.
@Valiant
Quote:
That's too bad because for me it's very fast
I agree its faster, but its not robust.
Sticky scroll bars, annoying but you don't notice if you only use the mouse scroll wheel, and the crash on exit.
Quote:
Only because we don't have a port of Google Chrome.
Chrome rendering engine is based on OWB
@Belxjander
Quote:
You might find yourselves quite surprised as it is down to the extensions and options as to how fast/stable TimberWolf really is.
I don't remember what extentions I'm using, I will check when I have the time.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
TimberWolf when set to UTF8 encoding can display Musical notes as readily as Japanese or Chinese along with Russian and English.
No, not because I want to. I tried taking everything font-related out of prefs.js like you told me this morning in irc, but TW put UTF8 back in. Grrr...
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
so if you can't get TimerWolf to work stable its not some to cry about.
His post was NOTHING to do with Timberwolf stability. i.e. Your original reply was totally off-topic. (If you want to moan about Timberwolf then you can create a new thread - no need to pollute an existing thread with irrelevant moaning.)
Sticky scroll bars, annoying but you don't notice if you only use the mouse scroll wheel, and the crash on exit.
The sticky scroll bar is a feature! And it hasn't crashed on exit here for a long time. So it may not be robust for you, but for Sundown, who uses it extensively and knows all its quirks, and I it is very robust.
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
Thanks for your suggestion, it led me to cause of the problem. I had run the font cache right after I installed TW for the very first time with no problems. But while doing it now it said that _TrueType had failed. Looking in the _TrueType dir, I found something called Score.ttf. Don't know where that came from, but after taking that out and running font-cache again TimberWolf works well for me once more. Thanks to everyone for your assistance and suggestions.
Valiant@Camelot AmigaOne XE, 800Mhz, 1GB, 9250 Radeon, OS4.1u7 Sam440ep, 666Mhz, 512Mb, 9250 Radeon, OS4.1u6 A1-X1000, 1.8Ghz, 1GB, 9250 Radeon, OS4.1x A1-X5000/40 2.2Ghz, 2GB, Radeon HD 7700, OS4.1 FE ud 2
Interesting fix, I have not tried it yet, but I will try to write protect the cache files to see if problem disappear, thanks. I use SFS2, because FFS is slow.
I agree FFS is very slow vs SFS, which is why I made a 500Mb FFS partition for TW only. Why, because we were told the ,sqlite files worked 100% on FFS. I'm sure this is why TW runs faster then on an SFS partition. The other issue with a non start or GR on start is that the CurrentUserProfile "places.sqlite" file spins off new extentions on startup. These temp extentions should get deleted when TW quits, sometimes they don't. If I get a start up problem, I make sure "places.sqlite" is the only one that exists, just delete any other "places" extentions & re-start.
Look, only one leg, count em, one! X1000/PA6T@1800MHz/2Gb/Radeon 4850
System font flaws don't help, should be a lot easier to add fonts & not worry about a cache setting.
To be fair, the font cache in this case is to do with fontconfig. It has absolutely nothing to do with the OS (which manages font caches just fine without that horrid slow scanning that fontconfig insists on)
I believe fontconfig is supposed to detect when the fonts need rescanning - at least Qt and OWB appear to be able to manage this (although it's a bit hit-and-miss as to whether the re-scan actually works).
It would be better if we had a native wrapper for fontconfig, which used the diskfont cache, although I'm not sure whether that is possible (never used fontconfig myself).