What's been said about font copyright is fairly true, but...
(Now forgive me as I'm trying to remember a documentary on the subject I watched a couple of years ago. The following facts I state may be totally off the mark.)
Firstly the translation of a font from it's source to another medium doesn't change or remove the copyright on it. It's covered under the modern rules of copyright as format shifting. While I don't know of any cases dealing with it, I'm sure most lawyers would have no problems in applying it.
Secondly, the licence that users get for use on personal computers is only a personal use licence. There are difference degrees of licence for difference of business. Publishing houses and design firms who use it for their business have to pay much higher fees than the everyday joe who does some DTP for a garage sale signs. How it apply to an open-source creative commons project like Oolite is beyond me.
In real terms both cases really don't apply to my real issue, Font Consistency. (In fact I can't remember the point I was trying to make in the last post.)
I've been seriously thinking about the long term issue of producing a consistent documentation. My goal is product templates that any one can use no matter what OS or application. Ideally someone makes a oxp, should be able to download a template of BerilOS website, drop the text and image in, and have a high quality doc' that matches all other Oolite docs. To give the game a trademark (or is that creative commons
) look.
Unfortunately, fonts are one of the most variable set of features found across the computer spectrum. While all three OSs have a Sans fonts (Hevlica - Mac, Arial - Win, Vera Sans - Linux), each one has slight differences and are general uncommon on the other systems. This is why I've adopted the use of Deja Vu typefaces for the documents I'm creating. DV has many advantages: it licences as GPL/Creative Commons, available for all three OSs, the serif and sans match in style, has some best uni-code support I've seen (Oolite in Canadian Aboriginal or Arabic anyone), and has a narrow versions which is missing from many fonts. While there are some issues, inconsistent family naming across the OS's being one, it does seem to me to be the best solution.
The fonts in questioin.
Wow, that was long winded. Now for some fun stuff. I'm stuck on the last section of the manual at the mo' (on the combat ranks no less
.) Seeking some respite, I've had a bit of a play with the combat rank badges again.
[Edited... 200708027-10:00 +13gmt]
In order we have (reading left-to-right then row-by-row):
Harmless, Mostly Harmless, Poor, Average
Above Average, Competent, Dangerous, Deadly
Elite, multi-coloured specials 1, multi-coloured specials 2, Supreme Commander.
I've only did one `wing' for speed, but having a second look, I think the they could work quite well on the BB as they are.
(I'll blame a late night and storm induced sinus headache on that stuffup on that one Daddy Hoggy.)
[End Edit.]
That's it for now, I'm going to bed and wonder how to explain the fact that GCW would not only condone the act of executing of criminal without trial but include it as part of the Commanders' Profile info.