Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Weird Character Issue

0 views
Skip to first unread message

Eddie Kasper

unread,
Nov 19, 2009, 4:12:44 PM11/19/09
to
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.


Ronx

unread,
Nov 19, 2009, 4:21:17 PM11/19/09
to
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.

"Eddie Kasper" <ed...@sbcglobal.net> wrote in message
news:ez6QM0V...@TK2MSFTNGP06.phx.gbl...

Eddie Kasper

unread,
Nov 19, 2009, 5:41:48 PM11/19/09
to
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.

"Ronx" <ron...@hotmail.com> wrote in message
news:Ouuw94Va...@TK2MSFTNGP02.phx.gbl...

Christoph Schneegans

unread,
Nov 19, 2009, 8:17:36 PM11/19/09
to
Eddie Kasper wrote:

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

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
("&nbsp;") 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
"Reformat HTML" in Code View; this will replace these characters by
"&nbsp;" entity references, which you can then delete.

--
<http://schneegans.de/sv/> · XML Schema Validator

Eddie Kasper

unread,
Nov 19, 2009, 9:43:53 PM11/19/09
to
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.

"Christoph Schneegans" <Chri...@Schneegans.de> wrote in message
news:7mm91gF...@mid.individual.net...


> Eddie Kasper wrote:
>
>> 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?
>
> 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

> ("&nbsp;") is displayed as "� ".

Eddie Kasper

unread,
Nov 19, 2009, 9:55:53 PM11/19/09
to
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.

"Christoph Schneegans" <Chri...@Schneegans.de> wrote in message
news:7mm91gF...@mid.individual.net...

> Eddie Kasper wrote:
>
>> 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?
>
> 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

> ("&nbsp;") is displayed as "� ".

Christoph Schneegans

unread,
Nov 20, 2009, 3:51:47 AM11/20/09
to
Eddie Kasper wrote:

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

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.

--
<http://schneegans.de/expression-web/codierung/> � Unicode in xWeb

0 new messages