bug#26302: Fwd: website translation English (US)?

[pelzflorian (Florian Pelz)]

I just noticed simon and I forgot to reply to the bug.
Here is our conversation on the English (US) display name.

----- Forwarded message from zimoun <zimon.toutoune@gmail.com> -----

Date: Mon, 27 Jul 2020 21:25:06 +0200
From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Subject: website translation English (US)?

Hi Florian,

Thank you for the work!  Really nice.

Aside, why is it "English (US)" and not simply "English".  Well, I am
not sure that the translation to "English (UK)" would be really
different.

Back to holidays (on September) I will try to do the French one if
roptat does not beat me. ;-)

All the best,
simon

----- End forwarded message -----

----- Forwarded message from zimoun <zimon.toutoune@gmail.com> -----

Date: Tue, 28 Jul 2020 00:40:43 +0200
From: zimoun <zimon.toutoune@gmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Subject: Re: website translation English (US)?

On Mon, 27 Jul 2020 at 22:49, "pelzflorian (Florian Pelz)" 
<pelzflorian@pelzflorian.de> wrote:

> The differences would be few and far between (some
> “have”s might become “have got”s, publicized becomes publicised) and
> there currently is no UK English translation.
>
> Hmm.  I am hesitant to remove the (US) from English (US).  I agree
> that if we do not have a separate English (UK) translation (Guix
> proper does not), then it would look better without the country code.
> However if we ever do get a separate UK/AU/… variant, then a rename to
> English (US) would break all older PO files.

Well, I have never checked but I do not know if the manual fully
respects US English.  I understand the PO files issue but currently the
trasnlationproject.org has en_GB and en_ZA registered, only.

>From my point of view, it looks weird to have French (FR), French (CA),
French (BE), etc..  And even it is not exactly the same French, as
French native, I can read and understand all kind of French (which is
not the case about listen) even if some sentence or vocabulary could
sound awkward.  Whatever!

I have not checked in the code (just pulled now :-)), but is it not
possible to add a comment in guix-website.pot about the variant and in
the same time having just “English” as msgid i.e. change to (G_
"English") in utils.scm.  Or something like that.

The English variant would be still possible and it would require an
update by all the translator – which appears to me fine.

WDYT?

All the best,
simon

ps:
Thank you again for all this tough work.

----- End forwarded message -----

----- Forwarded message from "pelzflorian (Florian Pelz)" 
<pelzflorian@pelzflorian.de> -----

Date: Tue, 28 Jul 2020 11:23:56 +0200
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: zimoun <zimon.toutoune@gmail.com>
Subject: Re: website translation English (US)?

Since the only reason I have for wanting to keep English (US) is a
minor, technical one, you are of course right, simon.  Better now
than later.

On Tue, Jul 28, 2020 at 12:40:43AM +0200, zimoun wrote:
> Well, I have never checked but I do not know if the manual fully
> respects US English.

I think it only contains U.S. English.

> I understand the PO files issue but currently the
> trasnlationproject.org has en_GB and en_ZA registered, only.

AFAIK most variants of English are similar to en_GB, so IIRC some
projects have an en.po for en_GB and an en_US.po for U.S. English.
This makes en.po the default for other Englishes, which is usually
enough.


> From my point of view, it looks weird to have French (FR), French (CA),
> French (BE), etc..  And even it is not exactly the same French, as
> French native, I can read and understand all kind of French (which is
> not the case about listen) even if some sentence or vocabulary could
> sound awkward.  Whatever!

Yes, I concur.

> I have not checked in the code (just pulled now :-)), but is it not
> possible to add a comment in guix-website.pot about the variant and in
> the same time having just “English” as msgid i.e. change to (G_
> "English") in utils.scm.  Or something like that.
> 
> The English variant would be still possible and it would require an
> update by all the translator – which appears to me fine.

In the attached patch I added a comment *maybe* not to change the
(G_ "English").  I do not know how many out-of-date translations will exist,

Regards,
Florian

----- End forwarded message -----

I will push the patch this evening.

Regards,
Florian

0001-website-Change-display-name-of-default-locale-from-E.patch
Description: Text document