public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Thomas Taylor <tayloth@gmail.com>, cygwin@cygwin.com
Subject: Re: Need help with multibyte UTF-8 characters
Date: Thu, 14 Dec 2017 19:50:00 -0000	[thread overview]
Message-ID: <1534444625.20171214221946@yandex.ru> (raw)
In-Reply-To: <1909177a-3f35-52d5-1717-9007d6efaa71@gmail.com>

Greetings, Thomas Taylor!

> I believe that Cygwin displays certain UTF-8 characters incorrectly.  To 
> see the problem, first save the attached "utf-8_test.sed" text file to 
> your desktop. 

First, your "NBSP" is actually http://www.fileformat.info/info/unicode/char/23b5/index.htm

> Then run "mintty," and set its options by right clicking
> in its title bar, selecting "Options" and then "Text." 

I just keep them clear.

> On the Text page
> set "Locale" to "en_US" and "Character set" to "UTF-8," and then 
> "Save."  Now exit and restart mintty.  Change directory to your desktop 
> and run the editor "vim" on the utf-8_test.sed file.  Once inside vim do 
> a ":set fileencoding=utf-8".  You should now see that vim displays 
> correctly a sample of one-, two-, and three-byte UTF-8 character 
> encodings in the test file.  Vim fails, however, on the three-byte 
> encodings for the "en" dash, the "em" dash, and the ellipsis, each of 
> which displays incorrectly as a filled-in rectangle.  Now exit vim and 
> do a "less" or "cat" on the utf-8_test.sed file.  You should see most of 
> the sample UTF-8 encoded characters displayed correctly, except once 
> again for the en dash, em dash, and ellipsis. 

All displayed correctly. Lucida Console 11pt.

> So it looks like a problem in the underlying Cygwin run-time libraries
> rather than in vim, less, or cat.  I haven't tested this on four-byte UTF-8
> character encodings, but assume Cygwin will have similar problems.

I don't have a good console font for mb4, but I presume it will be displaed
just fine.


-- 
With best regards,
Andrey Repin
Thursday, December 14, 2017 21:59:07

Sorry for my terrible english...
--
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 19:20 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 [this message]
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
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=1534444625.20171214221946@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=tayloth@gmail.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).