public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: "Миронов Леонид Владимирович" <lv.mironov@severstal.com>,
	cygwin@cygwin.com
Subject: Re: getclip and putclip garble unicode characters
Date: Thu, 24 Jun 2021 09:35:54 +0300	[thread overview]
Message-ID: <1442655532.20210624093554@yandex.ru> (raw)
In-Reply-To: <af6d2888db8e4256b8c24064389aed9b@severstal.com>

Greetings, Миронов Леонид Владимирович!

> getclip and putclip from cygutils-extra garble unicode characters:
> non-latin characters copied to clipboard in windows are replaced with
> question marks when retrieved with getclip in cygwin, and non-latin
> characters copied to clipboard using putclip are pasted it in windows
> looking like utf-8 displayed in cp1252 but can be retrieved with getclip
> exactly as pasted, so it looks like the problem is not in the way the data
> is copied but in the way cygwin and windows communicate text encoding to
> each other. LC_CTYPE=en_US.UTF-8, windows ANSI codepage is set to cp1251 - 1251, not 1252.

This looks like you are using a program incapable of dealing with unicode
clipboard. To achieve better results, switch your input language/keyboard to
matching language before copying text from application. I.e. switch to
Russian then copy text, then check what is returned by getclip.
But then, why LC_CTYPE is en_US?


-- 
With best regards,
Andrey Repin
Thursday, June 24, 2021 9:33:54

Sorry for my terrible english...

  parent reply	other threads:[~2021-06-24  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 13:45 Миронов Леонид Владимирович
2021-06-23 22:27 ` Mark Geisert
2021-07-05 10:04   ` Mark Geisert
2021-06-24  6:35 ` Andrey Repin [this message]
2021-06-25  9:00   ` Миронов Леонид Владимирович
2021-06-25 18:01   ` Thomas Wolff
2021-06-25 18:54     ` Brian Inglis

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=1442655532.20210624093554@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=lv.mironov@severstal.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).