Problems migrating from FrontPage to SharePoint Designer HTML enco

  • Thread starter Thread starter SGK
  • Start date Start date
S

SGK

I have been using FrontPage for many years to manage dozens of dynamic
websites. I recently installed SharePoint Designer, now that it is a free
download. The software looks and feels like FrontPage, with some nice new
added features. However, I am experiencing a problem that is causing
SharePoint to be unusable.

Whenever I open a page that was previously created/saved in FrontPage,
SharePoint Designer is changing the encoding on the page to utf-8 from
windows-1252. This is causing a bunch of "junk" and strange characters to
appear on the screen. I am aware of the differences between windows-1252 and
utf-8 the cause behind these strange characters. It is further complicated by
the fact that these sites make heavy use of include files, and you end up
with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
page will be encoded in utf-8 and the include files will still be encoded in
windows-1252), which causes even more issues.

Some of these sites have thousands of pages, with dozens of include files
(include files including other include files, etc.) so changing the entire
site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
there are SQL databases with literally millions of records encoded as
windows-1252.

Long story short... I am wondering if there is any way in SharePoint
Designer to change the "default" encoding from utf-8 to windows-1252?
Understand that many of these include files are simply ASP code and do not
have a header on the page, so am unable to specify windows-1252 as a content
type in the page header. I have searched through just about every menu on the
software and can not find anything.

Thank you in advance for any assistance.
 
SPD suffers from the same Byte Order Bit mark Bug that Expression Web 1 suffered from since they shared similar code
(Expression Web 2 has corrected this, but apparently SPD has not)

See it these tips for EW1 help
http://by-expression.com/content/bom.aspx
- check the macro link to remove the BOM at
http://groups.google.com/group/micr...webdesigner/msg/b3d5c9a3e477f729?dmode=source
- and the new page fix at
http://www.95isalive.com/expression/index.html
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I have been using FrontPage for many years to manage dozens of dynamic
| websites. I recently installed SharePoint Designer, now that it is a free
| download. The software looks and feels like FrontPage, with some nice new
| added features. However, I am experiencing a problem that is causing
| SharePoint to be unusable.
|
| Whenever I open a page that was previously created/saved in FrontPage,
| SharePoint Designer is changing the encoding on the page to utf-8 from
| windows-1252. This is causing a bunch of "junk" and strange characters to
| appear on the screen. I am aware of the differences between windows-1252 and
| utf-8 the cause behind these strange characters. It is further complicated by
| the fact that these sites make heavy use of include files, and you end up
| with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
| page will be encoded in utf-8 and the include files will still be encoded in
| windows-1252), which causes even more issues.
|
| Some of these sites have thousands of pages, with dozens of include files
| (include files including other include files, etc.) so changing the entire
| site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
| there are SQL databases with literally millions of records encoded as
| windows-1252.
|
| Long story short... I am wondering if there is any way in SharePoint
| Designer to change the "default" encoding from utf-8 to windows-1252?
| Understand that many of these include files are simply ASP code and do not
| have a header on the page, so am unable to specify windows-1252 as a content
| type in the page header. I have searched through just about every menu on the
| software and can not find anything.
|
| Thank you in advance for any assistance.
 
This seems to make sense, what you are describing. Have there been any recent
updates to SharePoint Designer which may have resolved this issue?

Stefan B Rusynko said:
SPD suffers from the same Byte Order Bit mark Bug that Expression Web 1 suffered from since they shared similar code
(Expression Web 2 has corrected this, but apparently SPD has not)

See it these tips for EW1 help
http://by-expression.com/content/bom.aspx
- check the macro link to remove the BOM at
http://groups.google.com/group/micr...webdesigner/msg/b3d5c9a3e477f729?dmode=source
- and the new page fix at
http://www.95isalive.com/expression/index.html
--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|I have been using FrontPage for many years to manage dozens of dynamic
| websites. I recently installed SharePoint Designer, now that it is a free
| download. The software looks and feels like FrontPage, with some nice new
| added features. However, I am experiencing a problem that is causing
| SharePoint to be unusable.
|
| Whenever I open a page that was previously created/saved in FrontPage,
| SharePoint Designer is changing the encoding on the page to utf-8 from
| windows-1252. This is causing a bunch of "junk" and strange characters to
| appear on the screen. I am aware of the differences between windows-1252 and
| utf-8 the cause behind these strange characters. It is further complicated by
| the fact that these sites make heavy use of include files, and you end up
| with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
| page will be encoded in utf-8 and the include files will still be encoded in
| windows-1252), which causes even more issues.
|
| Some of these sites have thousands of pages, with dozens of include files
| (include files including other include files, etc.) so changing the entire
| site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
| there are SQL databases with literally millions of records encoded as
| windows-1252.
|
| Long story short... I am wondering if there is any way in SharePoint
| Designer to change the "default" encoding from utf-8 to windows-1252?
| Understand that many of these include files are simply ASP code and do not
| have a header on the page, so am unable to specify windows-1252 as a content
| type in the page header. I have searched through just about every menu on the
| software and can not find anything.
|
| Thank you in advance for any assistance.
Click to expand...
 
TBMK - No SPD has not been updated

--




| This seems to make sense, what you are describing. Have there been any recent
| updates to SharePoint Designer which may have resolved this issue?
|
| "Stefan B Rusynko" wrote:
|
| > SPD suffers from the same Byte Order Bit mark Bug that Expression Web 1 suffered from since they shared similar code
| > (Expression Web 2 has corrected this, but apparently SPD has not)
| >
| > See it these tips for EW1 help
| > http://by-expression.com/content/bom.aspx
| > - check the macro link to remove the BOM at
| > http://groups.google.com/group/micr...webdesigner/msg/b3d5c9a3e477f729?dmode=source
| > - and the new page fix at
| > http://www.95isalive.com/expression/index.html
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > _____________________________________________
| >
| >
| > |I have been using FrontPage for many years to manage dozens of dynamic
| > | websites. I recently installed SharePoint Designer, now that it is a free
| > | download. The software looks and feels like FrontPage, with some nice new
| > | added features. However, I am experiencing a problem that is causing
| > | SharePoint to be unusable.
| > |
| > | Whenever I open a page that was previously created/saved in FrontPage,
| > | SharePoint Designer is changing the encoding on the page to utf-8 from
| > | windows-1252. This is causing a bunch of "junk" and strange characters to
| > | appear on the screen. I am aware of the differences between windows-1252 and
| > | utf-8 the cause behind these strange characters. It is further complicated by
| > | the fact that these sites make heavy use of include files, and you end up
| > | with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
| > | page will be encoded in utf-8 and the include files will still be encoded in
| > | windows-1252), which causes even more issues.
| > |
| > | Some of these sites have thousands of pages, with dozens of include files
| > | (include files including other include files, etc.) so changing the entire
| > | site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
| > | there are SQL databases with literally millions of records encoded as
| > | windows-1252.
| > |
| > | Long story short... I am wondering if there is any way in SharePoint
| > | Designer to change the "default" encoding from utf-8 to windows-1252?
| > | Understand that many of these include files are simply ASP code and do not
| > | have a header on the page, so am unable to specify windows-1252 as a content
| > | type in the page header. I have searched through just about every menu on the
| > | software and can not find anything.
| > |
| > | Thank you in advance for any assistance.
| >
| >
| >
 
SGK said:
I have been using FrontPage for many years to manage dozens of dynamic
websites. I recently installed SharePoint Designer, now that it is a free
download. The software looks and feels like FrontPage, with some nice new
added features. However, I am experiencing a problem that is causing
SharePoint to be unusable.

Whenever I open a page that was previously created/saved in FrontPage,
SharePoint Designer is changing the encoding on the page to utf-8 from
windows-1252. This is causing a bunch of "junk" and strange characters to
appear on the screen. I am aware of the differences between windows-1252
and
utf-8 the cause behind these strange characters. It is further complicated
by
the fact that these sites make heavy use of include files, and you end up
with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
page will be encoded in utf-8 and the include files will still be encoded
in
windows-1252), which causes even more issues.

Some of these sites have thousands of pages, with dozens of include files
(include files including other include files, etc.) so changing the entire
site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
there are SQL databases with literally millions of records encoded as
windows-1252.

Long story short... I am wondering if there is any way in SharePoint
Designer to change the "default" encoding from utf-8 to windows-1252?
Understand that many of these include files are simply ASP code and do not
have a header on the page, so am unable to specify windows-1252 as a
content
type in the page header. I have searched through just about every menu on
the
software and can not find anything.

Thank you in advance for any assistance.
Click to expand...
 
See if this EW1 workaround helps
http://www.95isalive.com/expression/index.html
Or try editing all your ASP include files to add as the 1st line
<% Response.charset="ISO-8859-1" %>

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


|
| "SGK" <[email protected]> a écrit dans le message de
| | >I have been using FrontPage for many years to manage dozens of dynamic
| > websites. I recently installed SharePoint Designer, now that it is a free
| > download. The software looks and feels like FrontPage, with some nice new
| > added features. However, I am experiencing a problem that is causing
| > SharePoint to be unusable.
| >
| > Whenever I open a page that was previously created/saved in FrontPage,
| > SharePoint Designer is changing the encoding on the page to utf-8 from
| > windows-1252. This is causing a bunch of "junk" and strange characters to
| > appear on the screen. I am aware of the differences between windows-1252
| > and
| > utf-8 the cause behind these strange characters. It is further complicated
| > by
| > the fact that these sites make heavy use of include files, and you end up
| > with a "mix" of windows-1252 and utf-8 encoding on the page (i.e. the main
| > page will be encoded in utf-8 and the include files will still be encoded
| > in
| > windows-1252), which causes even more issues.
| >
| > Some of these sites have thousands of pages, with dozens of include files
| > (include files including other include files, etc.) so changing the entire
| > site from windows-1252 to utf-8 is simply not feasible at this time. Plus,
| > there are SQL databases with literally millions of records encoded as
| > windows-1252.
| >
| > Long story short... I am wondering if there is any way in SharePoint
| > Designer to change the "default" encoding from utf-8 to windows-1252?
| > Understand that many of these include files are simply ASP code and do not
| > have a header on the page, so am unable to specify windows-1252 as a
| > content
| > type in the page header. I have searched through just about every menu on
| > the
| > software and can not find anything.
| >
| > Thank you in advance for any assistance.
|
 
Back
Top