[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Doc: Refer to the languages' countries by their proper ISO c

From: James
Subject: Re: [PATCH] Doc: Refer to the languages' countries by their proper ISO codes
Date: Sun, 31 Mar 2019 10:26:38 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1


Thanks for the contribution.

I have pushed this typo on your behalf.

(@bug No tracker was created as I thought this very trivial to warrant a full patch countdown).


author    Andrej Shadura <address@hidden>
    Sun, 31 Mar 2019 10:18:12 +0100 (10:18 +0100)
committer    James Lowe <address@hidden>
    Sun, 31 Mar 2019 10:23:14 +0100 (10:23 +0100)
commit    c05184b3ffa1e4b665ed1dfd8d0b641dab5286df




On 19/03/2019 12:28, Andrej Shadura wrote:
British English in en_GB, while American English is en_US.
en_BR would be English as spoken in Brazil, whil en_AM is English
as spoken in Armenia.

See ISO 3166-1 for more details.

Signed-off-by: Andrej Shadura <address@hidden>
  Documentation/contributor/programming-work.itexi | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/contributor/programming-work.itexi 
index 1823a9c1c8..cb7640c6a6 100644
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -565,7 +565,7 @@ proper user
  messages.  To help translations, user messages must follow
  uniform conventions.  Follow these rules when coding for LilyPond.
  Hopefully, this can be replaced by general GNU guidelines in the
-future.  Even better would be to have an English (en_BR, en_AM)
+future.  Even better would be to have an English (en_GB, en_US)
  guide helping programmers writing consistent messages for all GNU

reply via email to

[Prev in Thread] Current Thread [Next in Thread]