From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 119181 invoked by alias); 30 Jan 2018 22:57:29 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 119168 invoked by uid 89); 30 Jan 2018 22:57:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=month, d, opportunity, day X-HELO: ano163.rev.netart.pl X-Spam-Score: 1 Date: Wed, 31 Jan 2018 17:22:00 -0000 From: Rafal Luzynski Reply-To: Rafal Luzynski To: libc-alpha@sourceware.org, Carlos O'Donell Message-ID: <886475278.52145.1517353042610@poczta.nazwa.pl> In-Reply-To: <3bc43235-8938-980c-4354-019969cc9cc8@redhat.com> References: <1802414843.37687.1515744747279@poczta.nazwa.pl> <1927758682.38060.1515745107778@poczta.nazwa.pl> <49ea50a9-3cca-bbfe-8c75-41ea603d1a58@pacific.net> <232736801.586762.1516016805848@poczta.nazwa.pl> <1451718525.153086.1516445418821@poczta.nazwa.pl> <1069394619.57314.1516610620585@poczta.nazwa.pl> <1090774665.1268651.1516745363342@poczta.nazwa.pl> <2074921143.499812.1516841147600@poczta.nazwa.pl> <3bc43235-8938-980c-4354-019969cc9cc8@redhat.com> Subject: Re: [PATCH v12 5/6] Documentation to the above changes (bug 10871). MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Originating-Client: com.openexchange.ox.gui.dhtml X-SW-Source: 2018-01/txt/msg01138.txt.bz2 25.01.2018 02:47 Carlos O'Donell wrote: > > > On 01/24/2018 04:45 PM, Rafal Luzynski wrote: > > I have received a comment from Gnulib maintainers that this > > documentation is too ambiguous because does not define which > > date format should be considered "full" and which should be > > considered "month standalone". I have explained that the date > > is "full" if there is a day number and a month name (the week > > day and the year number are optional) and the month name is > > "standalone" when there is no day number (it may be just the > > month name alone, or if a year number is added this still counts > > as standalone). It has been requested to add this definition > > to the glibc documentation. > > > > But, OTOH, I can't guarantee this works the same in all languages > > which have this issue. Maybe we should add a phrase "in many > > languages" or "in most of the languages which need this feature"? > > > > Any suggestions how to fix the documentation? Does anybody want > > to commit immediately? > > I see no immediate need to rush into documenting this any more than > is currently documented. Please reflect on the comments provided > by the gnulib maintainers and see if any ideas come to mind. I still remember it needs to be fixed. While the manual and even the comments may be updated later NEWS file probably will not. I had an opportunity to discuss this with Dmitry and we have agreed that we should reword "when the month is used as part of a complete date" into "when the month appears together with a day of the month" and "when the month is named by itself" with "when the month appears without a day of the month" in order to make sure the readers understand the rules correctly. But I'm still thinking whether this is really the good direction. The old statements were ambiguous but easy to understand. The new ones may be not so easy. What about using both of them, like "when the month appears together with a day of the month (e.g., when it is used as part of a complete date)" and "when the month appears without a day of the month (e.g., when it is named by itself)" or even "(e.g., when it appears standalone)"? Also I think we need to mention at least once in the manual that some languages may have different rules. For example, Dmitry's comment [1] is a valid use of the nominative case despite appearing together with a day number (this corner case should be handled by translators and they should use the format "%OB, %-d-=D0=B5"). > In my experience it is sometimes best to use examples here to define > what you mean. So instead of writing completely generic text, we > use Polish as an example and describe which is full and standalone > using the example. I think we can use more languages to emphasize that the feature is not Polish-specific and to increase a chance that an example will be more familiar to the readers. What about Catalan, Upper Sorbian, Latin? (Note: Latin is not supported in glibc). Regards, Rafal [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3D10871#c5