E-mail List Archives
Thread: Re: Changing Default Template in FrontPage
Number of posts in this thread: 2 (In chronological order)
From: Terence de Giere
Date: Fri, Jan 31 2003 1:43PM
Subject: Re: Changing Default Template in FrontPage
No previous message | Next message →
The document type declaration in the message to the forum is OK. Parts
of a document type declaration *are* case sensitive. A good way to test
is to use the W3C or WDG SGML parsers. Upload your test template to one
of these sites. If the doctype has been corrupted you should get an
error message something like:
"Error: invalid formal public identifier" and/or "invalid public text class"
Several options for checking a Web page such as file upload, URL, etc.,
are available. The character set for the Web page should be specified in
the page. FrontPage will default to using the Windows character set,
rather than an ISO character set, such as ISO-8859-1, which is platform
independent. For example, insert <META HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"> inside the HEAD element in the
template.
URLs for the validators:
W3C Validator: http://validator.w3.org/
WDG Validator: http://www.htmlhelp.com/tools/validator/
The other thing that will happen using the validators is your HTML will
be checked to see if it matches the version of HTML to which the doctype
declaration refers. Many HTML editors will insert a doctype declaration,
but will not produce HTML to conform to it, so this is the other part of
conforming to public specifications that needs to be attended to.
Accessibility testing software currently will check for a doctype
declaration, but will not check the HTML itself, so it is necessary to
run this test independently using one of the tools listed above.
Terence de Giere
= EMAIL ADDRESS REMOVED =
----------------------------
John E. Brandt wrote:
I followed directions (found in the Webaim FrontPage Tutorial) to update the
normal.tem file, which sets the default "new_page.htm" that FP uses to
create a default template, to includes correct !DOCTYPE information and
Native Language. The modifications were done in Notepad and were achieved
using the
appropriate upper case and lower case. However, when the new page renders,
it has all of information but has mysteriously changes the words DOCTYPE
into lower case:
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en-us"> ....
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: jeb
Date: Sat, Feb 01 2003 10:06AM
Subject: RE: Changing Default Template in FrontPage
← Previous message | No next message
Thank you Terence for your thoughtful response. I will do as you suggest.
The "charset" issue has also plagued me. I know that validators have spotted
and commented on this. I was concerned that once changed, FrontPage would
not recognize it, or worse, change it back to the Windows-preferred
character set. It has been one of the most annoying characteristics of
FrontPage - and many have complained. I believe that version 2002 has a
switch to prevent FP from changing the code.
Thanks again.
jeb
-----Original Message-----
From: Terence de Giere [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Friday, January 31, 2003 3:32 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: Changing Default Template in FrontPage
The document type declaration in the message to the forum is OK. Parts
of a document type declaration *are* case sensitive. A good way to test
is to use the W3C or WDG SGML parsers. Upload your test template to one
of these sites. If the doctype has been corrupted you should get an
error message something like:
"Error: invalid formal public identifier" and/or "invalid public text class"
Several options for checking a Web page such as file upload, URL, etc.,
are available. The character set for the Web page should be specified in
the page. FrontPage will default to using the Windows character set,
rather than an ISO character set, such as ISO-8859-1, which is platform
independent. For example, insert <META HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"> inside the HEAD element in the
template.
URLs for the validators:
W3C Validator: http://validator.w3.org/
WDG Validator: http://www.htmlhelp.com/tools/validator/
The other thing that will happen using the validators is your HTML will
be checked to see if it matches the version of HTML to which the doctype
declaration refers. Many HTML editors will insert a doctype declaration,
but will not produce HTML to conform to it, so this is the other part of
conforming to public specifications that needs to be attended to.
Accessibility testing software currently will check for a doctype
declaration, but will not check the HTML itself, so it is necessary to
run this test independently using one of the tools listed above.
Terence de Giere
= EMAIL ADDRESS REMOVED =
----------------------------
John E. Brandt wrote:
I followed directions (found in the Webaim FrontPage Tutorial) to update the
normal.tem file, which sets the default "new_page.htm" that FP uses to
create a default template, to includes correct !DOCTYPE information and
Native Language. The modifications were done in Notepad and were achieved
using the
appropriate upper case and lower case. However, when the new page renders,
it has all of information but has mysteriously changes the words DOCTYPE
into lower case:
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en-us"> ....
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/