Corrupted international characters

[kalarasho]

I'm using international characters on my .aspx files. In order to publish my
site to the webserver I'm using frontpage - to allow me to publish only
changes (I have 100's of files). However the international characters on the
server side are being corrupted. If I transfer the same files using a
standard FTP client - everything is OK. I've tried with FP 2003 and with MS
Expression Web.

 

[Evertjan.]

=?Utf-8?B?a2FsYXJhc2hv?= wrote on 02 okt 2007 in
microsoft.public.inetserver.asp.general:

I'm using international characters on my .aspx files. In order to
publish my site to the webserver I'm using frontpage - to allow me to
publish only changes (I have 100's of files). However the
international characters on the server side are being corrupted. If I
transfer the same files using a standard FTP client - everything is
OK. I've tried with FP 2003 and with MS Expression Web.

1 This is a classic asp group.
Dotnet questions should be asked in
<microsoft.public.dotnet.framework.aspnet>

2 never use Frontpage if you are not an expert in that.
and if you are an expert in that, you als do not need it.

 

[kalarasho]

OK I've traced the problem to expression web. I am not sure it is related to
..NET at all, since it probably occurs in other ASCII files as well (not just
..aspx). The problem is that expression web corrupts the international
characters in the FTP process. Transferring the same files with FP 2003 works
fine. Is there any workaround (other then downgrading to FP 2003)?

 

[Evertjan.]

=?Utf-8?B?a2FsYXJhc2hv?= wrote on 10 okt 2007 in
microsoft.public.inetserver.asp.general:
[Please do not toppost on usenet]
[please do not quote signatures on usenet]

OK I've traced the problem to expression web. I am not sure it is
related to .NET at all, since it probably occurs in other ASCII files
as well (not just .aspx). The problem is that expression web corrupts
the international characters in the FTP process. Transferring the same
files with FP 2003 works fine. Is there any workaround (other then
downgrading to FP 2003)?

So you are not even interested in my two points above.
What does your "OK" mean?

What is an "expression web"?

If it is happening in both .aspx and .txt,
why do you think it is .asp related?

If it is not asp related, please ask elsewhere.