Sep 122009
 
No Gravatar

It’s been quite a ride starting the work on Kongoni 2.13.0 and this is our first newsletter detailing what has been happening.

The first important bit is that the votes are in, and the alpha release has been named. The first alpha of Kongoni 2.13.0 will be called: Cicero, named after the great Roman philosopher who gave us the quote “All generalizations are false”. Other proposals had included Kant, but as one developer put it “there is just no way I can say that guy’s name with a straight face”. The reasons for this comment is left as an excercise for the reader.

Of course, Nietzsche is not dead with the work on Cicero starting, updates and expansion continue. This week saw updates to our versions of digikam, KDE and icecat. New ports in the tree include UFRaw, Rawstudio and gsynaptics to name just a few. While Nietzsche will be aging from now on as it’s upstream distro is effectively frozen, it remains a stable platform and we will release updates and expand it continously for as long as we can, and certainly well into the stable cycle for 2.13.0

Our work on 2.13.0 started with updates to portpkg, earlier (during Nietszche’s cycle already) portpkg was expanded (based on work from Kongoni) to include support for slackware’s new txz format as well as a number of small updates to the rest of the system – now came the time to make the portpkg in current synchronize to slackware 13. This change was quite easy on the 32-bit platform and we have already had reports of current-testers successfully running a system after synchronizing with current. The only major hiccup was a bug in the metaport for sharutils which we fixed with our own source-port for sharutils.

The 64-bit platform is trickier as there are a number of things to address. The first challenge was allowing the system to upgrade to the new FHS-compliant directory layout from slackware64 as we are moving away from bluewhite64 as upstream. To this end a new port was created known as kongoni_upgrade_prepare. This port is available in both the current and Nietszche trees, but as it changes your target platform to current, it should not be installed on Nietzsche unless that is your intention (and current is far from stable yet – particularly on 64-bit). This port will remain a core functionality in the future of Kongoni, allowing us to script any fundamental changes to the system that needs to happen prior to an upgrade.

Thus the process to upgrade from Nietzsche to current its: synchronize your ports with Nietzsche, install kongoni_upgrade_prepare, synchronize again (now you will synchronise with slackware 13 and kongoni-current) then upgrade all packages. I would like to extend a personal note of thanks to Eric Hameleers for explaining the steps this port needs to do on 64-bit.

Please note that the kongoni_current ports are, at present, broken for 64-bit – basically all of them. The upgrade_prepare port will let you synchronize to slackware-13 but this is an intermediary step we had to finish first. However, the kongoni_current ports all still use the lib and /usr/lib as directory targets and this could cause issues with running them (I believe they won’t be severe issues and most should work – but be advised that this very risky).

Our next major task will be to hack virtually all the ports in the tree to make them FHS compliant on both platforms which will resolve this issue. We are planning a hackfest sometime in the next two weeks to sit and simply work through them all – one-by-one, and fix them. This will be a face-to-face session with the developers in Cape Town and surrounds. If there is enough outside interest, we’ll extend it over IRC, if you are interested in joining in – please mail me directly and we’ll get a discussion going on location and methodologies to use. The work is quite easy (really easy in fact) there is just a lot of it.

Once that task is completed, we will proceed with our real Cicero innovation stage, this means finalizing the new version of PIG and the enhancements to the installer we are working on. At this stage I don’t want to give an estimation on when Cicero will be released, but I don’t think we’re talking many months.

Finally, some great news: the FSF has officially added Kongoni to their list of fully free GNU/Linux distributions. That means it is now publicly recognized as a fully-free system by the people who define what “fully free system” means.

Sep 092009
 
No Gravatar

Okay, so unlike my work thus far, this album was taken onsite at a rock concert – not an ideal location, but at least it was tripod-friendly. So I decided, instead of trying to enhance realism as before, I was going to have some real fun – and try to capture the spirit of the show with some real artistic expression.

The results are much more experimental and expressive than my other pics – you can’t do this all the time or you’ll just look funny and overkilling, but just sometimes… it’s fun to let go.

