From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Need help with multibyte UTF-8 characters
Date: Wed, 13 Dec 2017 13:28:00 -0000 [thread overview]
Message-ID: <89a7d883-e3e5-42d7-2d22-020cdf6ccbdf@towo.net> (raw)
In-Reply-To: <b190e8bc-a60e-2a30-5caa-a2f67a0b91ce@SystematicSw.ab.ca>
Hi Brian,
Am 13.12.2017 um 06:21 schrieb Brian Inglis:
> On 2017-12-04 18:23, Thomas Taylor wrote:
>> I want to use multibyte UTF-8 characters in 64-bit Cygwin under Windows 7. The
>> "vim" editor running in mintty displays the two-byte characters correctly, but
>> not the three- (and I assume four-) byte characters, which instead display as
>> rectangular filled-in blocks. The "less" program doesn't even display two-byte
>> characters correctly, but instead displays them as <A1> to <FF>, depending on
>> the character in question, in reverse color in the terminal window. The "cat"
>> program is even worse, replacing every two-byte character with a character that
>> looks like three horizontal bars stacked one above the other. I've read the
>> "Internationalization" page in the Cygwin online manual, but am still baffled.
>> My LANG environment variable is set to "en_US.UTF-8". Can anyone help?
> 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?
Thomas
> # Set user-defined locale
> locale -fU > /dev/null 2>&1 \
> && LC_ALL=$(locale -fU) \
> || LC_ALL=$(locale | \
> sed '/^LANG=\|^LC_CTYPE=\|^LC_ALL=/{s///;h};$!d;x;s/"//g')
>
--
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
next prev parent reply other threads:[~2017-12-13 7:50 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 [this message]
2017-12-14 1:15 ` cyg Simple
2017-12-14 7:36 ` Brian Inglis
2017-12-14 16:21 ` Thomas Wolff
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=89a7d883-e3e5-42d7-2d22-020cdf6ccbdf@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).