public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Need help with multibyte UTF-8 characters
Date: Thu, 14 Dec 2017 16:21:00 -0000	[thread overview]
Message-ID: <5d68998a-b278-668f-c547-6bc341147205@towo.net> (raw)
In-Reply-To: <8d811915-176f-c9f5-6500-364e494142f7@SystematicSw.ab.ca>

Am 14.12.2017 um 05:40 schrieb Brian Inglis:
> On 2017-12-13 00:50, Thomas Wolff wrote:
>> Am 13.12.2017 um 06:21 schrieb Brian Inglis:
>>> On 2017-12-04 18:23, Thomas Taylor wrote:
>>> Your Windows Regional settings and your mintty/Options/Text/Language and
>>> Character Set should be set to match.
>>> The profile commands below set Cygwin locale to your Windows Regional settings
>>> and charset to UTF-8, or Unix locale to your system locale.
>>> Otherwise your system or mintty is going to be doing conversions on each
>>> character.
>> I am not aware that mintty character display and Windows regional settings would
>> interfere in any way you indicated.
>> Can you elaborate on this please?
> Maybe I'm just too optimistic that software will DTRT to ensure that output is
> faithfully passed thru, or converted for the next layer of software, if it has
> different settings.
> I set all of my locales the same so characters should pass thru transparently
> and I can see output faithfully rendered, given adequate font configurations.
Mintty interfaces to Windows using the Unicode/UTF-16 API, so there is 
no dependency on the Windows system locale.
I assume the original poster's problem is a font issue, unless a test 
case would demonstrate anything else.
Thomas

> What happens when your system, terminal, and shell locales and charsets differ?
> Either some component/-s has/have to do conversion to provide readable output,
> which is my expectation given the requirement to specify locales and charsets,
> or you could end up with garbled output if nothing is doing any conversion.
> Does one override others to pass thru readable output, does conversion occur, or
> do you just see junk in some or all cases when locales and charsets differ?
>
> I am ignoring here the effect on text content, input and output formatting of
> selecting languages, territories, and scripts.

--
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

  reply	other threads:[~2017-12-14  8:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  1:24 Thomas Taylor
2017-12-05  3:48 ` Brian Inglis
2017-12-12  3:43 ` Thomas Taylor
2017-12-12 20:00   ` Doug Henderson
2017-12-12 20:17   ` Thomas Taylor
2017-12-14 19:50     ` Andrey Repin
2017-12-15  2:51     ` Brian Inglis
2017-12-16  1:50       ` Thomas Wolff
2017-12-13  3:06   ` Thomas Wolff
2017-12-14 19:32   ` Brian Inglis
2017-12-13 13:07 ` Brian Inglis
2017-12-13 13:28   ` Thomas Wolff
2017-12-14  1:15     ` cyg Simple
2017-12-14  7:36     ` Brian Inglis
2017-12-14 16:21       ` Thomas Wolff [this message]
2017-12-14 18:09         ` cyg Simple
2017-12-14 19:20           ` Thomas Wolff
2017-12-14 16:55       ` cyg Simple

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d68998a-b278-668f-c547-6bc341147205@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.com \
    /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).