public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "ldv at altlinux dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sources.redhat.com
Subject: [Bug localedata/10871] ru_RU: 'mon' array should contain both nominative and genitive cases
Date: Sun, 18 Nov 2012 12:23:00 -0000	[thread overview]
Message-ID: <bug-10871-716-uZNcVjeizH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10871-716@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=10871

Dmitry V. Levin <ldv at altlinux dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
            Summary|Ru_RU month names are in    |ru_RU: 'mon' array should
                   |incorrect form              |contain both nominative and
                   |                            |genitive cases

--- Comment #5 from Dmitry V. Levin <ldv at altlinux dot org> 2012-11-18 12:20:56 UTC ---
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > You'll have to provide a complete patch.
> > 
> > I could provide a patch, but there is a problem in specification. Neither "man
> > 5 locale" nor "man date" specify the case of name. It is not clear whether it
> > should be nominative, genitive or some another case.
> 
> If it is not specified, we should follow the language's rules.

And the language rules require to use nominative or genitive or some another
case depending on context.

> If it would be
> specified it has to be specified in accordance with the language's rules. So
> let me as a "native speaker" to suggest the solution.
> 
> Both months and weekdays should be in lower case.

It depends.

> The correct form of date
> should be "28 февраля" (the genitive).

Yes, but "февраль, 28-е" is also correct.

