[ Content | Sidebar ]

Archives for 2008

New xcowsay at last!

August 30th, 2008

I’ve finally finished xcowsay 1.1! The big new feature is dream mode — you can display images inside the bubble!

There’s also a new --think flag to make text appear inside a thought bubble as well. Plus there’s some bug fixes and even a Portuguese translation. What are you waiting for?! Get it here.

Also, I’ve changed the theme on the site! Minimalist, eh?

New Lunar Lander version

July 19th, 2008

I’ve released version 0.4 of Lunar Lander! New features in this version:

  • Sound effects!
  • Much improved performance when no hardware acceleration is available
  • Prettier effects
  • Bug fixes
  • Windows binaries for the first time in ages

Get it here.

Underwater nuclear reactor

June 23rd, 2008

Underwater nuclear reactors are an amazing idea aren’t they? Turns out someone’s already patented a design. And there are even plans to build one in Estonia!

So last night I designed my own underwater nuclear reactor, complete with multi-colour submarines and colourful aquatic beasties!

I’m rather proud of it.

I think this is also a subject ripe for Thunderbirds fan fiction… 😛

Ruby Toys

June 18th, 2008

UPDATE 6/4/15: this post was previously a page but was removed when I reorganised the sidebar. Check out the rbib project on GitHub.

This page contains a couple of small Ruby utilities I’ve written.

BibTeX parser

A parser for BibTeX databases. Mostly intended for transforming the entries in some way, such as deleting unneeded keys. But it also works as a general purpose BibTeX interface.

Example: remove all the url fields from a database:

BibTeX::Parser.parse('input.bib').map do |entry|
  entry.reject_fields [:url]
end.save('stripped.bib')

Source code: git clone https://nickg@github.com/nickg/rbib.git

Released under the GPLv3.

Future:

  • Documentation
  • Gem installer

Lunar Lander update

June 13th, 2008

I’ve posted an updated version of my Lunar Lander game. This is mostly a code clean-up of the last release, but it also features a new options screen and the ability to switch resolutions.

Download it here.

Ideas for next xcowsay version

June 13th, 2008

These are some of things I’m thinking of adding for xcowsay 1.1:

  • Think mode: draw a thought bubble like cowthink in the original cowsay.
  • Dream mode: display images in the bubble.
  • Draw the bubble with Cairo and anti-aliasing.
  • Translations.
  • A few bug fixes ;-).

Thanks to everyone who downloaded xcowsay 1.0!!!!! 😀

Beta version of xcowsay panel applet

June 8th, 2008

I’ve written a GNOME panel applet based on the xcowsay source code. It doesn’t do much at the moment – click it to run xcowfortune.

If you want to try it out, get the source code here.

You’ll need to configure it with --prefix=/usr or set BONOBO_ACTIVATION_PATH for GNOME to find it.

Lunar Lander game

June 2nd, 2008

I’ve posted the source code of my Lunar Lander clone that I’ve be working on for a while now.

Check it out here!

xcowsay 1.0 released!

May 23rd, 2008

Woo! xcowsay is now finished! Download it here.

Please add comments, bug reports, suggestions, whatever.

UPDATE: Now on freshmeat!

A gettext i18n tutorial

May 23rd, 2008

I’ve recently struggled with GNU gettext for internationalizing some of my programs. This, for the benefit of other people who, like me, can’t be bovered to read the documentation, is the method I’ve used successfully:

I’m assuming you have a standard GNU autoconf/automake setup. If you don’t, there’s a lot of manual work to do. I’ve no idea how to do that: better read the manual instead.

There’s a handy tool gettextize which handles a lot of the monkey work for you. Run it in the top-level project directory:

$ gettextize

This will create a bunch of files (in the m4 and po directories), make a few changes to your configure.ac and Makefile.am (backups are created with a ~ suffix) and also print some instructions. Let’s follow them.

The first thing to do is add AM_GNU_GETTEXT([external]) to configure.ac in order to cause autoconfiguration
to look for an external libintl (apparently).

Next rename po/Makevars.template to po/Makevars and open it up. You’ll probably want to change the COPYRIGHT_HOLDER and MSGID_BUGS_ADDRESS to something relevant. I usually add --keyword=i18n to XGETTEXT_OPTIONS because I think the default _ looks pretty ugly.

Now you need to add every file that contains translatable strings to po/POTFILES.in. You can’t use wildcards or directory names — yuk! Something like this should do the trick:

$ find src -name '*.[ch]pp' > po/POTFILES.in

Now it’s time to regenerate the configure script with the gettext macros:

$ aclocal -I m4
$ autoconf

If you try to run configure now, it will complain about a missing config.sub. Luckily automake can add this for us:

$ automake --add-missing
configure.ac:10: installing `./config.guess'
configure.ac:10: installing `./config.sub'

Now run configure in your build directory. You should see some additional NLS messages.

Next we mark some strings as translatable. Make sure you include libintl.h in every source file with translatable strings. Surround the translatable strings with whatever you passed as a keyword in po/Makevars (_ is default, but I prefer i18n). These macros aren’t defined by default, and they need to be aliases to gettext. I usually make a header file i18n.h like this:

#ifndef INC_18N_H
#define INC_18N_H
 
#include <locale.h>
#include <libintl.h>
 
// Macros which xgettext extracts translatable strings from
#define i18n(s) gettext(s)
 
#endif

Now add i18ns around your translatable strings like this:

puts(i18n("Hello world"));

Before any call to gettext you need to execute the following setup code or it won’t work (assuming you’ve included config.h):

setlocale(LC_ALL, "");
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);

LOCALEDIR is passed to the compiler from my Makefile.am where I have something like:

localedir = $(datadir)/locale
DEFS = -DLOCALEDIR=\"$(localedir)\" @DEFS@

Now we need to (re-)generate the master package.pot file which contains all the translatable strings (where `package’ is the name of your package). We can do this with make dist in the build directory, but the following command will update the .pot and nothing else:

$ make -C po package.pot-update

Again, substitute `package’ for whatever your package name is. Notice that even if you run this in the build tree it will update the file in the source tree (ewww!!).

Finally, we can actually translate something. In the po directory of the source tree run:

$ msginit -l de_DE -i package.pot

Replace de_DE with whatever locale you wish to translate into. It’ll ask you for your email address and create a new de_DE.po file. Open it up and you’ll see a bunch of lines with msgid and msgstr pairs. The msgid is the English (or whatever language you’re translating from) and the msgstr line is the language you’re translating into. So for our example, we change it to:

msgid "Hello world"
msgstr "Hallo Welt"

It’s .gmo files rather than .po files that get distributed and installed. So how do we generate them? This is the bit that really confused me, and the documentation was not helpful. In the end I looked in the makefile source to see how it works. You need to create a file po/LINGUAS listing the available locales, one per line. Like this:

# List of available locales
de_DE
en_GB

There might be an easier way to do this, however. Now run configure to regenerate your makefiles and run:

$ make dist

The .gmo files for each locale should be generated in the po directory of the source tree.

Now if we install the package with make install the translations should be copied to $PREFIX/share/locale (or whatever your LOCALEDIR was). To test it out you can run your program with a non-default LANG environment variable — it should automagically select the correct set of strings, if a translation exists.

For example, to test our German translation we would set LANG to de_DE.UTF-8. You might have problems if your C library is not set up to support this locale (dpkg-reconfigure locales on Debian).

Finally, whenever you make a change to the translatable strings in your program, run the following to update the .pot file:

$ make -C po package.pot-update

Now in the po directory of the source tree, merge the changes into each translation with the following command:

$ msgmerge -U en_GB.po package.pot