Or, if it is broke, don't break it worse. ...
.
I don't think you've been on TER long enough to have gone through some of their major updates. I call them upDATES, not upGRADES because they didn't always go very well. TER did not ask users what they wanted or didn't want and new code often conflicted with old code. ... And here we are.
.
Also, you said, "I'll bet there's a way to tap a PC's intrinsic resources, including font s...". Well, TER has to work across ALL platforms from PCs to Macs to Linux to Android to iPhone to ... whatever else I'm forgetting to include. Post-update error reports (to the forums) included, "It worked for me on my Mac OS10 but when I upgraded to OS11 TER stopped working." "Stopped working on Chrome for Windows but works on Chrome on my Android phone." and on and on and on. After one major update, there were so many complaints that TER reverted to "TER Classic" while they tried to fix all the problems they created. As I recall, a lot of old posts were lost during one update and never recovered.
.
I don't think that adding new fonts that will work seamlessly across all platforms is as easy as you think. Is uni-code really uni-versal? If TER has to patch it in, it will NOT be easy or guaranteed to work at all.
.
I think TER should ask users for our input regarding our experiences with free open source forum software, which ones we like, don't like, and why. Migration will be a BIG headache but a ONE TIME headache. In the meantime, ...
.
IF IT AIN'T BROKE, DON'T BREAK IT!
Posted By: vigerous
Re: Open Source Forums and Databases
Thanks for the feedback. I was puzzled when I looked for the typical copyright symbol followed by one of the established forum builders, e.g., © vBulletin Solutions, which most online forums, incl. USASG, use. They used to have s/w to port existing forums built with bubble gum and bailing wire over to their platform. I could see how, given the ads here, that one of the established companies might have restriction, which is where your suggestion comes it.
They could indeed use open source s/w, platformed wherever they want (Cyprus?), and take it from there. However, not only did you ID a solution, you also ID'd the likely barrier to using it: porting their existing data. Years ago when forums started moving to established, purpose-designed forum s/w, there was at least one that I remember that had to inform it's users that all stored attachment (pics, etc.) were lost. Poof. Gone. That destroyed the forum since it was pic heavy by the nature of the forum's raison d'être. Imagine justifying that decision to stakeholders! But that was 10-15 years ago. Things have changed!
And who knows whether structure and s/w notation/documentation best practices were used throughout developing this site, particularly when new features and patches were applied. It could be spaghetti code that can't be ported w/o a truly large human effort, and that means $$, and that means we won't see vBulletin any time soon. But adding three or four editing functions? I'll bet there's a way to tap a PC's intrinsic resources, including fonts that you mentioned, to do that -- a la the dictionaries for spellcheck.