So without further ado, my friends and the band.

[nggallery id=6]

Sep 072009
 
No Gravatar

Hello, and welcome to this, the final part of my tutorial series on doing photoediting with GNU/Linux and free software. I say final because after this, we’re getting into the professional arena for which good books are a much better option than blogposts. What I will be covering in this is some basic photographic handling skills and how to do them in the gimp. I won’t be using channels or layers in this tutorial but everything in here remains applicacable when you use them.

A common problem for a photographer when you shoot outside a studio, is that your light and color and backgrounds are not ideal, so we’ll learn how to do some basic corrections, and how to highlight our subject against a cluttered background. Here is a picture I took at the 7thson gig, it was near the end of the show and to get it, I had to use a very high ISO level as the light was fading and I wasn’t using a flash. The price I paid was digital noise – and the background is rather cluttered.
Here you see the image, in UFRaw, with our first bit of highlighting already busy: we’re cropping out some of the wasted stuff.

I’ve not done much else in RAW on this one as the shot was really rather good, I only raised the exposure level very slightly.

Clicking on OK gives us the image in GIMP:

Our first problem is the digital noise that came from using a high ISO level, Gimp has a built-in tool to help correct this, called Despeckle (Filters|Enhance|Despeckle). UFraw also has such a tool but it offers far less control, despeckling costs you detail so you want to aim for an optimum balance to lose as little as possible and maintain a usable picture (if perhaps not a print-quality one).

This gives us a much better picture already. Now we can reduce some of the effects of despeckling by going for a softer-focussed image, for this we use one of GIMP’s most useful tools, the Gausian Blur, with a smallish radius, it just softens the focus enough to smooth out the picture without losing so much detail as to harm it – in fact, it makes it prettier.

Now we want to deal with the background, ripping it out is possible but will cost us all context, instead we just want to remove it’s eye-pulling effect while maintaining it’s presence, so it provides atmosphere rather than interference. I started by removing the drummer’s half visible head (as it contributed nothing) using the clone tool (I cover this in detail below), now for the fun part though – selecting the background outside the guitarist. Gimp offers an easy way to select complex shapes using the Path tool by clicking along the contours you can gradually select out your target.

Now we use Select|From Path to turn our path into a selection. You can also use the lasso tool for this, but only if you have a very steady hand. We will begin by reducing the coloring of the background making it effectively a semi-black-and-white image, thus reducing it’s distracting effect a great deal and making it nice for atmosphere. First we need to adjust our selection a little, we start by shrinking it until it is just inside the border of the guitarist (Select|Shrink Selection) – so we’ll have a smooth transition, then to smooth things further, we feather it (Select Feather) by about 5 pixels.

We invert the selection to select the background around the guitarist rather than the guitarist himself, we open the Hue/Saturation tool from the colors menu.  and drop the saturation a good deal – this gradually reduces the coloring of the background, until we get a near black-and-white effect with just enough color to still look nice.

Below, you can see the results, already an improvement, but there’s a catch – look at the guitar cable, it’s now much brighter on the player’s leg, and thus causes a problem, luckilly the way it runs, if we remove it, it will just appear that it ran behind him – so we have an easy answer, just get rid of it.

For this we use gimp’s clone tool. Cloning lets us take one part of the image and paint over another with it, it’s a powerful tool but at it’s most basic, using a feather-edged brush of about 35-pixel diameter and the aligned mode, it lets us quickly paint out the cable using the surrounding denim.

Now all we do is another small gausian blur to remove the edges from the changes we made, and here we have our final result, it’s pretty, it’s got atmosphere and we’ve turned a bad-luck shot into a work of art.

Sep 072009
 
No Gravatar

D34r Dr Grammar,

I red a bl0gpst 2day that sed txtspk is stoop n wus sayin’ why cannot kids spell nemore ? What gives ?

Sincerely,

L33t0

Dear L33t0,

