FrontPage XP/2002 - Replaces &#8250 with Character instead?

I am using the right-pointing angle quotation mark (Double - ?, and Single - ?). In HTML code I am using ? for the single and ? for the double but FrontPage keep putting it as text (i.e. the symbol) in HTML and it'll look foine for awhile but then it starts to look funky.
e.g. &#187 becomes » (Should stay as &#187 in HTML but show up in web browser as ?). I have the same problem with &#171, &#8250 and &copy.
:bawl

I am not using a foreign language, just English.

I do have "Preserve Existing HTML" checked but it still takes the &#number and changes it to the character instead of the code and then later saves mess the symbol up!

Is there anything I can do to stop FrontPage from doing this?
:help

Hi Cos.

I tried this in both FrontPage 2000 and XP Pro...the characters held for me through saves, page changes, close and reopen, etc.

I'm curious as to whether you have style sheet or some other code/formatting that would be interfering with your chosen character set?

Scott

Addendum:

Here is an interesting bit that I found in the Newsgroups on a similar issue:
(I did note that you said you have preserved html)

Quote:

---

From FP 2002 Help:

Change the page-encoding language for saving or loading a page
By default, Microsoft FrontPage sets the encoding of pages based on your
keyboard language when you first type on a page, or uses the web site's
default encoding to determine in what character set to save and load
pages. If no site is open, FrontPage uses the default encoding specified
for your computer. However, you can specify a different encoding for
individual pages.

About saving pages

The HTML encoding option lets you specify which HTML encoding FrontPage
should use to save a page. For example, if characters on your page are
not recognized by the default encoding, these unrecognized characters
are saved by embedding additional information in the page's HTML code,
thereby increasing the size of the file.

While a few characters might not pose a problem, you probably don't want
an entire page of characters saved this way, so you should specify the
correct encoding for the page. For example, if the default page encoding
for the web site is US/Western European but the page is written in
Greek characters, you should set the encoding for saving pages to Greek
or Multilingual.

When you save the page, the HTML encoding you specify is included in the
page's HTML code, telling Web browsers how to read the text in the page.

About reloading pages

If a page's HTML encoding is not specified, (for example, a page created
in NotePad), FrontPage must guess the page's encoding when it loads the
page. If FrontPage guesses incorrectly, the page will not be displayed
correctly. You can specify the correct encoding to use when the page is
reloaded.

Warning If the current page is being displayed incorrectly, you might
corrupt the contents of the page by saving the page over the original.

To set a pages HTML encoding, use the following procedure.

In Page view, right-click the page, click Page Properties on the
shortcut menu, and then click the Language tab.
Under HTML Encoding, do the following:
In the Save the document as box, select the character set in which to
save the current page.
In the Reload the current document as box, select the character set in
which to load the current page, if the current page is not displaying
text correctly.

---

and

Quote:

---

In Page view, right-click the page, click Page Properties on the
shortcut menu, and then click the Language tab.
Under HTML Encoding, do the following:
In the Save the document as box, select the character set in which to
save the current page.
In the Reload the current document as box, select the character set in
which to load the current page, if the current page is not displaying
text correctly.

---

I hope this is of some help.

Scott

Quote:

---

Originally Posted by Scott

I'm curious as to whether you have style sheet or some other code/formatting that would be interfering with your chosen character set?

---

I am using CSS. I didn't create the website, it's a template I found from a website. I am brand new to FrontPage and a newbie at HTML so I may be to blame here!!.

Quote:

---

Originally Posted by Scott

Here is an interesting bit that I found in the Newsgroups on a similar issue:
(I did note that you said you have preserved html)

---

Thank you! I will try that out later tonight or tomorrow night!
:)

Quote:

---

Originally Posted by Scott

I hope this is of some help.

---

Me, too!
:giggle

Seriously, I really appreciate it anytime someone takes the time to help me out!

THANKS, Scott!

No problem, really; that's why we're here :)

If this info doesn't do anything toward correcting the problem, then we move on - I am sure that we can narrow it down to something that can be controlled.
In the meantime I will see if there is anything else more specific on the subject (I am always in the Newgroups looking over Frontpage and Corel Suite info lately so it isn't a problem to extend the search a bit).

Scott

Quote:

---

In Page view, right-click the page, click Page Properties on the
shortcut menu, and then click the Language tab.
Under HTML Encoding, do the following:
In the Save the document as box, select the character set in which to
save the current page.
In the Reload the current document as box, select the character set in
which to load the current page, if the current page is not displaying
text correctly.

---

Under Page language - Mark current document as I had <None> there. Changed that to English (United States).

Under HTML encoding, I had;
Save this docoment as: US/Western European
Reload the current document: <Automatic Encoding>

So, I changed it to
Save this docoment as: US/Western European
Reload the current document: US/Western European

Guess I wasn't using English after all.
:blush

Tomorrow, after I've had time to work on my website I'll let you know how it goes!

Thanks!

Cos,

Sounds like we're on the correct path at least. Cool!
I did note this one for myself:

Quote:

---

If a page's HTML encoding is not specified, (for example, a page created
in NotePad), FrontPage must guess the page's encoding when it loads the
page. If FrontPage guesses incorrectly, the page will not be displayed
correctly.

---

I am guilty of taking code from both Notepad and MS Script Editor and throwing it into FrontPage...it has ended up causing me problems and now I know why so this thread is a payoff for me as well! Thanks for asking the question!

Hope the testing goes well :)

Scott

Scott,

Well, so far so good. Had to change those setting on every page but haven't had much time to work on anything but as far as I can tell, it seems to work.
:thumb

Still not sure that the difference is between these two. It seems to reset to <Automatic Encoding> sometimes. Gotta go read up on FrontPage!
Reload the current document: <Automatic Encoding>
Reload the current document: US/Western European
:dunno

Hi Cosmos.

Have been away the last few days so I am only catching up on things now.
I am glad that this is working (is a shame that you had to set it up per-page though). :)

I am not sure what the Automatic Encoding entails but I will look to see how it differs from default and US/West-Euro.

Scott

Use this instead and you won't have to worry about changing those settings you've been messing with.

HTML Code:

---

»

---

That's if I'm understanding you correctly.

HTH, Thanks.