public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Helmut Karlowski <helmut.karlowski@ish.de>
To: cygwin@cygwin.com
Cc: cygwin@cygwin.com
Subject: utf/codepage-conversion on cmd-window
Date: Tue, 06 Oct 2015 19:01:00 -0000	[thread overview]
Message-ID: 5AC96F1252A8B8C03DC3FD65665BC476
Message-ID: <20151006210122.160D1A28.helmut.karlowski@ish.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

I came across a surprising behaviour when a cygwin-process prints to a
windows-console. In cygwin 1.7 (XP) I don't think any conversion took 
place, while now in cygwin 2 (10) cygwin-utf-8 gets converted into the
suitable(?) windows-encoding used in the cmd-window.

I have a file containing german umlaut-characters encoded in utf-8 and
cp850.

When I'm in the cmd-window:

C:\bat>type cmduml.txt
├û├ä├£├Â├ñ├╝├ƒ      -> some cp850-characters with 
high-bit set
ÖÄÜöäüß              -> correct output

C:\bat>\cygwin\bin\cat cmduml.txt
ÖÄÜöäüß               -> utf converted to cp850
¦¦¦¦¦¦¦                            -> ???

C:\bat>chcp
Aktive Codepage: 850.

It makes things easier the way it is now, but I could not find it 
documented. Also I wonder about cygwin's output of the 
cp-850-characters, I'd expect them to be printed unchanged, instead I 
only see grey rectangles.

In the cygwin-window the file is:

/c/bat|17:05:30#od -x cmduml.txt
0000000 96c3 84c3 9cc3 b6c3 a4c3 bcc3 9fc3 990a
0000020 9a8e 8494 e181 0a0d
0000030

I've also attached it.

I hope all is displayed correctly, but it should be easy to reproduce.

-Helmut


[-- Attachment #2: cmduml.txt --]
[-- Type: application/octet-stream, Size: 24 bytes --]

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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:[~2015-10-06 19:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5AC96F1252A8B8C03DC3FD65665BC476 \
    --to=helmut.karlowski@ish.de \
    --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).