What is OpenArena?

OpenArena is a FPS (First Person Shooter) based on the open source Quake III engine (ioquake3). It is open source (GPLv3) and runs on all major operating systems (Linux, Windows, Mac -- so if you're reading this on Windows or a Mac, you can still head over to OpenArena's website, download and play the game!)

How to Install OpenArena in Ubuntu

Installing programs in Ubuntu couldn't be easier, but there are also many ways of doing so.

Ubuntu Software Centre

Go to Applications > Ubuntu Software Centre, search "openarena", click "More Info" and click "Install"

Synaptic Package Manager

Go to System > Administration > Synaptic Package Manager, search "openarena" and double-click to install.

Command Line / Terminal

Open the Terminal via Appliations > Accessories > Terminal and run
sudo aptitude install openarena

Why Upgrade to Version 0.8.5?

OpenArena is available at version 0.8.1 in Ubuntu 9.04 (Jaunty Jackalope), Ubuntu 9.04 (Karmic Koala), Ubuntu 10.04 (Lucid Lynx), so what do you do if you want to play version 0.8.5?

Firstly, why would you want to update the game? Well a lot of bug fixes are usually implemented in patches, including all of these features:

• UI restyling by Udi. In case you have not noticed, OA is now blue!
• New effects: rocket smoke, shotgun sparks, flares.
• New maps include:
  • am_underworks, am_underworks2, hydronex2 from ArmageddonMan
  • blitzkrieg3 from ArmageddonMan and Boczeq
  • oa_koth2 from cosmo
  • ps9ctf, ps37ctf from PsYthe
• Map improvments include ctf_compromise, ctf_gate1, ctf_inyard and oa_minia
• Angelyss team skins are more colorful
• 3 new player skins, one for Beret, one for buttbuttin and one for Angelyss
• New inclusion of the 'Challenge' system. Read here for details about it.
• Empty servers without humans with 'only humans' set is now really really empty
• Voting menu
• Different styles of weapon bars
• Various gameplay bugs fixed, like LMS survivor bug,
• New server admin system as explained here.
• Bots are much improved and understand the gameplay objectives better of the latter gametypes (Harvester, Overload, etc)

How to Apply the 0.8.5 Patch in Ubuntu

Like installing OpenArena in Ubuntu, applying the patch is extremely easy -- however, it's not self-explanatory.

1. Download patch 0.8.5 (40 MB)
2. Create folder .openarena in your home folder
3. Extract the patch so it sits in /user/username/.openarena/baseoa/pak6-patch085.pk3

Then start the game via Applications > Games > OpenArena

Enjoy!

A friend of mine and I helped to publish an online magazine called Interspecies some time ago, where he would do the editing and I would do the publishing. This friend worked with the owner to collect and produce readable copy, who would then turn all the articles over to me, in .txt format at my request, for publishing. I worked in Adobe Illustrator CS2 (I didn't own Adobe InDesign and didn't feel I had much control over Scribus), produced some graphics, integrated some photos, slapped in the text and published to PDF format.

Why did I publish in PDF format? Before PDF was an open standard (ISO/IEC 32000-1:2008) and thus allowed to be openly implemented, the PDF format allowed me, the publisher, to control the design, content, imagery and layout of my publication down to the pixel. The PDF format would encapsulate my images, my vector graphics and even my font-family so that when John The Reader read my publication, it would look exactly the same to him as it did to me.

But what about the seeing-impaired? As a web developer, I try and follow the W3C WAI (Web Accessibility Initiative) and other accessibility standards and initiatives so that I can help aide people who don't have the manual dexterity to use a mouse or people who need a screen reader to view a web page. I've never seen such a person use any of my websites, but I hope by this practice I am making the web just that much more accessible for everyone. But is the PDF format really accessible?

This friend who I did publishing with has finished his undergraduate degree and is on his way to becoming a lawyer. Along the way, he is helping to publish a couple of newsletters (wasn't Barack Obama the editor and then president of the Harvard Law Review? -- just saying) and asked me,

If I am publishing a newsletter online and want people to be able to change fonts (it will be read by the seeing impaired), in what format should I send the newsletter out?

So I responded that the only way I knew how, was to publish on the web and either use (a) JavaScript/HTML/CSS and create buttons for the user to increase or decrease font size or (b) simply publish on the web and let the user use their tools (screen readers, web browser) and let them adjust the font size themselves. For instance, Mozilla Firefox (and many other open source browsers) all the use of [Ctrl] + [+] to increase font size, [Ctrl] + [-] to decrease font size and [Ctrl] + [0] to reset the font size, all on the fly. PDFs do not allow font sizes to be changed, unless you open them in some sort of PDF editor (but who has the time or resources to do that?)

If PDFs are great for strict publishers and the web is better (but not perfect) for accessibility, which one do you choose? What other choices do publishers and editors have to make sure their content can be read by the most amount of people?

Although I published in PDF format in the past, if I were to publish a magazine nowadays, I would publish on the web and allow the user to use their tools to adjust to their viewing needs. That's the suggestion I concluded with for my friend.

What are your thoughts?