Date: Sun, 05 May 2019 00:30:34 +0000 From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 237752] LC_TIME keywords violate POSIX Message-ID: <bug-237752-99@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237752 Bug ID: 237752 Summary: LC_TIME keywords violate POSIX Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: standards Assignee: standards@FreeBSD.org Reporter: alex+freebsd@strugee.net IEEE Std 1003.1-2004 ("POSIX.1")[1] section 7.3.5.1 states: > In a locale definition, the following mandatory keywords shall be recogni= zed: > > [...] > > [abmon] Define the abbreviated month names, corresponding to the %b conve= rsion specification. The operand shall consist of twelve semicolon-separate= d strings, each surrounded by double-quotes. The first string shall be the= abbreviated name of the first month of the year (January), the second the= abbreviated name of the second month, and so on. However, it turns out that FreeBSD does not conform to this behavior. `loca= le -k abmon` returns "Unknown keyword: `abmon'". On the other hand, `locale -k abmon_1` _does_ return "Jan", and so on and so forth. It seems to me that this is a bug and that the locale keywords need to be changed if FreeBSD wants to conform to POSIX. Note that locale(1) claims to= be conformant to POSIX.1. I have confirmed this bug both on FreeBSD 11.2 and on FreeBSD 12. (For some context, I'm the maintainer of filter-other-days[2] and in the co= urse of trying to figure out how to do localization support, I started using `lo= cale -k` to extract this information from the system.) [1]: https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=3D&arnumber=3D1309815 [2]: https://github.com/strugee/filter-other-days --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237752-99>