This is the mail archive of the
mailing list for the Cygwin project.
Re: "Accented" characters
- To: cygwin <cygwin at sourceware dot cygnus dot com>
- Subject: Re: "Accented" characters
- From: Alain CULOS <Alain dot EnnisZ at eircom dot net>
- Date: Fri, 08 Oct 1999 19:43:34 +0100
- Organization: http://homepage.eircom.net/~joannaalain/
- Reply-To: Alain dot CulosZ at bigfoot dot com
[Please note I am NOT subscribed to the list]
[Please BCC any reply to my address without the Z]
A long time ago I was enquiring about how to get bash to display accents
DOS box but I still have not gotten around to doing that.
So I hope you will forgive me for restarting that thread.
In my .bat script for starting bash I included the two lines from the autoexec
prepare the page ... for bash just in case.
Here is what it does when I start bash :
MODE prepare code page function completed
MODE select code page function completed
This part is still in the .bat and seem to work.
Now proceed to bash itself, when it starts immediately after the above output :
1 -> /c/WINDOWS/COMMAND.COM /c chcp 850
Code page 850 not prepared for system
Strange isn't it ?
2 -> cat /c/AUTOEXEC.BAT
mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
The above is what I duplicated in my bash start up script.
Works in DOS, accents show fine.
Does not work in bash, accents not input or displayed.
Should I do something with the termcap file ?
If so, could someone point me to the relevant termcap documentation and possibly
Alain CULOS wrote (a long time ago) :
> Benjamin Riefenstahl wrote:
> > Hi Alain,
> > > Benjamin Riefenstahl wrote:
> > > > Firstly, in b18 bash needs the complete filename for CHCP, so it's
> > > > actually "chcp.com 1252".
> > Alain CULOS wrote:
> > > When I read that I was delighted I would be able to have proper accents in
> > > Bash/Dos window.
> > > Pity is I don't seem to have chcp.com at all at all (yes I did a
> > > search on my disk).
> > > Any idea what could replace chcp on a Windows 95 B platform ?
> > > The rest will probably work fine once I have that chcp thingy replaced.
> > As some other Win95 user found out, it looks like this is rather
> > difficult on Win95.
> > CHCP is an internal command of command.com on Win95. So for that part
> > "$COMSPEC /c chcp 1252" is the solution.
> OK, so I used this but windows 95 only wants a three digit code for
> I tried 851 at random and it told me the page was not prepared for
> Anyway, in my DOS box accents are perfect, it's only BASH that
> displays them badly.
> > But the main problem is, it seems that support for code page 1252 in the
> > console window doesn't come with the regular Win95 installation. I don't
> > know where to get the necessary files and how exactly to install and
> > activate them. You could try to find these files and instructions at
> > http://www.microsoft.com, but I'm not sure that this will work at all.
> I'll try that some time.
> I checked my autoexec.bat and it shows something like :
> mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
> mode con codepage select=850
> So I went about reading ega.cpi (I would assume this is code page
> information) and found a nice binary file, that's where I stopped so
> > Another solution might be to use some other command window like the rxvt
> > that I have seen discussed here. It's at
> > http://www.io.com/~bub/rxvt.html according to the last resource pointer
> > post.
> I'll also have a look at that some time.
> Thanks for the pointers.
> ANTI SPAM / ANTI ARROSAGE COMMERCIAL :
> Pour me répondre, veuillez enlever le Z de mon adresse.
> To answer me, please take out the Z from my address.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org