It seems every third blogpost on the net these days is lamenting the loss of grammar and spelling skill among the youth (as they put it), the comments fields to these posts invariably then come down to a near perfect 50/50 split between those arguing that such complaints are simply pedantry and a fear of freedom, a sort of longing for the days of the “Kings English” and pointing out that Shakespeare, the greatest English poet of all couldn’t even spell his own name the same more than once – versus those declaring that good spelling and grammar is just good manners and consideration for your readers, that anybody who ever uses txtspk will obviously never get a job, that our schools have no standards etc. etc.

Who is right ?

Well, as with just about every question on which debate rages, it keeps raging because people are trying to oversimplify it. This isn’t a right or wrong question with two simple sides. It’s a complex issue with multiple sides and historical influences. Firstly, we need to understand where each side is coming from.

When I went to school we were taught that written and spoken language are very different, that we don’t write as we pronounce, that we don’t construct sentences the same way when writing. This came about for two big reasons – firstly, until not long ago virtually all writing was the recording of information such as news, books and important letters. This meant that writing was, by it’s nature, a very formal thing in almost all cases. Secondly – only a small handful of the population was literate anyway, so writing was always the preserve of a tiny elite (this didn’t start changing until the 18th century really). So when only a small and highly educated group used  the medium, it is not surprising that it was held to a very high academic standard.

As reading and writing became more commonplace, this didn’t really change the standard though – because writing was still special, we wrote school projects, curiculum vitae’s and letters to our banks. We wrote business letters, and just occasionally a letter to a penpal who would only read an respond many weeks later. It was a rare thing, done with care and attention.

But nobody spoke as we wrote, no-one in the entire history of language ever has, and if anybody tried- nobody would actually understand them – or want to. Language, both spoken and written has always been an evolving thing, because of the formal nature of writing however it evolved far slower and in fact artificial systems were  created to deliberate retard it’s evolution – there was a good reason to do so, so written works would remain readable for a long time – hence concepts like “The King’s English” was invented. Since the only writing ever done was at least somewhat formal and important, and since this writing was something the average person only rarely did – it worked.

But then came the communications revolution and the internet. The first generation of internet users were highly educated because the early years of the internet was primarily an academic medium. More-over, the only major interface to it was computers with keyboards, on which  nearly all the users were highly proficient (since most of them worked with keyboards all day long) – hence we didn’t see the change really start back then. Leetspeak developed but it was more a kind of subculture thing than a true trend.

It was the cellphone revolution that really changed things. Suddenly we had a generation who mostly used writing, not in any formal setting  but for conversation. For them, writing was not something special and rare done with important reasons, sometimes they would write something important – but very nearly all the writing they do is conversational – a means of just chit-chatting, as transient as a greeting on the street.

To make matters worse, the major interface in use for this had a length limit of 140 characters, and no keyboard, just a very annoying keypad on which even the best typists are still really slow. They adapted, this highly informal conversational writing, took on the phraseology and grammar of spoken conversations, and it’s spelling became a form of highly phonetic shorthand.

As such, that is not a bad thing, it’s what written English would have been five centuries ago if those in power had not deliberately taken measures to control and retard the evolution of written language. Now without getting into the anarchist-language vs. controlled language debate, the reality is that one can slow the evolution of a language but it cannot be stopped. If written language deviates too far from spoken, it becomes useless so it has to follow, albeit at a slower rate and this has always been true.

The problem we face now is that this conversational style of writing is the only writing practice most youngsters get. I stand by my belief that there is nothing wrong with it, where appropriate. Using txtspk when writing an SMS is just clever, it’s natural and appropriate to the medium and the purpose of the writing. Using it to write a curiculum vitae is not – since the person reading will most likely not be from the SMS generation and will judge it a sign of low intelligence or education (regardless of whether there is any truth to this). This is gradually changing, we see professors at major universities like Oxford calling for the removal of spelling marks in tests because they applaud the liberation and true democratization of linguistics that is happening here, but for now this is still the world we live in.

