"Accented" characters

"Accented" characters

[Henrik Johansson]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

I recently installed cygwin release 20.1, and almost everything works
just great!

There is a couple of problems, however.  When I write (in bash)
	ls //c/tmp/l*.txt
the response is
	//c/tmp/l?smig.txt
even though the real filename is "läsmig.txt" (the second character in
the filename has the code 228, or 0xE4...it is an 'a' with two dots).

The second (probably related) problem is: a file contains a list of
filenames on separate lines, and I have a shellscript that reads the
list file line by line, and works on the files one by one.  When it
sees the line
	//c/tmp/läsmig.txt
and sets the variable F to this value, an
	ls "$F"
results in the following error:
	ls: //c/tmp/lSsmig.txt: No such file or directory

Strange, isn't it?

I have done the following at the bash prompt, but nothing is changed:
	set meta-flag On
	set convert-meta Off
	set output-meta On

The FAQ and other information on your web site didn't mention this, so
I thought it was best to send you a letter about it.

Best regards,

/hj

--
Name: Henrik Johansson, email:  Henrik.Johansson@Nexus.SE,
Phone: +46 18 171811, Fax: +46 18 696516,
Address: Technology Nexus AB, Box 857,
S - 751 08 Uppsala, Sweden

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

Hi Henrik,

Henrik Johansson wrote:
> There is a couple of problems, however.  When I write (in bash)
>         ls //c/tmp/l*.txt
> the response is
>         //c/tmp/l?smig.txt
> even though the real filename is "läsmig.txt" (the second character in
> the filename has the code 228, or 0xE4...it is an 'a' with two dots).

Try the command

	chcp 1252

Background: Consoles in Win/32 still use the so-called "OEM" character
set encoding for display instead of the so-called "ANSI" encoding used
in GUI apps and for the file system. The CHCP command (CHange CodePage)
switches between the various installed codepages for consoles. 1252 is
the codepage usually used by GUI apps in western versions of Windows, so
doing "CHCP 1252" makes the standard GUI codepage and the codepage of
the console the same. This eliminates conversion errors which are most
probably the root of your problem.

so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]

Hi everybody,


> Henrik Johansson wrote:
> > There is a couple of problems, however.  When I write (in bash)
> >         ls //c/tmp/l*.txt
> > the response is
> >         //c/tmp/l?smig.txt
> > even though the real filename is "läsmig.txt" (the second character in
> > the filename has the code 228, or 0xE4...it is an 'a' with two dots).

Benjamin Riefenstahl wrote:
>         chcp 1252

Ok, after some private exchange with Dan Herron
<herron@informatik.uni-hamburg.de> I caved in and actually tested these
things instead of just shooting from the hip ;-). Note that all that
follows is only tested with b18 (good enough for my occasional tests
until now).

Firstly, in b18 bash needs the complete filename for CHCP, so it's
actually "chcp.com 1252".

Secondly, bash needs some additional configuration in ~/.inputrc (copied
from my Linux box):

>>>>>>>>>>>
set convert-meta Off
set output-meta On
<<<<<<<<<<<

Thirdly and lastly, for ls to show 8-bit chars correctly, the "-N" (AKA
"--literal") option is needed, so

  ls -N

does the job.


so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

Hi everybody,


> Henrik Johansson wrote:
> > There is a couple of problems, however.  When I write (in bash)
> >         ls //c/tmp/l*.txt
> > the response is
> >         //c/tmp/l?smig.txt
> > even though the real filename is "läsmig.txt" (the second character in
> > the filename has the code 228, or 0xE4...it is an 'a' with two dots).

Benjamin Riefenstahl wrote:
>         chcp 1252

Ok, after some private exchange with Dan Herron
<herron@informatik.uni-hamburg.de> I caved in and actually tested these
things instead of just shooting from the hip ;-). Note that all that
follows is only tested with b18 (good enough for my occasional tests
until now).

Firstly, in b18 bash needs the complete filename for CHCP, so it's
actually "chcp.com 1252".

Secondly, bash needs some additional configuration in ~/.inputrc (copied
from my Linux box):

>>>>>>>>>>>
set convert-meta Off
set output-meta On
<<<<<<<<<<<

Thirdly and lastly, for ls to show 8-bit chars correctly, the "-N" (AKA
"--literal") option is needed, so

  ls -N

does the job.


so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Hi Henrik,

Henrik Johansson wrote:
> There is a couple of problems, however.  When I write (in bash)
>         ls //c/tmp/l*.txt
> the response is
>         //c/tmp/l?smig.txt
> even though the real filename is "läsmig.txt" (the second character in
> the filename has the code 228, or 0xE4...it is an 'a' with two dots).

Try the command

	chcp 1252

Background: Consoles in Win/32 still use the so-called "OEM" character
set encoding for display instead of the so-called "ANSI" encoding used
in GUI apps and for the file system. The CHCP command (CHange CodePage)
switches between the various installed codepages for consoles. 1252 is
the codepage usually used by GUI apps in western versions of Windows, so
doing "CHCP 1252" makes the standard GUI codepage and the codepage of
the console the same. This eliminates conversion errors which are most
probably the root of your problem.

so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

"Accented" characters

[Henrik Johansson]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

I recently installed cygwin release 20.1, and almost everything works
just great!

There is a couple of problems, however.  When I write (in bash)
	ls //c/tmp/l*.txt
the response is
	//c/tmp/l?smig.txt
even though the real filename is "läsmig.txt" (the second character in
the filename has the code 228, or 0xE4...it is an 'a' with two dots).

The second (probably related) problem is: a file contains a list of
filenames on separate lines, and I have a shellscript that reads the
list file line by line, and works on the files one by one.  When it
sees the line
	//c/tmp/läsmig.txt
and sets the variable F to this value, an
	ls "$F"
