public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Internal echo of shell beaves (sometimes) different to external echo
Date: Fri, 20 Jul 2012 08:25:00 -0000	[thread overview]
Message-ID: <20120720082452.GV31055@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20120720T084207-511@post.gmane.org>

On Jul 20 07:08, Ralf wrote:
> 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

What you don't seem to see is that the codeset doesn't play any role
anymore *at this point in time*.  You already created the string
"Rücken" in ISO-8859-1 at the time you created the script and your
script will diligently create the file ttt.txt with the word Rücken in
ISO-8859-1, because that's how it's stored in the script.  Thus, it
doesn't matter what codeset you have set when running that script.

Here's an idea for you to test:

Replace

  echo "Rücken" > ttt.txt

with

  read -p "Enter: " foo
  echo "$foo" > ttt.txt

And then start your script with LANG set to, for instance, C.UTF-8, as is
the default when running an interactive Cygwin shell like bash or tcsh.
(though I would prefer to use POSIX paths rather than DOS paths:
 http://cygwin.com/cygwin-ug-net/using.html#using-pathnames)


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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  8:25 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
2012-07-20  8:25     ` Corinna Vinschen [this message]
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=20120720082452.GV31055@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).