In 20 years or so, when every personnel manager was a member of the SMS generation, sending your CV in what is now proper written English will be sure to have you marked as “out of touch, and too old for the job” – it will be as bad for your career as it is to send it in txtspk now ! But until that day (rue it or delight in it – but nobody can possibly prevent it) enlightened self-interest declares that txtspk English should be used only where appropriate. It is appropriate only in conversational writing – the kind created by cellphones and the net, where we are talking to our friends – like we would in a pub over a beer, and the fact that we are using a written medium is completely inconsequential and in fact if anything a hindrance. It is appropriate then to reduce that hindrance as far as possible so that the natural rapid flow of the conversation can largely survive.

It is quite acceptable, and if you aren’t a very good typist, in fact more polite, to use txtspk when on a cellphone keyboard or having a chat on IM, or even when tweeting.

It is not appropriate (at least not yet) to use txtspk when writing formal or important stuff. You shouldn’t use it to write your school assignments, you shouldn’t use it when writing a blogpost that you mean to be a serious and formal statement on a topic (even if that topic is a very casual and informal one) and you certainly shouldn’t use it for business or academic correspondence.

So that is my take on it, txtspk is just a natural human response to the idiosyncratic nature of formal written language when you try to use it to have an informal friendly discussion. When suddenly those Latinisms and archaisms of spelling that have given English one of the highest rates of dyslexia in the world become so cumbersome as to prevent meaningful conversation, rather than aid it as it does in a formal setting, but we are some ways from it being a natural and normal form of writing for most people – from in fact, it being possible to write a novel in txtspk that anybody over the age of 20 will actually be able to read (yep, I’m ten years too early myself…) – but since the youth virtually without exception has embraced it, it’s inevitable that this will change.

So Doctor Grammar’s advice, if you were writing something formal and somebody gets pedantic over the spelling of a word you got wrong, apologize and correct it. If you were having a conversational chat with a friend and the same thing happens, tell him to: g0 f4 urslf.

UPDATE: It occurred to me later that there is in fact one crucial thing our schools should be doing differently. I read articles about teachers complaining that children have lost the ability to write cursively because “all they do is type” – but none of them know how to type well. Losing the skill of handwriting is neither surprising nor a bad thing, a pen is an archaic technology now and before long it will be like that kid who was using a walkman for a week – they would just spend the entire time wondering “how on earth did people cope with this ?”. I will go so far as to say that if my grandchildren know what a pen looks like -  I will be a very sad man indeed. We live in a world of typing now – but our schools are not teaching this essential skill. We used to have typing classes for girls, as part of our sexist past. Where we’d teach them to type fast and efficiently on typewriters while schooling the boys in woodworking. As the computer revolution made typists obsolete – we started teaching computer literacy, and typing classes became ancient history (this was starting even when I was in school).

Now we have a generation growing up doing 90% of their written communication by typing – and never having learned to do it well. When you are expected to hand your CV in as a typed document rather than a written one, it’s a major problem if you type with one finger. Schools need to expand computer literacy classes with good old fashioned 60-words per minute on a qwerty typing classes – now that is preparing kids with an essential skill.

Sep 062009
 
No Gravatar

So your best friends and your ex-girlfriend with whom you’re still friends somehow all end up unexpectedly at your house on a hot Saturday afternoon ? What to do, what to do. Well obviously, break out the liquor and take lots of pictures. Of course, it was the worst time of the day lighting wise, so most of what I took was trashed, but there were a couple of good ones, having now progressed quite a bit on the touch-up skills thing, I could also make some nicely artistic photos out of shots that really didn’t lend themselves to it easilly (like background blurs to highlight a person in a cluttered location).

Enjoy the results, I think their the best I’ve done yet.

[nggallery id=5]

Sep 012009
 
No Gravatar

So, with the Kruger Park pictures uploaded, I can now proceed with part four, the first item on touch-ups, focusing on RAW work. At this stage, it’s the only part I’m willing to claim any knowledge off, mostly because it’s about 95% of what I have been doing, since my first photoset were nature pictures, and I had no reason to want to make them into logos or edit them to remove spots or anything, what I wanted to achieve was to make sure my pictures represented the reality of the scene as close as possible – for this RAW work is almost everything you need.