results in the following error:
	ls: //c/tmp/lSsmig.txt: No such file or directory

Strange, isn't it?

I have done the following at the bash prompt, but nothing is changed:
	set meta-flag On
	set convert-meta Off
	set output-meta On

The FAQ and other information on your web site didn't mention this, so
I thought it was best to send you a letter about it.

Best regards,

/hj

--
Name: Henrik Johansson, email:  Henrik.Johansson@Nexus.SE,
Phone: +46 18 171811, Fax: +46 18 696516,
Address: Technology Nexus AB, Box 857,
S - 751 08 Uppsala, Sweden

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

Benjamin Riefenstahl wrote:

> Hi everybody,
>
> > Henrik Johansson wrote:
> > > There is a couple of problems, however.  When I write (in bash)
> > >         ls //c/tmp/l*.txt
> > > the response is
> > >         //c/tmp/l?smig.txt
> > > even though the real filename is "läsmig.txt" (the second character in
> > > the filename has the code 228, or 0xE4...it is an 'a' with two dots).
>
> Benjamin Riefenstahl wrote:
> >         chcp 1252
>
> Ok, after some private exchange with Dan Herron
> <herron@informatik.uni-hamburg.de> I caved in and actually tested these
> things instead of just shooting from the hip ;-). Note that all that
> follows is only tested with b18 (good enough for my occasional tests
> until now).
>
> Firstly, in b18 bash needs the complete filename for CHCP, so it's
> actually "chcp.com 1252".

When I read that I was delighted I would be able to have proper accents in my
Bash/Dos window.
Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
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.


> Secondly, bash needs some additional configuration in ~/.inputrc (copied
> from my Linux box):
>
> >>>>>>>>>>>
> set convert-meta Off
> set output-meta On
> <<<<<<<<<<<
>
> Thirdly and lastly, for ls to show 8-bit chars correctly, the "-N" (AKA
> "--literal") option is needed, so
>
>   ls -N
>
> does the job.
>
> so long, benny
> ======================================
> Benjamin Riefenstahl (benny@crocodial.de)
> Crocodial Communications EntwicklungsGmbH
> Ruhrstr. 61, D-22761 Hamburg, Germany

--
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 cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

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 my
> Bash/Dos window.
> Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
> 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.

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.

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.


so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]

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 my
> > Bash/Dos window.
> > Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
> > 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
chcp.
I tried 851 at random and it told me the page was not prepared for
windows.
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
far.

> 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.

Regards,
Al.

--
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 cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]

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 my
> > Bash/Dos window.
> > Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
> > 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
chcp.
I tried 851 at random and it told me the page was not prepared for
windows.
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
far.

> 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.

Regards,
Al.

--
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 cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Benjamin Riefenstahl]

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 my
> Bash/Dos window.
> Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
> 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.

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.

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.


so long, benny
======================================
Benjamin Riefenstahl (benny@crocodial.de)
Crocodial Communications EntwicklungsGmbH
Ruhrstr. 61, D-22761 Hamburg, Germany

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

Benjamin Riefenstahl wrote:

> Hi everybody,
>
> > Henrik Johansson wrote:
> > > There is a couple of problems, however.  When I write (in bash)
> > >         ls //c/tmp/l*.txt
> > > the response is
> > >         //c/tmp/l?smig.txt
> > > even though the real filename is "läsmig.txt" (the second character in
> > > the filename has the code 228, or 0xE4...it is an 'a' with two dots).
>
> Benjamin Riefenstahl wrote:
> >         chcp 1252
>
> Ok, after some private exchange with Dan Herron
> <herron@informatik.uni-hamburg.de> I caved in and actually tested these
> things instead of just shooting from the hip ;-). Note that all that
> follows is only tested with b18 (good enough for my occasional tests
> until now).
>
> Firstly, in b18 bash needs the complete filename for CHCP, so it's
> actually "chcp.com 1252".

When I read that I was delighted I would be able to have proper accents in my
Bash/Dos window.
Pity is I don't seem to have chcp.com at all at all (yes I did a comprehensive
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.


> Secondly, bash needs some additional configuration in ~/.inputrc (copied
> from my Linux box):
>
> >>>>>>>>>>>
> set convert-meta Off
> set output-meta On
> <<<<<<<<<<<
>
> Thirdly and lastly, for ls to show 8-bit chars correctly, the "-N" (AKA
> "--literal") option is needed, so
>
>   ls -N
>
> does the job.
>
> so long, benny
> ======================================
> Benjamin Riefenstahl (benny@crocodial.de)
> Crocodial Communications EntwicklungsGmbH
> Ruhrstr. 61, D-22761 Hamburg, Germany

--
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 cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3682 bytes --]

Hi All,


[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
properly in
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
to
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
<snip>
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

to a
tutorial ?

Best regards,
Alain.


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
my
> > > Bash/Dos window.
> > > Pity is I don't seem to have chcp.com at all at all (yes I did a
comprehensive
> > > 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
> chcp.
> I tried 851 at random and it told me the page was not prepared for
> windows.
> 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
> far.
>
> > 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.
>
> Regards,
> Al.
>
> --
> 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 cygwin-unsubscribe@sourceware.cygnus.com

Re: "Accented" characters

[Alain CULOS]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3682 bytes --]

Hi All,


[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
properly in
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
to
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
<snip>
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

to a
tutorial ?

Best regards,
Alain.


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
my
> > > Bash/Dos window.
> > > Pity is I don't seem to have chcp.com at all at all (yes I did a
comprehensive
> > > 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
> chcp.
> I tried 851 at random and it told me the page was not prepared for
> windows.
> 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
> far.
>
> > 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.
>
> Regards,
> Al.
>
> --
> 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 cygwin-unsubscribe@sourceware.cygnus.com