From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 97305 invoked by alias); 11 Jan 2017 12:52:13 -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 97296 invoked by uid 89); 11 Jan 2017 12:52:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=impressed, oem, OEM, H*MI:sk:9b07d29 X-HELO: mail-oi0-f49.google.com Received: from mail-oi0-f49.google.com (HELO mail-oi0-f49.google.com) (209.85.218.49) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Jan 2017 12:52:02 +0000 Received: by mail-oi0-f49.google.com with SMTP id u143so176237480oif.3 for ; Wed, 11 Jan 2017 04:52:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:subject:to:in-reply-to :user-agent; bh=2FQ891ApJFkmphMBHfO0r8nTGUG2aIeBFVwkOmLLwEc=; b=GOlONkd0yHZ7GIg11bJUeyEItifuObdRUsW6mcT+fTJwzzu1FkxTBxuTDzljVa+cjZ YQPXajV7Io3itaOIHZQfcORRpX49pnTn3ducbkgQQKbiqr+1MZTymilDWP/VcPwyLUUS /0ho6Sy1GWYdXMRbyIMFEoh0aK/b+deuSDUmS/lOOZfAJ6DbROLz3WST3pZvhKSbiISJ XoZDJ6gdzyIDyuJoo6isqyLnacf18qBnFnXoRDCOvgGtrgCPx3xqd9ECbxZ23yaJntoH lXu6uZvjwlrQic5V/OJvN0zTudtePWBOQecO8g0durUvbrAlRcDneuSuXpe8NHs66eC0 F5VQ== X-Gm-Message-State: AIkVDXKN/iRXt/nlvSrtT21eNSomlBxtw2CIPkH1dFT75VrRpvhO0amD0R9TD4xs5B/aAQ== X-Received: by 10.157.46.57 with SMTP id q54mr3912784otb.28.1484139120372; Wed, 11 Jan 2017 04:52:00 -0800 (PST) Received: from tmp.ggvAVAUyc1 ([2605:6000:9fc0:56:811:343f:f904:d318]) by smtp.gmail.com with ESMTPSA id n126sm2328011oia.18.2017.01.11.04.51.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jan 2017 04:51:59 -0800 (PST) Message-ID: <58762a6f.8440ca0a.2df89.dc44@mx.google.com> Date: Wed, 11 Jan 2017 12:52:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1 To: cygwin@cygwin.com In-Reply-To: <9b07d29e-1978-e726-90af-1822c11de9a4@SystematicSw.ab.ca> User-Agent: mailing-list.awk X-SW-Source: 2017-01/txt/msg00094.txt.bz2 On Tue, 10 Jan 2017 23:49:16, Brian Inglis wrote: > Both of which run under the cmd console No, they dont. They both run under the Console Window Host. > You can look up which characters are displayed using Alt-numpad-digits > at https://en.wikipedia.org/wiki/Code_page_437 or in the selected code > page using Alt-numpad-0-digits at Code_page_nnn or Windows_nnnn. Why do I need to do this? I already know that it is capital omega. > On top of that is added the Windows locale mapping to Cygwin locale and > character set, plus readline settings used by bash in ~/.inputrc, which > may change input interpretation. Again, did you try this or are you just guessing? If so what inputrc value needs to be set? > Type locale to see what locale Cygwin thinks you are running. > Documentation available is at: > https://cygwin.com/cygwin-ug-net/setup-locale.html > which documents the default as C.UTF-8 (ASCII) unless LC_ALL, LC_CTYPE, > or LANG env vars are set to change the locale and/or char set. Again, did you try this or are you just guessing? If so what value needs to be set? > You may have to chcp n in Cygwin.bat to get correct character output, > either 437 for US, 850 for English, 65001 for UTF-8, others from > above reference for other locales and char sets. Again, no because cmd.exe works fine even with 437. > It is an alternative input method for Unicode characters which does > not seem to be supported with bash under cmd configured with default > code pages, but is in mintty and elsewhere in Windows, which avoids > having to pop up CharMap and search when you know the Unicode code > point wanted. Again, hex input is not needed, cmd.exe handles Alt-decimal just fine. > Most Windows monospace fonts do not support most new Unicode characters, > but fallback fonts can be configured in the registry to provide missing > glyphs, given available fonts which support the glyphs, and code page > 65001/char set UTF-8 which supports the Unicode character set. Again, no font is needed as this character is already supported though existing fonts. > Mea culpa, having configured everything I can in Windows, Cygwin, and > apps to support Unicode/UTF-8 character sets, with appropriate fonts > and fallbacks, I forget the limitations and problems with OEM code > pages which caused me to make that effort, indeed that people, apps, > or systems still use those code pages implicitly. Somehow you managed to make a nearly 400 word reply without adding anything to your previous post. I am actually impressed. Please going forward post suggestions that you have actually tried and fix the problem at hand, thank you. -- 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