Turkish or Russian standard characters are not unicode. They are 8-bit. In
Turkish the first 7-bits (0-127) are the same as ANSI but characters
(128-255) are different.
So it is the same as french. And it works very well with french text. If it
doesn't with turkish or russian characters, then there is something I don't
understand. You should single step thru the component code and try to
understand what.
--
[EMAIL PROTECTED]
http://www.overbyte.be
----- Original Message -----
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Saturday, June 04, 2005 10:52 AM
Subject: Re: [twsocket] Folder names in THttpServer
Hello,
Thank you for your reply. Turkish or Russian standard characters are not
unicode. They are 8-bit. In Turkish the first 7-bits (0-127) are the same
as ANSI but characters (128-255) are different.
Best Regards,
SZ
----- Original Message -----
From: "Francois PIETTE" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Saturday, June 04, 2005 11:09 AM
Subject: Re: [twsocket] Folder names in THttpServer
The characters [EMAIL PROTECTED] turns out to be 80¤éÀô¹C?/A>. ATV
I have no experience with turkish, russian and other chatacter set.
What I can say is that I have no problem with accented characters used in
french.
Maybe a unicode or double byte character set issue ?
btw: FTP is defined as a 8 bit ascii protocol.
--
[EMAIL PROTECTED]
http://www.overbyte.be
----- Original Message -----
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Friday, May 27, 2005 1:31 PM
Subject: [twsocket] Folder names in THttpServer
Hello,
I have some reports and experience that there is a problem with non-ascii
characters in folder names--not with files. Here is the report I got:
The characters [EMAIL PROTECTED] turns out to be 80¤éÀô¹C?/A>. ATV
[EMAIL PROTECTED] turns out to be ATV ²Ä¤Q?/A>.
[EMAIL PROTECTED] turns out to be ·R.?/A>. And [EMAIL PROTECTED] turns out to be
´İ»Å?/A>
it doesn't seem to be a specific character..
Anyone have any idea why this happens? Is there an RFC that explains this
behavior and its cure?
Best Regards,
SubZero
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
