Created attachment 562 [details]
Patched English strings for DrakX installer

Created attachment 563 [details]
Patched English strings for Live installer

If you want to help with this type of work, please join the English translation team by following the steps here: 
http://mageia.org/wiki/doku.php?id=translators:tx_short_guide

CC: (none) => margot

Ehh I thought you couldn't edit the English strings through there

Comment on attachment 563 [details]
Patched English strings for Live installer

-msgid "Do you want to save /etc/fstab modifications"
+msgid "Do you wish to save the changes to your fstab modifications"

The original makes sense the changed version does not.

And we shouldn't edit the .pot. However, i understand that it is easier to say in .pot what is wrong, so once the proofreading team will tell that the change are ok, I will try to commit them in the perl source code ( and then see how we manage the .pot change )

CC: (none) => misc

Created attachment 570 [details]
Revised draklive pot

Attachment 562 is obsolete: 0 => 1

Created attachment 571 [details]
Revised Drakx patch

Attachment 563 is obsolete: 0 => 1

I think we should first decide upon which variant of English we use in pot files. At the moment we have a mixture of AE and BE, which was only made worse by some i18n folks proposing "corrections" to absolutely correct AE strings.

I think, since the US have the larger population and AE is quite common in the IT world, I would like to have AE as default with the possibility to "translate" it into BE using transifex and an i18n-en_GB team (that already exists) for the convenience of the British and all other people that prefer colour written with a "u" ;-)

CC: (none) => oliver.bgr

As a native speaker of en_GB, en_AU and en_NZ with well over 60 years of experience, I see very little point in 'standardising' on either _US or _GB.

For the past I don't know how many years the computer industry has not had a defined en_ 'standard' language.

In most cases, simply because the majority of applications from the commercial world have been written in the US, that 'standard' has been en_US.

I feel confident that the vast majority of EN-speaking users couldn't care less about which flavor of EN colours their favourite programme.

I note with interest that bugzilla uses an en_US dictionary, so let's leave the default flavour of English as en_US.

CC: (none) => john

(In reply to comment #10)

> I note with interest that bugzilla uses an en_US dictionary, 

That depends on the dictionary that your browser's spell-checker is using

> so let's leave the default flavour of English as en_US.

I agree. The default language in KDE, Gnome and most (perhaps all) GUI applications is en_US. There may be a case for having en_GB "translations" for the drakxtools as are provided for many GUI applications, but I don't regard that as essential.

(In reply to comment #11)
> I agree. The default language in KDE, Gnome and most (perhaps all) GUI
> applications is en_US. There may be a case for having en_GB "translations" for
> the drakxtools as are provided for many GUI applications, but I don't regard
> that as essential.

I second that. Besides, we don't ask "what colour would you like your desktop to be?"

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

*** Bug 6069 has been marked as a duplicate of this bug. ***

CC: (none) => gtarn

The English tought in schools (non native speakers) was/is (mostly) British English as standard, at least I was told years ago.

CC: (none) => pavelfric

list that someone send me:

center --> centre

initialize --> initialise

favorites --> favourites

colors --> colours

Version: 2 => Cauldron
Assignee: thierry.vignaud => bugsquad
Keywords: PATCH => (none)

(In reply to comment #16)
> list that someone send me:
> 
> center --> centre
> 
> initialize --> initialise
> 
> favorites --> favourites
> 
> colors --> colours

All software that Mageia is based on (KDE, GNOME, Xfce, LibreOfffice, etc.) uses American English. KDE English Breakfast Network ( http://www.englishbreakfastnetwork.org/ ) even warns the developers when British words are used.

Please do not break the compatibility with upstream with such changes.

CC: (none) => yurchor

The time for such changes is when there is a potential confusion.  No British-English speaker would themselves spell things in the US way, but equally no British-English speaker would be confused by reading US-English.  I agree with Yurchor.  Consistency is much more important.

CC: (none) => annew

yes sorry I had confused with another issue /o\

Even if en_US is the default language when writing code and strings, this does not prevent us from having en_GB "translations" in our tools.

CC: (none) => mageia

I'm pretty sure someone already made a sed script to change localisation from en_US to en_GB, though I don't know where to search for it.

Basically, I think we could get a correct en_GB locale using scripts such as:
s/localization/localisation/
s/color/colour/
s/center/centre/
and so on...

BTW, I think we tend to inconsistently use en_US and en_GB spellings, since most of the time our tools are written by non native English speakers. We could then also use a script to correct en_US localisation with the same script as above in reverse. We could then run en -> en_US on the default strings, and en -> en_GB for the en_GB locale.

CC: (none) => remi

Well... this escalated in the wrong direction. I was not trying to complain about en_US vs. en_GB (I live in Canada, by the way), but I was only trying to get rid of the poorly-written English from the installer cause, well, it needed it badly.

So, what to do with this bug report? There's been a lot of talking but I don't know what the next step should be now, I'm confused :)

Keywords: Junior_job => (none)
CC: (none) => stormi

also, setting version to cauldron since mga3 installer is frozen.

Version: 3 => Cauldron

what about this bureport ?

CC: (none) => nicolas.lecureuil

It still needs to be done; I can tell that the first language of the upstream developers wasn't English (isn't Mandriva a French company), so cleaning up that part would be very useful to help polish our image.

we are from france and brasil. And eugeni was from brasil.

Not sure if this is the correct assignment, but I think it would look better on us all if we can incorporate (some of) these changes in Mageia instead of letting it sit in our bugzilla for 5 more years.

Assignee: bugsquad => doc-bugs

(In reply to Remco Rijnders from comment #28)
> Not sure if this is the correct assignment, but I think it would look better
> on us all if we can incorporate (some of) these changes in Mageia instead of
> letting it sit in our bugzilla for 5 more years.

Documentation team is for our official documentation in http://doc.mageia.org and for monitoring the wiki.

However, I'll share my thoughts:

Correcting the English in our tools isn't easy
https://wiki.mageia.org/en/Fixing_strings_in_code_without_breaking_translations

Those who can do that, have a TODO list with many much more urgent things

*Moreover*, we need to be sure that there is agreement (between native English speakers and people with a very good understanding of the tools) on which strings should be changed into what!

In short: I don't think this is going to happen any time soon.

However, AFAIK there is room for, e.g., "en_GB" and "en_US" translations.

I think making such translations is the only way to solve this fast.

re-assigning to i18n/l10n
(feel free to assign back to bugsquad if you don't think solving this via en_* translations will work)

CC: (none) => marja11
Assignee: doc-bugs => i18n-bugs

ping...
Bug is 6 years old.
What is the status?

CC: (none) => fri

(In reply to Morgan Leijström from comment #30)
> ping...
> Bug is 6 years old.
> What is the status?

Just need someone to decide that we will go for it... Or will not go for it. It is not hard to implement this.

As Marja said, the easier is to have translation catalogs for en_US, en_GB and even other countries or regions.
Then, developers will be free to pick these "translation" to incorporate them in the source.

CC: (none) => yves.brungard_mageia