Newest Entries are on the Recent Entries page.

Monday, 28th July 2008

Translated the American english language strings to British English.  632 strings!  Was mostly cut-n-paste like though, just fixing some obvious differences.

This should allow for the testing/verification of the gettext localisation code soon, before I mark this i18n task off as complete.
 

Sunday, 27th July 2008

Updated the salasaga_screencapture module for gettext, then americanized (!) the british spelling in salasaga_ide.  This should allow me to create en_GB and en_AU localisations for Salasaga to test if everything is working properly.
 

Saturday, 26th July 2008

Finished the initial conversion of all the functions in the salasaga_ide module for gettext, including the big and hairy functions. :)
 

Friday, 25th July 2008

Nearly finished converting all of the functions in the salasaga_ide module for gettext.  Have avoided the really big and hairy looking functions so far though. ;->
 

Thursday, 24th July 2008

Not a lot done.  Converted a few more functions for gettext.
 

Wednesday, 23rd July 2008

Today was taken up rebuilding my MSYS virtual machine (VMware Workstation) over and over, in order to test some changes to Ming's cvs.  Finally got it done, and Ming is confirmed to work on MSYS now, but it took about 16 hours straight. :-/
 

Tuesday, 22nd July 2008

Putting the bits in place for internationalisation of the salasaga_ide module.  Strings seem to be getting extracted fine from the source files converted so far, and locale messages files are getting installed properly as well.

Probably time to try uploading a .pot file to Launchpad, so get a feel for how that system works.
 

Monday, 21st July 2008

Updated the screen capture module ("salasaga_screencapture") to use automake.  With that completed, now things should be in place for getting internationalisation (i18n) happening.
 

Sunday, 20th July 2008

Took most of today updating the main IDE module ("salasaga_ide") to use automake.  This is so it's possible to use gettext() properly, which needs to know where the languages modules are installed at run time.

It also simplified some of the run time code that previously had been guessing where various images, fonts, and sounds were installed.
 

Monday, 14th July 2008

Have been creating "Blueprints" on Launchpad for each of the items on the ToDo list.  This is to make things easier to track, and allow other people to comment on and make suggestions on.

  https://blueprints.launchpad.net/salasaga 
 

Tuesday, 8th July 2008

Started adding the various bugs and feature requests that people have made, to the SourceForge.net bug tracking system for Salasaga.  Seemed like a good place for them at this point, so they don't get lost.

However, Iulian Udrea (Ubuntu) has made a better suggestion, that of using Canonical's "Launchpad".  It includes bug tracking, feature request tracking (blueprints), and has integrated tools for managing translations.

Sounds like a winner.  Salasaga is now registered on Launchpad, and the bugs and ToDo list items will be added there reasonably soon.  It should also be of great assistance with the translation effort too.
 

Monday, 7th July 2008

A few people have volunteered to translate Salasaga to their own language(s) recently, so I've started to look into what is needed to make this happen.

GNU's "gettext" (po files) seems to be the standard approach, so I'm trying out gettext locally on my development system, to see if things will be as simple as they could be.  (fingers crossed!)