Re: [RFC][PATCH v8 08/16] Let alternative month names be a copy of regular ones (bug 10871).

[Rafal Luzynski <digitalfreak at lingonborough dot com>]

3.07.2017 23:33 Zack Weinberg <zackw@panix.com> wrote:
>
>
> On 06/28/2017 06:05 AM, Rafal Luzynski wrote:
> > If alt_mon definition is missing from a locale then let it be
> > a copy of mon array. Majority of languages do not need this feature
> > so let us accept the locale definition file without alt_mon and
> > provide the same content as mon when software requires alt_mon.
>
> This seems a reasonable policy, but it should be documented.

OK but where is the documentation of the locale data file?
I can't find it.

> > + /* If alt_mon is missing then let it be a copy of mon. */
>
> "Let it be <thing>" is unusual in English, although it does get used in
> formal mathematical writing. Instead
>
> /* If alt_mon was not specified, make it a copy of mon. */

Thank you.  If I didn't say it before then I must say now that as
a non-English native speaker I will need some proofreading of the
natural language texts, for example the documentation.

While at this, I'm not sure if I named the symbols for the abbreviated
alternative month names correctly:

locale data source file label: "ab_alt_mon"
macros in locale/langinfo.h: _NL_ABALTMON_1 ...12, _NL_WABALTMON_1 ...12

Compare this with alternative month names (my new feature) and abbreviated
month names (already existing):

locale data source file label: "alt_mon", "abmon"
macros in locale/langinfo.h: ALTMON_1 ...12, _NL_WALTMON_1 ...12,
ABMON_1 ...12, _NL_WABMON_1 ...12

Sorry if it looks nit-picky again but I'm aware that once the decision
is made it will be difficult to undo it.

Regards,

Rafal