PSPP-BUG: [bug #21062] Add en_US, en_GB translations

[Ben Pfaff]

Follow-up Comment #4, bug #21062 (project pspp):

>In deference to pspp's origins, I've decided to use American 
>spelling in the sources, and added a en_GB localisation. 

My thought was that, as in the Linux kernel, each developer would simply
spell words as he preferred, and then people with different preferences could
use locali[sz]ation to adjust to taste.  But I can't complain about this
resolution either, as long as you are also satisfied with it.

>Those (like myself) who use neither en_GB nor en_US by default 
>will probably wish to use a command similar to export 
>LANGUAGE="en_AU:en_GB:en" 

Hmm.  I didn't reali[sz]e that there were Australia-specific forms of
technical language, but of course it makes sense that there would be.  If it's
not too much trouble, would you mind giving an example of a difference, simply
for my personal enlightenment?

>Btw, I want to do a major shake up about the way we handle i18n,
>but this can wait until after the release.

OK.  I think that the acceptance of ctype_l and friends into relevant
standards should make this easier than it would have been say a year ago.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?21062>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/