|
Formatting
Formatting
Click to view graphic
Changing the font attributes of a Table Of Contents has no effectSource of the problemWhen you apply font formatting to a Table Of Contents component, the formatting appears in the Page view editor but not in Preview mode or when you view the page in a Web browser.FrontPage doesn't write the font information for the Table Of Contents to the page. The Table of Contents component uses only heading tags (such as H1, H2, or H3). FrontPage doesn't apply any other font or style formatting to the list.
How to fix itTo work around this behavior, use Cascading Style Sheets (CSS) to define the styles for the heading attributes. To do this, follow these steps:
Any styles you define using this procedure will apply to all hyperlinks and paragraphs with the heading size you specified.
Any styles you define at this point will apply to the entire Web page, and not just to the Table Of Contents component. This isn't a problem if, as is common, the Web page contains only the Table Of Contents. If, however, the page contains any other content, you might have to override the formatting you selected for the Table Of Contents.
More information The Table Of Contents component works by first listing all the links in a starting page that you specify when you configure the component. Many designers call these "level two" pages because they have links directly from the home page. Under each level two page, FrontPage lists all the hyperlinks from that page to a level three page. Under each level three page it lists all the hyperlinks from that page to a level four page, and so forth. The text that identifies each page is the Title text. To enter or modify this text, open the page in Page view and then, on the File menu, click Page Properties. It's quite common after creating a new Table Of Contents component to find many of the Web pages identified with names like New Page 2 or New Page 683. This is because you haven't yet given your pages meaningful titles. Because the title of each Web page is quite evident to Web visitorsit appears in the browser's Title baryou really should go back and give all your pages reasonable titles. A more difficult problem with the Table Of Contents component is that it picks up various Web pages you'd rather it didn't. Most Web pages contain not only "primary" hyperlinksmeaning those that truly reflect your Web's intended structurebut also various "convenience" links that point to almost random but nevertheless useful locations. Unfortunately, the Table Of Contents component doesn't know the difference and displays all links, significant or not. There's really no fix for this other than removing the extraneous links, and that might be something you're not prepared to do. The Table Of Contents component, like most things in life, is neither a quick and universal fix nor a useless failure. If it meets your needs, don't hesitate to use it. But if your needs differ from what the component provides, forcing the labor-saving component to do what you want might be more work than creating a clickable site map by hand.
Changing the background color of a shared border changes the wrong borderSource of the problemWhen you change the background color of a shared border, the Border Properties dialog box defaults to the first available border, not to the last border you clicked in the Shared Borders dialog box.When the Border Properties dialog box appears, you must use the Border drop-down box to select the border you want.
How to fix itTo change the background color of a shared border, be sure to select the correct border in the Border list in the Border Properties dialog box. To do this, follow these steps:
Note that if you clear all the check boxes, no shared borders will be in effect and FrontPage therefore dims the Border Properties button. However, because this problem assumes you're using one or more shared borders, the Border Properties button should be available. Click it.
The hyperlink rollover effects built into FrontPage aren't sufficient
Source of the problemYou can make your Web pages more interactive by opening them in Page view and selecting the Enable Hyperlinks Rollover Effects check box on the Page Properties dialog box. (To display this setting, click Properties on the File menu, and then click the Background tab.)This check box and the options available after clicking the associated Rollover Style button provide a fair number of options but don't exploit the full flexibility of Cascading Style Sheets (CSS). But by hand-entering CSS code, you can obtain several effects not available through the Rollover Style button.
How to fix itOpen a new or existing Web page and make sure it contains one or more ordinary text hyperlinks. Here's the procedure to create a new page for experimentation:
When the Insert Hyperlink dialog box appears, in the Address field, enter http://search.microsoft.com, and click OK.
Make underlines a different color In this effect, the hyperlink text color will be the same as the text color of the document. Only the line under each hyperlink will appear in a different color:
<style> At the bottom of the Page view window, click the Preview tab to see the effect of your changes. The <style> and </style> tags mark these lines as CSS code that applies to the entire Web page.
The second and third lines constitute a CSS rule that applies to the entire body of the Web page. They contain three formatting commands:
The next three lines constitute a rule that applies to all hyperlinks. (The HTML tag for a hyperlink is <a>, for anchor.) It contains four specifications:
The last four lines set the border color to different colors for ordinary hyperlinks, recently visited hyperlinks, hyperlinks currently beneath the mouse pointer, and whatever hyperlink the visitor clicks. The hyperlink text itself will remain black. If you have trouble seeing the underline color change, increase the thickness to 3 or 5 pixels. Outline buttons This effect is similar to the previous one, except that it draws a border around all four sides of each hyperlink. The following code creates the effect of hyperlink text within a hollow square button:
<style> Here's how this code differs from that in the previous example:
Hover buttons This effect creates solid hover-style buttons. Change the CSS code to the following:
<style> Here's how this code differs from that in the previous example:
Alter text styles This effect formats all hyperlink text as non-underlined, italicized, and lowercase. Unvisited links appear in bold text, and links are converted to uppercase text when a Web visitor rests the mouse pointer over the link:
<style> Here's how this code differs from that in the previous example:
More information Like the hyperlink rollover effects built into FrontPage, these examples barely scratch the surface of what is possible. Working with this code, however, should give you the ability and incentive for further experimentation and investigation. For additional references on this topic, browse http://search.Microsoft.com, and search for the following article numbers:
I can't get rid of the underlining on hyperlinks
Source of the problemFrom the standpoint of typography, underlining is an archaic technique that dates back to the early days of typewriters. Now that computers handle fonts and other typographical effects with ease, underlined hyperlinks are quite a throwback. This solution explains how to remove underlining from hyperlinks in Microsoft FrontPage 2002.
How to fix itRemove the underline from a single hyperlinkTo remove the underline formatting from a single hyperlink:
Remove the underline from all hyperlinks You can remove the underline from all hyperlinks in a page by adding a <STYLE> section to the page. To do this:
Cellspacing or cellpadding attributes disappear from HTMLSource of the problemFrontPage might remove the cellspacing or cellpadding table attributes from your HTML when you set the Cell Padding attribute of a table to 2 pixels or when you set the Cell Spacing attribute of a table to 1 pixel.These values are the browser defaults for the given properties. FrontPage removes both the attribute and the value because they're unnecessary.
How to fix itTo work around this behavior, change attribute values in the HTML source. To do this, follow these steps:
<table border="1" cellpadding="0" cellspacing="0"
<table border="1" cellpadding="1" cellspacing="2"
I right-clicked an inline frame, but the Inline Frame Properties command didn't appearSource of the problemWhen you use FrontPage to open a Web page that contains an inline frame (IFRAME), and then right-click the inline frame, the resulting shortcut menu doesn't contain an Inline Frame Prop-erties command.You can select an inline frame only by clicking its outer edges. When you click in the middle of the IFRAME, you select the properties for the underlying page.
How to fix itTo work around this problem, follow these steps:
An Inline Frame Properties option will appear on the shortcut menu.
I can't create an inline frame with a margin width of zeroSource of the problemEven though 0 is a valid value for the margin width of an inline frame, entering a Margin Width of 0 in the Inline Frame Properties dialog box will cause this error message to appear:"Please enter an integer between 1 and 100000."
How to fix itTo work around this problem:
Locate this value:
marginwidth="1" Change it to:
marginwidth="0"
The WordArt gallery doesn't provide enough formatting optionsSource of the problemInserting WordArt is simple but might not produce the appearance you had in mind. Fortunately, FrontPage has far more options than the WordArt Gallery provides.
How to fix itIf none of the styles in the WordArt Gallery meet your needs, choose the style that's closest to what you want and then modify the results using these tools:
To modify a WordArt object, first select the object, and then use the following toolbar buttons:
To modify a WordArt object, first select the object, and then use the following toolbar buttons:
More information FrontPage displays Word Art objectsand a range of other drawing objects as wellusing a technology called Vector Markup Language (VML). VML describes pictures as a series of points, lines, and curves, and notlike a GIF or JPEG fileas a series of colored dots. Pictures consisting mostly of lines and colored shapes are drastically smaller when expressed as VML rather than GIF or JPEG files. Because not all browsers support VML, FrontPage:
Together, these actions produce the following results:
To control the details of this approach:
The Down Level Image File check box controls the creation of GIF files that correspond to each VML picture. Selecting this box tells FrontPage to create such files. Clearing it means browsers that don't support VML will bypass the picture.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||