From: John Cowan <cowan@ccil.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 35920@debbugs.gnu.org,
"Christopher Lam" <christopher.lck@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Subject: bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8
Date: Sun, 30 Jun 2019 21:28:18 -0400 [thread overview]
Message-ID: <CAD2gp_TFRto1CThe1D3i1UtMUbC+T9ttBFpuU1gno+P9WFBpJg@mail.gmail.com> (raw)
In-Reply-To: <877e92k70r.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
On Sun, Jun 30, 2019 at 7:06 PM Mark H Weaver <mhw@netris.org> wrote:
Is there a portable way to find the relevant locale files and interpret
> them, on both POSIX and Windows systems? If so, can you point out the
> relevant documentation?
>
Portable in the sense that the information can be obtained on both Posix
and Windows, but not with exactly the same code.
On Posix, you need the nl_langinfo() and nl_langinfo_l() functions from
<langinfo.h>. These functions are documented at <
http://pubs.opengroup.org/onlinepubs/9699919799/functions/nl_langinfo.html>,
and the constants d at <
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/langinfo.h.html>.
On Windows, you need to call EnumCalendarInfoExEx if you have dropped
support for Vista and earlier versions, or if not, then follow the links
from the page about it. The function is documented at <
https://docs.microsoft.com/en-us/windows/desktop/api/Winnls/nf-winnls-enumcalendarinfoexex>,
and the constants that specify particular pieces of information at <
https://docs.microsoft.com/en-us/windows/desktop/Intl/calendar-type-information>.
(I have never used these interfaces myself.)
I hope this is helpful.
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
Eric Raymond is the Margaret Mead of the Open Source movement.
--Bruce Perens, a long time ago
[-- Attachment #2: Type: text/html, Size: 2326 bytes --]
next prev parent reply other threads:[~2019-07-01 1:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKVAZZKGeVMxtMsONgmM6dVkT2UZuCmNQrXFmrDkb9_TvW_Yeg@mail.gmail.com>
[not found] ` <877ebt7tc0.fsf@netris.org>
[not found] ` <CAKVAZZLTL1+AJCkQ0t8VbdS=39BxLG5=T7TD+C0_2_7-kPuY0g@mail.gmail.com>
[not found] ` <87tvew4efa.fsf@netris.org>
[not found] ` <CAKVAZZ+v9kFaAUxeJ5_opNSnmwJONT+wW14R38AHGpnwqEfuGA@mail.gmail.com>
[not found] ` <875zrb3ydk.fsf@netris.org>
[not found] ` <871s1z3tbq.fsf@netris.org>
[not found] ` <CAKVAZZLQ628QAfYffmOQ3Q4j9hzBck7nzh0BHSEshEU0sRQpOA@mail.gmail.com>
[not found] ` <CAKVAZZJP1veiMKYqpvZTZG2g6LO=_O-ovzouzEJ-T-mQUsOzYQ@mail.gmail.com>
[not found] ` <CAKVAZZJ0v1-snrRQj0CAxFikKDy+Xf_FWxHXV4tVJ1mVrnY8ig@mail.gmail.com>
2019-05-26 20:41 ` bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8 Mark H Weaver
2019-05-26 20:53 ` Mark H Weaver
2019-05-26 21:48 ` Mark H Weaver
2019-06-30 19:51 ` Ludovic Courtès
2019-06-30 21:12 ` Mark H Weaver
2019-06-30 22:37 ` John Cowan
2019-06-30 23:06 ` Mark H Weaver
2019-07-01 1:28 ` John Cowan [this message]
2019-07-02 8:58 ` Ludovic Courtès
2019-07-02 9:07 ` Ludovic Courtès
2019-07-02 16:51 ` John Cowan
2019-05-27 0:04 ` Christopher Lam
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2gp_TFRto1CThe1D3i1UtMUbC+T9ttBFpuU1gno+P9WFBpJg@mail.gmail.com \
--to=cowan@ccil.org \
--cc=35920@debbugs.gnu.org \
--cc=christopher.lck@gmail.com \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).