special characters

  • Thread starter Thread starter Jean Pierre Daviau
  • Start date Start date
J

Jean Pierre Daviau

echo 0>émétâ.txt | dir>out.txt | notepad out.txt

out.txt = 7 ,m,tf.txt

ON SCREEN
type out.txt = 7 émétâ.txt
=====================
cmd/U
echo 0>émétâ.txt | dir>out.txt | notepad out.txt

out.txt = 0 ,m,tf.txt

ON SCREEN
type out.txt = 0 émétâ.txt


--
Thanks for your attention.

Jean Pierre Daviau
--
Easyphp1.8 with Apache1.3.24
Server version: Apache/2.0.55
Server built: Oct 9 2005 19:16:56
DEVC++, borland 5.5
windows Xp
asus p4 s533/333/133
Intel(R) Celeron (R) CPU 2.00 GHz
Processor Radeon7000 0x5159 agp
http://www.jeanpierredaviau.com
 
Jean Pierre Daviau said:
echo 0>émétâ.txt | dir>out.txt | notepad out.txt

out.txt = 7 ,m,tf.txt

ON SCREEN
type out.txt = 7 émétâ.txt
=====================
cmd/U
echo 0>émétâ.txt | dir>out.txt | notepad out.txt

out.txt = 0 ,m,tf.txt

ON SCREEN
type out.txt = 0 émétâ.txt


--
Thanks for your attention.

Jean Pierre Daviau
--
Click to expand...

Well, I've been dealing with computers for 35 years now, and I haven't a
clue what this post is about.

Is it a question, a complaint, a report or what?

What are you trying to do?

The only thing that really stands out is the "echo 0>filename" part.

digit>filename in NT-DOS will try to redirect handle "digit" to the file. I
believe this may be the source of the problem - whatever the problem is, and
would recommend replacing the "echo 0>filename" with
filename echo 0
Click to expand...

As for the rest - no idea of what you are trying to do, whether the
file-contents is input or output or what the object of the exercise is.
 
I gess this is clearer ;-)
echo 0>émétâ.txt
Click to expand...
echo aaa>émétâ.txt creates the file émétâ.txt with aaa in it.
| dir>out.txt | notepad out.txt
Click to expand...
creates out.txt with 7 ,m,tf.txt in it if opened by notepad.

émétâ.txt opened by notepad reads as 7 ,m,tf.txt
if type out.txt
Click to expand...
on screen émétâ.txt reads as émétâ.txt but in out.txt opened
by notepad, or EditPlus or Word I read 7 ,m,tf.txt

Why cant I get émétâ.txt written in out.txt as émétâ.txt instead of 7
,m,tf.txt?

I tried with cmd /U with the same results

JPD
 
Jean Pierre Daviau said:
I gess this is clearer ;-)

echo aaa>émétâ.txt creates the file émétâ.txt with aaa in it.

creates out.txt with 7 ,m,tf.txt in it if opened by notepad.

émétâ.txt opened by notepad reads as 7 ,m,tf.txt

on screen émétâ.txt reads as émétâ.txt but in out.txt
opened by notepad, or EditPlus or Word I read 7 ,m,tf.txt

Why cant I get émétâ.txt written in out.txt as émétâ.txt instead of 7
,m,tf.txt?

I tried with cmd /U with the same results

JPD
Click to expand...

It probably has to do with the FONT you are using.

When displayed using COURIER or ARIAL, the display should be correct.
émétâ
for hex-bytes E9 6D E9 74 E2

When using LUCIDA, I get greek characters.

Any characters not in the range 20..7F are likely to show up differently
depending on font.
 
It probably has to do with the FONT you are using.
When displayed using COURIER or ARIAL, the display should be correct.
émétâ
for hex-bytes E9 6D E9 74 E2

When using LUCIDA, I get greek characters.

Any characters not in the range 20..7F are likely to show up differently
depending on font.
Click to expand...
No.

Samething with Courier, Times New Roman and Verdana.

If I type the characters directly in the file the text is OK
 
In microsoft.public.win2000.cmdprompt.admin Jean Pierre Daviau
wrote:
I gess this is clearer ;-)

echo aaa>émétâ.txt creates the file émétâ.txt with aaa
in it.

creates out.txt with 7 ,m,tf.txt in it if opened by notepad.

émétâ.txt opened by notepad reads as 7 ,m,tf.txt

on screen émétâ.txt reads as émétâ.txt but in
out.txt opened by notepad, or EditPlus or Word I read 7
,m,tf.txt

Why cant I get émétâ.txt written in out.txt as émétâ.txt
instead of 7 ,m,tf.txt?

I tried with cmd /U with the same results
Click to expand...

Codepage difference.
Thus different glyphs are used for a character between Windows 1252
(or whatever) in notepad vs. at the CMD prompt (possibly 437 or
850).
Open out.txt in EDIT.
 
it comes from de echo and copy con: commands

The following works:

cmd /U
echo émétâ>émétâ.txt

with notepad
émétâ


With type
® m ?® t ?ó


with EditPlus
I get strange characters wich dont prints in the email


