public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ralf <wiesweg@tacos-gmbh.de>
To: cygwin@cygwin.com
Subject: Re: Internal echo of shell beaves (sometimes) different to external echo
Date: Fri, 20 Jul 2012 07:08:00 -0000	[thread overview]
Message-ID: <loom.20120720T084207-511@post.gmane.org> (raw)
In-Reply-To: <50086B4A.6090801@laposte.net>

Cyrille Lefevre <cyrille.lefevre-lists <at> laposte.net> writes:

> 
> Le 19/07/2012 16:51, Ralf a écrit :
> > Is there a way to get the right umlaut with the internal echo of the shell?
> > Example script:
> >
> > export LC_ALL=de_DE
> 
> seems to default to iso8859-1 or something like that, let's try
> 
> export LC_ALL=de_DE.UTF-8
> 
> which should work better...
> 

export LC_ALL=de_DE.UTF-8 gives following output:

 C:\>bash ttt.sh
 CYGWIN_NT-6.0-WOW64 WIESWEG 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
 Râ–’cken
 0000000   R 374   c   k   e   n  \r  \n
 0000010
 Râ–’cken
 0000000   R 374   c   k   e   n  \n
 0000007
 Râ–’cken
 0000000   R 374   c   k   e   n  \n
 0000007


> also, check your that terminal setting is UTF-8 both for input/output.

How do I check that my terminal setting is UTF-8 both for input/output?
All settings I use are made in inputrc:
 C:\>cat ~/.inputrc
 set meta-flag on
 set convert-meta off
 set output-meta on
And in my environment variables:
 ...
 BASH=/usr/bin/sh
 BASHOPTS=cmdhist:expand_aliases:extquote:force_fignore:hostcomplete:interactive
 _comments:progcomp:promptvars:sourcepath
 BASH_ALIASES=()
 BASH_ARGC=()
 BASH_ARGV=()
 BASH_CMDS=()
 BASH_LINENO=()
 BASH_SOURCE=()
 BASH_VERSINFO=([0]="4" [1]="1" [2]="10" [3]="4" [4]="release" [5]="i686-
 pc-cygwin")
 BASH_VERSION='4.1.10(4)-release'
 ...
 CYGWIN=nodosfilewarning
 ...
 POSIXLY_CORRECT=y
 ...
 SHELL=/bin/bash
 SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-
 comments:monitor:posix
 ...
 TERM=cygwin
 ....
> 
> tried using fr_FR vs fr_FR.UTF-8 and echo vs /bin/echo, both work well 
> in all case !
> 

Do you use rxvt, mintty or something like that?

Regards
Ralf


--
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:[~2012-07-20  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 14:51 Ralf
2012-07-19 20:16 ` Cyrille Lefevre
2012-07-20  7:08   ` Ralf [this message]
2012-07-20  8:25     ` Corinna Vinschen
2012-07-20 10:47       ` Ralf
2012-07-20 11:53         ` Andy Koppe
2012-07-20 12:09           ` Ralf

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=loom.20120720T084207-511@post.gmane.org \
    --to=wiesweg@tacos-gmbh.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).