> > The solution could be extending `mon' array. For example, it could contain 12,
> > 24, or even more elements. Element #1 is name of January in nominative case,
> > element #13 is name of January in genitive case, #25 is the name of January in
> > some 3rd case, etc. `%B' is name of month in nominative case, `%1B' is the same
> > as `%B', `%2B' is the name of months in genitive case, `%3B' is the name of
> > months in the "3rd" case, etc.
> > 
> > Alternatively, it could be multidimensional array, so in construct `%nB' n
> > selects the proper dimension.
> > 
> > Any thoughts on that?
> 
> I think one should definitely extend the "mon" array. However the better idea
> would be to put there not the cases (nominative, genitive etc) but the contexts
> (month's name "as-is", month's name "when used in a date" etc). The array could
> be extensible.

Yes, putting "mon" array in a single case (no matter whether it would be
nominative, genitive or other case) cannot fix the issue, it would just fix
some language forms and break other language forms.  To fix the issue, an
extension is necessary.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-11-18 12:23 UTC|newest]

Thread overview: 138+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10871-716@http.sourceware.org/bugzilla/>
2011-02-28  5:12 ` [Bug localedata/10871] Ru_RU month names are in incorrect form van.de.bugger at gmail dot com
2012-11-18  7:49 ` a.m.suharev at gmail dot com
2012-11-18 12:23 ` ldv at altlinux dot org [this message]
2013-06-11 20:57 ` [Bug localedata/10871] ru_RU: 'mon' array should contain both nominative and genitive cases piotrdrag at gmail dot com
2014-07-01  5:56 ` fweimer at redhat dot com
2014-07-01  5:56 ` fweimer at redhat dot com
2014-09-11  0:39 ` samos-project at meta dot ua
2014-09-11  1:57 ` samos-project at meta dot ua
2014-09-11  7:14 ` fweimer at redhat dot com
2015-10-28  2:59 ` digitalfreak at lingonborough dot com
2015-10-28 21:33 ` piotrdrag at gmail dot com
2015-11-19  1:56 ` digitalfreak at lingonborough dot com
2015-11-20 18:40 ` piotrdrag at gmail dot com
2015-11-26 23:50 ` digitalfreak at lingonborough dot com
2016-01-05  2:18 ` digitalfreak at lingonborough dot com
2016-01-05  2:29 ` digitalfreak at lingonborough dot com
2016-01-05  2:34 ` digitalfreak at lingonborough dot com
2016-01-05  2:39 ` digitalfreak at lingonborough dot com
2016-01-05  2:46 ` digitalfreak at lingonborough dot com
2016-01-05  2:54 ` digitalfreak at lingonborough dot com
2016-01-05  3:09 ` digitalfreak at lingonborough dot com
2016-01-08 21:03 ` vapier at gentoo dot org
2016-01-13 21:20 ` van.de.bugger at gmail dot com
2016-01-13 23:50 ` vapier at gentoo dot org
2016-01-14 12:38   ` Keld Simonsen
2016-01-14 12:40 ` keld at keldix dot com
2016-01-14 12:51 ` vapier at gentoo dot org
2016-01-14 13:31   ` Keld Simonsen
2016-01-14 13:34 ` keld at keldix dot com
2016-01-14 14:42 ` vapier at gentoo dot org
2016-01-17  0:23 ` van.de.bugger at gmail dot com
2016-01-17  2:22   ` Keld Simonsen
2016-01-17  0:29 ` van.de.bugger at gmail dot com
2016-01-17  2:11   ` Keld Simonsen
2016-01-17  1:06 ` van.de.bugger at gmail dot com
2016-01-17  2:12 ` keld at keldix dot com
2016-01-17  2:28 ` keld at keldix dot com
2016-01-17  8:07 ` kon at iki dot fi
2016-01-17 14:03 ` van.de.bugger at gmail dot com
2016-01-17 15:57   ` Egmont Koblinger
2016-01-17 14:39 ` piotrdrag at gmail dot com
2016-01-17 19:48 ` piotrdrag at gmail dot com
2016-01-17 19:48 ` van.de.bugger at gmail dot com
2016-01-17 22:42 ` van.de.bugger at gmail dot com
2016-01-18  1:31 ` kon at iki dot fi
2016-01-19  1:30 ` van.de.bugger at gmail dot com
2016-01-20  7:13 ` kon at iki dot fi
2016-01-20  8:02 ` kon at iki dot fi
2016-01-21 23:16 ` digitalfreak at lingonborough dot com
2016-01-23  7:27 ` kon at iki dot fi
2016-01-27 23:18 ` digitalfreak at lingonborough dot com
2016-01-31 10:51 ` samos-project at meta dot ua
2016-03-03 14:06 ` piotrdrag at gmail dot com
2016-03-04 22:33 ` digitalfreak at lingonborough dot com
2016-03-24 11:15 ` digitalfreak at lingonborough dot com
2016-03-24 11:17 ` digitalfreak at lingonborough dot com
2016-03-24 11:23 ` digitalfreak at lingonborough dot com
2016-03-24 11:24 ` digitalfreak at lingonborough dot com
2016-03-24 11:26 ` digitalfreak at lingonborough dot com
2016-03-24 11:26 ` digitalfreak at lingonborough dot com
2016-04-18  5:44 ` vapier at gentoo dot org
2016-08-24 10:37 ` piotrdrag at gmail dot com
2016-08-28 23:48 ` digitalfreak at lingonborough dot com
2016-10-18  0:31 ` digitalfreak at lingonborough dot com
2016-10-18  0:31 ` digitalfreak at lingonborough dot com
2016-10-18  0:31 ` digitalfreak at lingonborough dot com
2016-10-18  0:31 ` digitalfreak at lingonborough dot com
2016-10-18  0:32 ` digitalfreak at lingonborough dot com
2016-10-18  0:32 ` digitalfreak at lingonborough dot com
2016-10-18  0:32 ` digitalfreak at lingonborough dot com
2016-10-18  0:32 ` digitalfreak at lingonborough dot com
2016-10-18  0:32 ` joseph at codesourcery dot com
2016-10-18  0:33 ` digitalfreak at lingonborough dot com
2016-10-18  0:33 ` digitalfreak at lingonborough dot com
2016-10-18  0:33 ` digitalfreak at lingonborough dot com
2016-10-28  0:10 ` digitalfreak at lingonborough dot com
2016-10-28  0:10 ` digitalfreak at lingonborough dot com
2016-10-28  0:10 ` digitalfreak at lingonborough dot com
2016-10-28  0:10 ` digitalfreak at lingonborough dot com
2016-10-28  0:10 ` digitalfreak at lingonborough dot com
2016-12-22 23:06 ` digitalfreak at lingonborough dot com
2016-12-22 23:10 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:34 ` digitalfreak at lingonborough dot com
2016-12-22 23:35 ` digitalfreak at lingonborough dot com
2016-12-22 23:35 ` digitalfreak at lingonborough dot com
2016-12-22 23:40 ` digitalfreak at lingonborough dot com
2017-03-20  8:48 ` digitalfreak at lingonborough dot com
2017-03-20  8:51 ` digitalfreak at lingonborough dot com
2017-03-20  8:58 ` digitalfreak at lingonborough dot com
2017-03-20  9:02 ` digitalfreak at lingonborough dot com
2017-03-20  9:11   ` Keld Simonsen
2017-03-20  9:05 ` digitalfreak at lingonborough dot com
2017-03-20  9:14 ` digitalfreak at lingonborough dot com
2017-03-20  9:14 ` keld at keldix dot com
2017-03-20 10:39 ` digitalfreak at lingonborough dot com
2017-03-20 10:40 ` digitalfreak at lingonborough dot com
2017-03-20 10:40 ` digitalfreak at lingonborough dot com
2017-03-20 10:40 ` digitalfreak at lingonborough dot com
2017-03-20 10:40 ` digitalfreak at lingonborough dot com
2017-03-20 10:40 ` digitalfreak at lingonborough dot com
2017-03-20 10:41 ` digitalfreak at lingonborough dot com
2017-04-12  8:15 ` fweimer at redhat dot com
2017-05-23 23:35 ` digitalfreak at lingonborough dot com
2017-05-23 23:35 ` digitalfreak at lingonborough dot com
2017-05-23 23:35 ` digitalfreak at lingonborough dot com
2017-06-28  0:59 ` digitalfreak at lingonborough dot com
2017-06-28  0:59 ` digitalfreak at lingonborough dot com
2017-06-28  1:00 ` digitalfreak at lingonborough dot com
2017-06-28  1:00 ` digitalfreak at lingonborough dot com
2017-06-28  1:00 ` digitalfreak at lingonborough dot com
2017-06-28  1:00 ` digitalfreak at lingonborough dot com
2017-06-28  1:00 ` digitalfreak at lingonborough dot com
2017-09-19 10:10 ` digitalfreak at lingonborough dot com
2017-09-19 10:13 ` digitalfreak at lingonborough dot com
2017-09-19 10:18 ` digitalfreak at lingonborough dot com
2017-09-19 10:19 ` digitalfreak at lingonborough dot com
2017-09-19 10:20 ` digitalfreak at lingonborough dot com
2017-09-19 10:23 ` digitalfreak at lingonborough dot com
2017-09-22 12:01 ` digitalfreak at lingonborough dot com
2017-11-16  1:49 ` digitalfreak at lingonborough dot com
2017-11-16  1:52 ` digitalfreak at lingonborough dot com
2017-11-16  1:53 ` digitalfreak at lingonborough dot com
2017-11-16  1:55 ` digitalfreak at lingonborough dot com
2017-11-16  2:01 ` digitalfreak at lingonborough dot com
2017-11-16  2:03 ` digitalfreak at lingonborough dot com
2017-11-16  2:04 ` digitalfreak at lingonborough dot com
2017-11-16  2:05 ` digitalfreak at lingonborough dot com
2017-11-16  2:06 ` digitalfreak at lingonborough dot com
2017-11-16  2:08 ` digitalfreak at lingonborough dot com
2017-11-16  2:09 ` digitalfreak at lingonborough dot com
2017-12-06  1:08 ` [Bug locale/10871] " digitalfreak at lingonborough dot com

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-10871-716-uZNcVjeizH@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sources.redhat.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).