There are three essential skills when it comes to raw work, with a large number of sub-levels which require a deep understanding, I won’t be going into those – plenty of good books cover them in detail and there is nothing GNU/Linux specific about them. What I do want to share is a basic working method I used with, I believe, considerable success for processing RAW images on GNU/Linux. I used the UFRaw plugin because I really like getting the RAW editor before the normal image editor so this document is based on that approach.

For this howto, I deliberately worked with a picture I really wanted to save as it was the only one of it’s kind I had – and hadn’t been taken well. I wanted to make out of it, the best picture I could.

Let us open a picture – from digikam, I right-click on it and say “Open with GIMP”

This picture was taken in dusky conditions with mere moments to catch the shot. The tiny bit of camera-shake I picked up I can’t do anything about and there was no time to adjust camera settings – so the picture is dark, but that much at least we can fix.

The first thing to do is change the white balance. You can do this manually by adjusting the temperature slider (the red/blue intensity levels of the pixels), and the green slider. If you know you had a good white balance when taking the picture, keep it on the “Camera WB” or if you want to use the white balance the camera had suggested set it to “Auto WB”. There is also a number of presets, which you should recognize as the same presets generally included on camera’s.

In this case, I opted for a preset, “Shaded” as it suited the shot well, and after some experimentation  I found it to give by far the best result – it brought out the colors of the original shot without distorting them. I also upped the exposure slider a little bit. I almost always avoid the auto-exposure feature because frankly – I think it’s not very good, I suspect it’s better when mapped with the point-white-balance feature as you can choose which part of the image it should base it’s exposure calculations on, but I haven’t experimented much with this.

Essentially, exposure control let’s you lighten or darken an image, since you can’t change how much light was captured by the censor, this is akin to how a film photographer could make up for it a bit by leaving the photo exposed in the darkroom for longer or shorter periods of time. There are some catches though, when exposing down – there is a lot of guesswork the program has to make, since it can’t “de-light” the image, it has to guess how to shade it darker (but it’s surprisingly good at this). Exposing up is digitally a much easier process (I read this on the UFRaw website, and I won’t argue with the guy who wrote the code about what was easier) but it has it’s own catch. On photo-paper, long exposures would cause the image to become grittier (much like shooting with higher ISO values) – in your digital lab, it introduces digital-noise.

Now digital noise may or may not be a problem for you – the amount of digital noise you get for the amount of exposure is the big thing. At lower-sized views, the noise may not be visible to the naked eye at all. This is then fine if you keep the picture for web-user or post-card sized printing. A picture that you had to up the exposure by any significant degree won’t make a good A3 print, but it may yet be a nice and useful picture and could save one that was otherwise lost. In this case, I only upped it a little as the picture really wasn’t under-exposed, it was just dark.

Here is the result of my tweaks:

The next thing that you can do inside UFRaw that I use a lot is cropping, of course you can do this with gimp as well, and I often use that one, but I rather like the way UFRaw does it and I like being able to crop while doing light work as I find it is sometimes helpful to be able to ignore the light on the areas you don’t intend to keep anyway.

In this case, I don’t want to crop a lot, but like most nature pics I got quite a bit of superfluous background that doesn’t add either meaning or context to the picture and simply reduces the real-estate for the subject, I do want to at least trim that down a bit:

With all this done, we click the okay button, and the image gets passed on to Gimp, where we can do more RAW work using gimp’s extensive set of tools, including crops if we want to etc. and when done, easily and with good control, export it to a more permanent storage format like lzw-compressed tiff or dng or whatever you prefer.

UPDATE: I discovered a small but very annoying bug with using the UFRaw plugin, when using it in plugin mode, it sends the file to GIMP as clipboard data, when you then save it (regardless of what format, but lets assume you are using LZW-tiff as your post-raw archive format) – you lose the EXIF data (since the clipboard doesn’t contain it. So I suggest using UFraw standalone, edit the raw file, and then use UFRaw to save it as TIFF with the EXIF data intact, and open the TIFF file with Gimp for your touch-up work.