With WordPad
émétâ
 
Codepage difference.
Thus different glyphs are used for a character between Windows 1252
(or whatever) in notepad vs. at the CMD prompt (possibly 437 or
850).
Open out.txt in EDIT.
Click to expand...

ÚmÚtÔt.txt
ÚmÚtÔt.txt

23/10/2006 08:59 0 émétâ.txt

-------------------------
EditPlus, Notepad
émétât.txt
émétât.txt

23/10/2006 08:59 0 ,m,tf.txt
 
If I make a batch like this.

---------- batch --------

@echo émétât.txt

cmd/U @echo émétât.txt
---------- batch --------------
both gives:

ÚmÚtÔt.txt



Is there a registry key that would set the codepage?
I found theese for mime:
[HKEY_CLASSES_ROOT\MIME\Database\Charset\DOS-874]
"Codepage"=dword:0000036a
"InternetEncoding"=dword:0000036a

[HKEY_CLASSES_ROOT\MIME\Database\Charset\DOS-720]
"Codepage"=dword:000004e8
"InternetEncoding"=dword:000002d0

[HKEY_CLASSES_ROOT\MIME\Database\Charset\DOS-862]
"Codepage"=dword:000004e7
"InternetEncoding"=dword:0000035e



JPD
 
In said:
If I make a batch like this.

---------- batch --------

@echo émétât.txt

cmd/U @echo émétât.txt
---------- batch --------------
both gives:

ÚmÚtÔt.txt
Click to expand...


Did you already change the font in notepad as suggested previously?
Get/use MS Linedraw.ttf

It actually seems from here that that is your primary or only problem
in this case. But codepage differences can and do present similar
problems.
 
Did you already change the font in notepad as suggested previously?
Click to expand...
I have tried many without success
Get/use MS Linedraw.ttf
Click to expand...

Ha ha! This one works.

I dont understand why notepad needs this font to display àéê etc correctly.
And why Times New Roman dont displays theese characters in notepad.

Thanks
 
It actually seems from here that that is your primary or only problem
in this case. But codepage differences can and do present similar
problems.
Click to expand...

As it seems I would have to use this font in word, etc to get the right
display. It is very limitative.
 
Jean Pierre Daviau said:
I have tried many without success


Ha ha! This one works.

I dont understand why notepad needs this font to display àéê etc
correctly. And why Times New Roman dont displays theese characters in
notepad.

Thanks
Click to expand...

Try running "Character Map"

Start > Programs > Accessories > System Tools > Character Map

This will show you what is displayed for each byte-code and codepage for
each installed font.
 
In microsoft.public.win2000.cmdprompt.admin Jean Pierre Daviau
wrote:
As it seems I would have to use this font in word, etc to get
the right display. It is very limitative.
Click to expand...

Right. You will probably have to generate Unicode output or
"convert" the Extended ASCII values in order to display in "most
Windows applications". Most of this problem is Windows, as other OSs
often exhibit no such problems.
 
Found on a French newsgroup
(Translated by google)

Traditional. Coding in a console is in OEM whereas in a window it is in
ANSI. Thus it is necessary you to publish your text according to your exit
(the majority of the text editors serious allow it) or to use notepad for
postings under Windows and edict for postings in mode comforts. Another
possibility is to convert your texts with scripts of JCB oem2ansi.vbs and
ansi2oem.vbs

http://www.bellamyjc.org/fr/vbsdownload.html#oem2ansi
http://www.bellamyjc.org/fr/vbsdownload.html#ansi2oem
 
In microsoft.public.win2000.cmdprompt.admin Jean Pierre Daviau
wrote:
Found on a French newsgroup
(Translated by google)

Traditional. Coding in a console is in OEM whereas in a window
it is in ANSI. Thus it is necessary you to publish your text
according to your exit (the majority of the text editors serious
allow it) or to use notepad for postings under Windows and edict
for postings in mode comforts. Another possibility is to convert
your texts with scripts of JCB oem2ansi.vbs and ansi2oem.vbs

http://www.bellamyjc.org/fr/vbsdownload.html#oem2ansi
http://www.bellamyjc.org/fr/vbsdownload.html#ansi2oem
Click to expand...

Thanks for the follow-up. Seems like your problem is resolvable, if
not pretty. :)
 
May be some enlighted guy will pass by with a more elegant registery
solution ? ;-)


JP
 
In microsoft.public.win2000.cmdprompt.admin Jean Pierre Daviau
wrote:
May be some enlighted guy will pass by with a more elegant
registery solution ? ;-)
Click to expand...

Possibly, but I doubt it. CMD uses conventional IBM-based
international character codepages whereas Windows uses a non-standard
Unicode codepage (Windows "1252" most often) and "ner the twain shall
meet". <G> And as we just saw how the font choosen can often show
the "correct" glyph for the given character code. The subject is
complex and often dificult to deal with.

It is easy to change the codepage in CMD (see CHCP and CP commands),
but that may or may not entirely resolve a difficulty. In some few
cases pasting data in the system clipboard as "OEM" might help.
 
Back
Top