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 <andre...@debian.org> --- Documentation/contributor/programming-work.itexi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/contributor/programming-work.itexi b/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 programs. -- 2.20.1 _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
