From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 83348 invoked by alias); 10 Jan 2019 00:07:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 83340 invoked by uid 89); 10 Jan 2019 00:07:52 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=limitation, jony, JonY, cygwins X-HELO: mail-it1-f196.google.com Received: from mail-it1-f196.google.com (HELO mail-it1-f196.google.com) (209.85.166.196) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Jan 2019 00:07:50 +0000 Received: by mail-it1-f196.google.com with SMTP id a6so13778871itl.4 for ; Wed, 09 Jan 2019 16:07:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=jYLasmtyymDdTgptVpyQ7bD9aBkg4okQSM2RCxevZVs=; b=nnAwnZolHylftrrfnJ6H7mrgORL3hGfmUKfHgHZdE2Bhew/E173fkLXL2EL6C/TLsf 4Cd42ww5XslCztZW47UKkLC6z649f6d3Nhw1Myb0ANaB694NJSpQFvVSYBs1YQWdJPFK 17wTqXOhT2NCI94+tUqTa5znUBdKeL/FORRo2cdwnT4NN1YhnrQCt+FwRCwTGEbANc0/ W8+QMc/obG9zrTwSa4hFbHV7/E49f2hy6MJ8S2c8+upWrPL8XVPmaUxp4wBKU4bEEXB6 rJiFunhlHQKN0FVJLQ6tt5xKWH/skqjQU01dHj4CxwZ/yuApsUw75a+uvSpET9kTQBS+ 6A+Q== MIME-Version: 1.0 Received: by 2002:a4f:1fc4:0:0:0:0:0 with HTTP; Wed, 9 Jan 2019 16:07:47 -0800 (PST) In-Reply-To: <7fca2500-d62e-e251-c832-bb6bf2b5f03d@SystematicSw.ab.ca> References: <92c7e8c2-c440-1bb8-f329-23951d10dffe@gmail.com> <2ec22a55-c5d6-d425-02fe-ec9508a30275@obj-sys.com> <7fca2500-d62e-e251-c832-bb6bf2b5f03d@SystematicSw.ab.ca> From: Lee Date: Thu, 10 Jan 2019 00:07:00 -0000 Message-ID: Subject: Re: i686-w64-mingw32-gcc: LC_MESSAGES To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00057.txt.bz2 On 1/9/19, Brian Inglis wrote: > > On 2019-01-09 12:43, Lee wrote: >> On 1/9/19, Douglas Coup wrote: >>> >>> On 1/9/2019 1:14 PM, Lee wrote: >>>> On 1/9/19, JonY wrote: >>>>> On 1/8/19 9:26 PM, Lee wrote: >>>>>> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/locale.h.html >>>>>> has a note for LC_MESSAGES: >>>>>> The functionality described is an extension to the ISO C standard. >>>>>> Application developers may make use of an extension as it is >>>>>> supported on all POSIX.1-2017-conforming systems. >>>>>> i686-w64-mingw32-gcc doesn't have LC_MESSAGES defined. >>>>>> Is that an oversight, something missing in windows, or .. ?? >>>>> Windows MSVCR isn't POSIX nor ISO C compliant, so you shouldn't be >>>>> referring to opengroups, only against MSDN. >>>> What's a Windows MSVCR? >>>> Since the same program compiled with cygwins' gcc has LC_MESSAGES >>>> defined, I was guessing it was just a library thing and maybe it just >>>> hadn't been implemented in the mingw libraries yet.. but it sounds >>>> like it's not an oversight & Microsoft needs to support LC_MESSAGES >>>> before i686-w64-mingw32-gcc will. Is that about right? >>> MSVCR = MicroSoft Visual C Run-time (I think) >> Meaning i686-w64-mingw32-gcc uses the Microsoft libraries vs. cygwin >> gcc using posix compliant libraries? Implying LC_MESSAGES not being >> defined is yet another instance of Microsoft not following accepted >> standards? >> The background for my question is >> https://github.com/htacg/tidy-html5/issues/770 >> Tidy removed the setlocale call from the library init function, so if >> users want a specific locale/language they're going to have to set it >> up themselves. >> I'd like to update the tidylib example code showing how to set the >> language, but >> setlocale(LC_ALL, ""); >> tidySetLanguage( setlocale(LC_MESSAGES, NULL) ); >> probably isn't a good example if LC_MESSAGES is missing on some systems. > > You have to convert your messages to Windows message resources in your > build, then link and package Windows message resources with non-POSIX > compliant exes, or add a POSIX message implementation to your exes. I'm just trying to come up with example code for how to set the locale & language in the tidylib documentation; thankfully, me building a native windows version of tidy isn't the goal.. I was just trying out code that worked under cygwin & was a bit surprised it wouldn't even compile for windows. But it seems to be a windows limitation, so [snip snarky comment] Regards, Lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple