Lyle
November 2nd, 2007, 15:32
There are many FP users like myself who have inadvertently and unknowingly created a nightmare for themselves - with seemingly no real help available.
We finally discovered something beyond the heretofore touted fixes.
Indeed - the Site Settings - Default Page Encoding - should be set to Unicode UTF and not US... and if using FP2002 or earlier the MS Office Update may be needed - although I question if this really makes or breaks the real final issue.
We recently discovered this:
If < span en-us > and the closure </span> already exist on a page background, paragraph, or table setting, etc., FrontPage will continue in suit to add the dreaded < span en-us> tags when anything whatsoever is changed in the associated area.
If not tags pre-exist - then FP will not add more. It's 'crazy making' because one can be at one part of a page and get additional tags with any changes made - then move down a paragraph or two - and then NOT get them.
It takes a REAL close look at the pre-existings HTML to discern and remove the dreaded tags to get FrontPage to stop the seemingly endless nightmare.
The good news - ha! They don't really 'hurt' the display on most any browser - it's only that they can easily grow to a point that they make making sense of your HTML near impossible.
Back to removing the 'ten thousand' things at this end. Arggggg!
We finally discovered something beyond the heretofore touted fixes.
Indeed - the Site Settings - Default Page Encoding - should be set to Unicode UTF and not US... and if using FP2002 or earlier the MS Office Update may be needed - although I question if this really makes or breaks the real final issue.
We recently discovered this:
If < span en-us > and the closure </span> already exist on a page background, paragraph, or table setting, etc., FrontPage will continue in suit to add the dreaded < span en-us> tags when anything whatsoever is changed in the associated area.
If not tags pre-exist - then FP will not add more. It's 'crazy making' because one can be at one part of a page and get additional tags with any changes made - then move down a paragraph or two - and then NOT get them.
It takes a REAL close look at the pre-existings HTML to discern and remove the dreaded tags to get FrontPage to stop the seemingly endless nightmare.
The good news - ha! They don't really 'hurt' the display on most any browser - it's only that they can easily grow to a point that they make making sense of your HTML near impossible.
Back to removing the 'ten thousand' things at this end. Arggggg!