public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: "João Pinto" <jo.pinto08@gmail.com>, bug-glibc-locales@gnu.org
Subject: Re: Bug in the i18n pt_BR file
Date: Wed, 29 Jan 2020 16:06:00 -0000	[thread overview]
Message-ID: <871rri8cy9.fsf@linux.ibm.com> (raw)
In-Reply-To: <CABAQ600+15hfvvDX1bqcX8X8j8v4ksFAUMjksq4ZNogq2YWJXA@mail.gmail.com>

Hi João,

João Pinto <jo.pinto08@gmail.com> writes:

> Hi, I'm João Pinto from Brazil and I'd like to report a bug in the
> i18n pt_BR locale file. The capitalizations on the months and the week
> days were wrong, so I fixed them in the file that I'm sending annexed
> to this email. If you guys were so nice to replace the current file
> with my corrections I'd be very grateful.

Would you have a reference on why they have to be capitalized?

> LC_TIME
> abday   "Dom";"Seg";/
>     "Ter";"Qua";/
>     "Qui";"Sex";/
>     "S<U00E1>b"
> day     "Domingo";/
>     "Segunda";/
>     "Ter<U00E7>a";/
>     "Quarta";/
>     "Quinta";/
>     "Sexta";/
>     "S<U00E1>bado"

I could not find a reference for week days.

> abmon   "Jan";"Fev";/
>     "Mar";"Abr";/
>     "Mai";"Jun";/
>     "Jul";"Ago";/
>     "Set";"Out";/
>     "Nov";"Dez"
> mon     "Janeiro";/
>     "Fevereiro";/
>     "Mar<U00E7>o";/
>     "Abril";/
>     "Maio";/
>     "Junho";/
>     "Julho";/
>     "Agosto";/
>     "Setembro";/
>     "Outubro";/
>     "Novembro";/
>     "Dezembro"

ABNT in its standard NBR 6023:2002 indicates that months should be always used
in lower case, regardless if they're abbreviated or not.
See Annex A (Abreviatura dos meses).

-- 
Tulio Magno

  reply	other threads:[~2020-01-29 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29  7:01 João Pinto
2020-01-29 16:06 ` Tulio Magno Quites Machado Filho [this message]
2020-01-29 17:04   ` Caleb Herbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rri8cy9.fsf@linux.ibm.com \
    --to=tuliom@ascii.art.br \
    --cc=bug-glibc-locales@gnu.org \
    --cc=jo.pinto08@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).