Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 830982 - Last Review: January 6, 2006 - Revision: 2.6
You receive WYSIWYG errors when you use XSLT style sheets that contain the XSL:ELEMENT element in FrontPage 2003
In Microsoft Office FrontPage 2003, when you develop a Web
page by using custom Extensible Style Sheet Language Transformations (XSLT)
style sheets, you may experience WYSIWYG (what you see is what you get) errors
in Design view in FrontPage 2003. When you try to view the page in Design view,
nothing appears, but if you preview the Web page in a Web browser, you can
successfully view the page.
This problem occurs because of problems that involve
implicit paragraph (<p>) tags in the parser when you use code that
contains the XSL:ELEMENT element. In certain cases, the XSL:ELEMENT element may
cause the XSLT parser to read the content as being mis-nested and is therefore
understood not to be valid. This will result in WYSIWYG errors in Design view
in FrontPage 2003.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this article.
WYSIWYG is a display method that shows documents and
graphical characters on the screen as they appear when they are printed.
WYSIWYG tries to duplicate print output as closely as
possible.
For additional information about XSLT, click the
following article number to view the article in the Microsoft Knowledge Base:
313997Â
(http://kbalertz.com/Feedback.aspx?kbNumber=313997/
)
INFO: Roadmap for Executing XSLT Transformations in .NET Applications
APPLIES TO
- Microsoft Office FrontPage 2003
- Microsoft Office SharePoint Portal Server 2003
- Microsoft Windows SharePoint Services 2.0
| kbprb kbweb kbxml kbnofix KB830982 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate