Weird Character Issue

Asked By Eddie Kasper

19-Nov-09 04:12 PM

I am using a shopping cart called Product Cart which uses .asp. Each time I
open a asp page for the very first time and then save it, these weird
characters starts showing up in various places.

One example is a site that has been up for a few years and never had any
kind of weird character issue. Today, I open a asp file to edit a class name
in the html and then I saved it. Thereafter, the character issues started
appearing.

The folks at ProductCart is baffled by this and thinks it may be an issue
with Expression Web.

Is there something in Expression Web that would cause this or at least a
setting that will resolve this?

Thanks.

What weird characters? and where?

Ronx replied to Eddie Kasper

19-Nov-09 04:21 PM

Reply

What weird characters? and where?  A link to a page with this fault will
help to find a solution.

--
Ron Symonds
Microsoft MVP (Expression Web)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

http://www.zozomusic.com/musicstore/pc/Kustom-Profile1RBT-Portable-PA-130p456.

Eddie Kasper replied to Ronx

19-Nov-09 05:41 PM

Reply

http://www.zozomusic.com/musicstore/pc/Kustom-Profile1RBT-Portable-PA-130p456.htm

It goes away after I added the UTF-8 which is fine but I wonder why the
weird character do not occur until I use Expression to save a file?

I have removed the UTF-8 so you can see the characters. Just review the
content and you will see several of them.

Thanks.

Eddie Kasper wrote:xWeb uses UTF-8 encoding by default.

Christoph Schneegans replied to Eddie Kasper

19-Nov-09 08:17 PM

Reply

xWeb uses UTF-8 encoding by default. What you did was to remove the
UTF-8 encoding *declaration*, while the file itself is still UTF-8
encoded. A browser now has to guess the file's encoding because no
encoding declaration is available. Some browsers might choose
Windows-1252 to decode the file, and when an UTF-8 encoded file is
decoded using Windows-1252, every occurence of the U+00A0 character
(" ") is displayed as "?? ".

Thus, you should not only restore the UTF-8 encoding declaration,
but also get rid of these U+00A0 characters in your document. You
probably mistook them for ordinary spaces because they are
indistinguishable in both Code View and Design View. Choose

--

Thanks for the detailed answer. It makes now.

Eddie Kasper replied to Christoph Schneegans

19-Nov-09 09:43 PM

Reply

Thanks for the detailed answer. It makes now.

To be clear, I assume that the character encoding tag should the first line
within the <head> tag to avoid issues.

Thanks.

Sorry for the other post, I miss a few words.

Eddie Kasper replied to Christoph Schneegans

19-Nov-09 09:55 PM

Reply

Sorry for the other post, I miss a few words.  Here it is again:

Thanks for the detailed answer. It makes sense now.

To be clear, I assume that the character encoding tag should be the first
line
within the <head> tag to avoid issues.

Thanks.

Eddie Kasper wrote:Exactly, the "meta" encoding declaration should appear as

Christoph Schneegans replied to Eddie Kasper

20-Nov-09 03:51 AM

Reply

Exactly, the "meta" encoding declaration should appear as early as
possible, and the first valid location is the first element after
the opening <head> tag.

--