After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 683655 - i18n enhancements
i18n enhancements
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-09-09 05:47 UTC by Chris Leonard
Modified: 2012-10-08 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch (4.12 KB, patch)
2012-10-08 13:21 UTC, Matt Kraai
accepted-commit_now Details | Review

Description Chris Leonard 2012-09-09 05:47:12 UTC
Please use en_US orthography

  ../src/client.c:341 ../src/terminal-options.c:994

Maximise the window
to
Maximize the window

+++++++++++++++++++++++++++++++

Please combine these two strings

../src/org.gnome.Terminal.Preferences.gschema.xml.in.h:1
Human-readable name of the profile

../src/org.gnome.Terminal.Preferences.gschema.xml.in.h:2
Human-readable name of the profile.
Comment 1 Matt Kraai 2012-10-08 13:21:39 UTC
Created attachment 226038 [details] [review]
Patch

This patch changes all occurrences of "maximise" to "maximize".

I didn't combine the two strings because all of the <_summary> strings do not end with a period and 25 of 26 <_description> strings do end with a period.
Comment 2 Chris Leonard 2012-10-08 13:28:24 UTC
Thanks for the en_US standardization.

On the string merge request, fair enough.  However, I must admit I find these
sorts of minute (and generally meaningless) distinctions to be just a little
silly, so I do not hesitate to ask devs to consider localizer effort before
multiplying strings for seemingly arbitrary reasons.  No harm in asking.
Comment 3 Christian Persch 2012-10-08 13:35:21 UTC
I'm _against_ en_US standardisation actually, and only allowing this because it's unfortunately an established principle in gnome.

This is for master only, so no string freezes broken.
Comment 4 Chris Leonard 2012-10-08 13:48:51 UTC
Christian, I'm sorry you feel that way, but standards are useful, otherwise we would need to maintain a separate en_US language project.  If it is any consolation, I came across this as I was in the process of completing the en_GB "translation".  

It may seem overly picky to point out non en-US standard strings, but I come from the Sugar Labs downstream and via several million OLPC XO laptops, these strings are landing in the hands of kids in the classroom, so grammatical and orthographic "correctness" is important.
Comment 5 Christian Persch 2012-10-08 13:50:41 UTC
I agree that standards are useful; I would have standardised on proper english, not en-us.

So all those kids are getting en-us instead of english? What a pity.
Comment 6 Chris Leonard 2012-10-08 14:08:05 UTC
Not at all, we have localization efforts in over 130 languages and recently completed Māori for New Zealand and Aymara (Aru) for Peru.

http://translate.sugarlabs.org/

Based on the size and location of the OLPC deployments, I would suspect the majority of the kids are using the Spanish strings.

Our friends in OLPC Australia use the en-GB PO files in their builds and therefore learn to spell the way the Queen intended.  That option is also available to any other deployments that wish to use it.  This is part of the reason I have completed so many en_GB PO files in Damned Lies that are currently pending commit.

http://l10n.gnome.org/languages/en_GB/all/ui/

"The United States and Great Britain are two countries separated by a common language." (and variants) attributed to G.B. Shaw

"We have really everything in common with America nowadays, except, of course, language."  Oscar Wilde, The Canterville Ghost (1887)