bugPSPP - Bugs: bug #21062, Add en_US, en_GB translations

 
 

bug #21062: Add en_US, en_GB translations

Submitter:  Ben Pfaff <blp>
Submitted:  Thu 13 Sep 2007 05:36:40 AM UTC
   
 
Category:  Internationalization/Localization Severity:  5 - Average
Status:  None Assigned to:  None
Open/Closed:  Closed Release:  Post-0.6.0
Effort:  0.00
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 15 Sep 2007 04:51:43 AM UTC, comment #4: 


>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.

Ben Pfaff <blp>
Group administrator
Sat 15 Sep 2007 02:54:22 AM UTC, comment #3: 

OK. Done.

Traditionally at this point, we should have started a flame war about which language variant gets to be the default.  However, in deference to pspp's origins, I've decided to use American spelling in the sources, and added a en_GB localisation.  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"

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

John Darrington <jmd>
Group administrator
Thu 13 Sep 2007 01:47:21 PM UTC, comment #2: 


>Which messages were you thinking of in particular?


The one that stood out to me in particular was the title of bug #20830: "analyse" versus "analyze".

I've run into a few others ("center" versus "centre" sticks in my mind), but I don't recall whether they were user-visible or just in variable names etc.  If the latter then of course they should just stay as they are.

>The only other discrepancy was one occurrence of "minimise"
>whereas other words end in -ize --- both suffices are acceptable
>in British English, depending on whether one's allegences lie
>towards Oxford or Cambridge ...


I didn't realize (heh) that both were acceptable.  Thanks for the tip.

Ben Pfaff <blp>
Group administrator
Thu 13 Sep 2007 01:08:01 PM UTC, comment #1: 


> Currently spelling in PSPP messages, etc. is a mix of American and British.


I had a quick look through po/pspp.pot and the only spelling which I thought might cause tension was the word "license", but since this is part of a proper noun, I'd be hesitant to translate it.  The only other discrepancy was one occurrence of "minimise" whereas  other words end in -ize --- both suffices are acceptable in British English, depending on whether one's allegences lie towards Oxford or Cambridge ...

We used to have a en_GB, but since we removed all the messages with the word "color/colour" there was no use for it.

Which messages were you thinking of in particular?

John Darrington <jmd>
Group administrator
Thu 13 Sep 2007 05:36:40 AM UTC, original submission:  

Currently spelling in PSPP messages, etc. is a mix of American and British.  This is fine--it makes sense for each author to use what spelling he or she is accustomed to--but it would be nice to add translations so that each user can see what he or she is accustomed to, too.

Ben Pfaff <blp>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jmd (Posted a comment)
  • -email is unavailable- added by blp (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-09-15 jmd Open/ClosedOpen Closed
    2007-09-13 blp ReleaseNone Post-0.6.0

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code