We could design our own imageset and apply it to any theme from the administration panel. It's pretty nifty. We would simply need to decide on a banner size (width x height), and a format (I prefer .png personally, but I'm a dork -- just please please no .gif. That format needs to die already, it's outlived its useful life, and really ought to be replaced by animated .png or the CSS trick I obsessed over in my last post). The rest would involve me writing a javascript (or php file, it depends on which one would be most suitable to the particular theme) that picks a random banner from a "banners" folder whenever the page loads. Once we pick a theme or two, we could get rid of all the others and only allow users to pick from a couple specific themes. BFFC, TDH, and MandoMercs each have one theme, period, if I remember correctly, and don't allow user theme-switching...which is really for the best when trying to guarantee a stable, consistent user experience.
Also, Lyat'aag, you don't happen to be using a beta version of Firefox or anything, do you? I know some of the beta chains don't support certain features, in favour of alternate features...
Firefox 3.6.13 for Windows and Mac both show the font...maybe a Greasemonky script or something? Something that interferes with the CSS loading on this site would definitely be detrimental to the existence of the font...
Also, Ubuntu appears to prefer a different implementation of @font-face, as per
http://font.ubuntu.com/web/, so I'll try out that implementation and see what kinds of results I get.
<EDIT>
Apparently, that font loader is just a suggestion, and relies on Google having the font you want to use uploaded and available...so I can't use it with the mandalorian font. More research is needed.
Oh, hey, I found a test page. Please visit
this link in your browser, and let me know which ones show up in a fancy font, and which ones show up in a block-type font. This will help me put a patch over the hole you fell through.
There are so many nuances to making this thing work cross-browser, and apparently I missed one (or multiples) of them...
Also, I forgot to mention, please make sure you're viewing the forum using the Prosilver (default) theme when checking the mando font, for now. I've only coded it into the Prosilver theme so far, since it's the default. Once we decide on another theme and make modifications to it, I'll scoot my changes to the new theme as well.
It's weird, because really the only difference between the font declaration for the translator's transcriber and the font usage here on the forum is the filepath to the font files. As long as I'm pointing to the right location in the filesystem, it should work, but I've found that if I move the font files and change the filepath (making the filepath a complete hardcoded http://.../.../... straight to the font files doesn't work. The files have to be within the same directory as the css file containing the declaration. I wonder if that could be what's setting it off, maybe the Linux version of Firefox differs ever so slightly in how it deals with filepaths in css files? Really, though, it should be identical to other versions of Firefox, and the only difference would be the code that interfaces with the operating system itself.
I'm confused.
</EDIT>