On Sun, 6 Jan 2008, Bryce Harrington wrote:
Hi all,
We're still not yet to string freeze, but took a big step forward towards that today.
Also, for en_CA, it looks like it hasn't been filled in very much,
the stats might be misleading, hard for these kinds of scripts to know if things have deliberately been left blank to allow the defaults to show throuhg.
and what is there seems to just be Britishisms (centre, metre, etc.)
from having seen the Gnome localisations very often en_CA and en_GB are 99% the same but a few words like those ending with -ize and a few others seem to be preferred for en_CA compared to en_GB
we simply copy the en_GB file to en_CA?
I'd guess it would be better than an unmaintained file if the old maintainer cannot be contacted. the inactivity might simple be because not much needs to be done.
(ideally it would be easier if users could get en_US as the C locale or when they specifically choose en_US and that the generic 'en' spellings followed British spelling rather than needing en_GB en_IE and various others (or at least having that extra layer of inheritance so en_CA would only need to include the smaller differences from en_GB). that is unfortunately a bigger infrastructure problem and little to do with Inkscape. (Sucks that using en_IE leaves me with American spellings.))
Gnome have some scripts for automating the en_US to en_GB conversion but proofreading is very much advised. Similar scripts may exist for en_CA. http://live.gnome.org/BritishEnglish
always helps though to see if the Americanisms are all entirely necessary. Words like Bookmarks and Recycle Bin are great in that they work both ways and require no further localisation. some spelling differences are unavoidable of course but translators - kind patient people that they must be to wade through technical jargon and attempt to make it comprehensible - from time to time make changes to grammar or rephrase for better clarity and do so quietly rather than fighting to push these upstream.