From: "digitalfreak at lingonborough dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/24296] Orthographic mistakes in 'day' and 'abday' sections in tt_RU (Tatar) locale
Date: Wed, 20 Mar 2019 21:19:00 -0000 [thread overview]
Message-ID: <bug-24296-716-j0xLk8hSW0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24296-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24296
Rafal Luzynski <digitalfreak at lingonborough dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.30
--- Comment #13 from Rafal Luzynski <digitalfreak at lingonborough dot com> ---
(In reply to mansur from comment #11)
> [...]
> Is this format of changelog message ok?
>
> I added a bug number and a locale name to the patch file.
Thank you, it was better. I've decided not to bother you anymore and corrected
the commit comment and the ChangeLog. You can see it in comment 12. Then I
pushed the patch to master. This bug is fixed now. Thank you for your
contribution.
> I took a look in tt_RU@iqtelif locale. As much as I know there are no
> officially accepted orthography for that alphabet, so trying to "fix"
> something there will be just guessing how it should be in my opinion. And I
> don't see any obvious mistakes there in day, abday, mon, abmon sections.
Good idea not to change it if you are not sure, if the sources do not exist,
and especially if you can't see any error.
> About the bug 21938. I don't know exactly what it depends on, but I suppose
> postal_fmt should be the same as in ru_RU locale because both these locales
> are mostly used in the same country. Am I right?
Most probably yes, unless there are some words included which need translation.
I did not analyze that bug carefully.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2019-03-20 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 10:37 [Bug localedata/24296] New: " 6688000 at gmail dot com
2019-03-03 10:38 ` [Bug localedata/24296] " 6688000 at gmail dot com
2019-03-15 9:39 ` digitalfreak at lingonborough dot com
2019-03-15 17:24 ` 6688000 at gmail dot com
2019-03-15 20:36 ` digitalfreak at lingonborough dot com
2019-03-15 21:28 ` 6688000 at gmail dot com
2019-03-15 22:11 ` digitalfreak at lingonborough dot com
2019-03-16 8:24 ` 6688000 at gmail dot com
2019-03-16 19:11 ` digitalfreak at lingonborough dot com
2019-03-16 21:00 ` cjlhomeaddress at gmail dot com
2019-03-17 10:03 ` 6688000 at gmail dot com
2019-03-19 22:09 ` digitalfreak at lingonborough dot com
2019-03-20 8:32 ` 6688000 at gmail dot com
2019-03-20 21:05 ` cvs-commit at gcc dot gnu.org
2019-03-20 21:19 ` digitalfreak at lingonborough dot com [this message]
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=bug-24296-716-j0xLk8hSW0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.org \
/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).