FrontPage - Tips |
Topic status automatically displays here - do not remove.
Like all other Microsoft products, FrontPage (FP) has its own idiosyncrasies and quirks.
This topic describes those FP behaviours which appear strange or illogical, and details the problem, with examples, solutions and workarounds, and tips.
General Tips
Using
VSS with FP
Working with Lists
Working with Bookmarks
Working with Hyperlinks
Working with Tables
Working with Character Entities
Note
Unless stated otherwise, all references are for FP2000, as supplied with Office2000.
How
to install Office 2000 (including FrontPage 2000)
How
to determine which version of FrontPage is installed
How
to install the HTML Tools toolbar in FrontPage
How
to add the Lotech Solutions style toolbar to FrontPage
Using FrontPage to Create Glossary Popups
Using FrontPage To Create Hidden Sections
FrontPage Keyboard Shortcuts
Tips and tricks for editing raw HTML
When using FP2000, don't copy anything directly from MS Word as it carries heaps of unwanted inline formatting with it. If you must copy something from a Word source, paste it into Notepad first (which removes all formatting baggage), then reselect and copy it from Notepad into FP. This annoying behaviour was remedied in FP2002 where MS has provided different paste behaviour with the clipboard.
As a workaround to the annoying behaviour of FP to display it's preview pages from a temporary folder, and subsequently break all script created links, you should copy the attached Version.txt file to your login profile folder named "Local Settings", (e.g. D:\Documents and Settings\colinramsden\Local Settings\Version.txt).
Note
After upgrading to FP XP (2002), this behaviour reoccurred. You have to copy the Version.txt file into the folder named "Temporary Internet Files" beneath "Local Settings" in the profile. This is a devil in itself as the right-click Paste menu item is disabled (greyed-out) in this folder. You have to right-click on the folder itself in the tree in the Folders pane. The paste appears to work, even though the file doesn't display in the list view pane.
Apparently, FP webs can integrate with VSS5 and later, automating file check-in and check-out with SourceSafe. However, it appears that this can only occur if the option was chosen during the installation of VSS. You must select the Custom installation option, and check the Enable SourceSafe Integration check box.
For further details, see: file://syd-file2/doco/ADMIN/Help%20Tools/FrontPage%202000%20Server%20Extensions%20DK/adadv_6.htm#advss.doc-1019.
The next best alternative (if installing a new version of VSS is not possible), is to utilise the "light" version control mechanism available to FP Server Extension enabled webs. To enable this functionality, (disabled by default), you must first of all have the folder structure for the web project containing only the required files for the project in the folder, (with no mixed projects sharing "common" folders).
You next start-up FP and using the open web command (from the menu select File | Open Web), navigate to the root folder of the web project. You will be prompted to create a web and requested for permission to install the FP Server Extensions to the web folder. Accept the request.
Once open, click on the root node of the Folder List tree, then from the menu select Tools | Web Settings. On the General tab, check the Use document check-in and check-out check box. When prompted for confirmation, click Yes.
Unfortunately, FrontPage does not produce paired tags when dealing with lists, which causes inconsistent display of the topic. The result is that the unclosed <P> tag is embedded within the closed <LI> tag pair. This does not comply with the ECMA-262 Standard and will break XML when we port the help to the dotNET platform.
Incorrect
<UL> <LI> <P CLASS="txt">List item 1 text goes here.</LI> <LI> <P CLASS="txt">List item 2 text goes here.</LI> </UL>
Correct
<UL> <LI>List item 1 text goes here.</LI> <LI>List item 2 text goes here.</LI> </UL>
To remove unwanted unpaired <P> tags located within list items:
Either
Unfortunately, FrontPage does not produce paired tags when dealing with lists, which causes inconsistent display of the topic. As with the previous problem (Removing unwanted unpaired <P> tags within lists), the result is that the unclosed <P> tag is embedded within the closed <LI> tag pair. This still does not comply with the ECMA-262 Standard and will break XML when we port the help to the dotNET platform.
Incorrect
<UL>
<LI>List item 1 text goes here.</LI>
<P CLASS="txt">Paragraph
text displays here.
<LI>List item 2 text goes here.</LI>
</UL>
Correct
<UL>
<LI>List item 1 text goes here.</LI>
<P CLASS="txt">Paragraph
text displays here.</P>
<LI>List item 2 text goes here.</LI>
</UL>
To add paired <P> tags within lists:
This procedure is useful for adding paragraphs within existing lists whilst remaining in Normal tab view. Create the list outline first, then go back to insert any extra paragraphs within the list where required.
<OL> <LI>List Item 1</LI> <LI>List Item 2</LI> <LI>List Item 3</LI> </OL>
<OL> <LI>List Item 1</LI> <LI>List Item 2</LI> <LI> <P class="txt"> </LI> <LI>List Item 3</LI> </OL>
<OL> <LI>List Item 1</LI> <LI>List Item 2</LI> <P class="txt"></P> <LI>List Item 3</LI> </OL>
Tables display with large ugly grey borders.
Incorrect
Column | Data |
---|---|
NamespaceKey | MS.HelpIntegrDemo.1033 |
NamespaceName | MS.HelpIntegrDemo.1033 |
File_Collection | _E933A8FC91204B9B839FF5B8C801A26D1 |
Description Help | Integration Demo Collection |
Correct
Column | Data |
---|---|
NamespaceKey | MS.HelpIntegrDemo.1033 |
NamespaceName | MS.HelpIntegrDemo.1033 |
File_Collection | _E933A8FC91204B9B839FF5B8C801A26D1 |
Description Help | Integration Demo Collection |
FP (or is it IE?) has the annoying tendency to display some HTML tags with default values which are not always obvious to the HTML author. Tables and Lists seem to cause the most grief to the unwary. Even though all table properties are set in the LotechSolutions.css, FP and IE ignore some of them unless certain conditions are met.
To properly apply Table styles
FP (& IE) require the TABLE tag to contain the CELLSPACING and PADDING parameters before they'll apply CSS values to them.
<TABLE CELLSPACING="0" PADDING="0">
or
<TABLE CELLSPACING PADDING>
FP has a limited range of characters it can interpret, understand and display properly. This particular problem involves how to insert an en-dash () or em-dash () into a topic in FP.
Notes
An en-dash is not the same as a hyphen (-), and is not used in the same places as you would use a hyphen. See Using proper typography.
FP does not apparently recognise or display en-space or em-space character entities. Nor does it recognise thin-space or hair-space either.
Incorrect
hyphen: - double hyphen: — underscrore: _ typing "–": – typing "—": —
Correct
en-dash: em-dash:
To insert an en-dash or em-dash character entity using FP:
Unfortunately, FP provides no tool to insert character entities, so you have to manually insert them into the HTML.
Note
The start Ampersand (&) and the end semi-colon (;) are required.
Character Name | HTML4 Entity name (Dec) | Example |
---|---|---|
less than |
< |
< |
greater than |
&rt; |
> |
ampersand |
& |
& |
apostrophe or single quote |
' |
' |
double quote |
" |
" |
left single quote |
& |
|
right single quote |
& |
|
left double quote |
& |
|
right double quote |
& |
|
non-breaking space |
|
|
en-space |
  |
|
em-space |
  |
|
thin space |
  |
|
en-dash |
& |
|
em-dash |
& |
|
over-line |
‾ |
‾ |
horizontal ellipsis |
& |
|
bullet |
& |
|
degree |
° |
° |
trademark |
& |
|
copyright |
& |
|
registered |
& |
|
vulgar fraction one quarter |
&fraq14 |
|
vulgar fraction one half |
&fraq12 |
|
vulgar fraction three quarters |
&fraq34 |
|
infinity |
∞ |
∞ |
pi symbol |
ϖ |
ϖ |
Pi Greek letter (lower case) |
πpx; |
πpx; |
Pi Greek letter (capital) |
Π |
Π |
lozenge |
◊ |
◊ |
spades |
♠ |
♠ |
clubs |
♣ |
♣ |
hearts |
♥ |
♥ |
diamonds |
♦px; |
♦px; |
Euro |
& |
|
prime hours / feet |
′ |
′ |
Prime minutes / inches |
″ |
″ |
Warning
These named entities are case sensitive. See "prime" and "Prime".
Character Name | Unicode Value Hex (Dec) | Example |
---|---|---|
en-space character | 2002 (8194) | |
em-space character | 2003 (8195) | |
thin space | 2009 (8201) | |
hair space | 200A (8202) | |
hyphen (breaking) | 2010 (8208) | ‐ |
hyphen (non-breaking) | 2011 (8209) | ‑ |
en-dash character | 2013 (8211) | |
em-dash character | 2014 (8212) | |
TradeMark symbol | 2122 (8482) | |
CopyRight symbol | 00A9 (0169) | |
Registered symbol | 00AE (0174) | |
degrees symbol | 00B0 (0176) |
For details, see http://www.w3.org/TR/REC-html40/sgml/entities.html
Description.
Incorrect
WrongExample
Correct
RightExample
Either
http://news.cnet.com/2100-1001-239273.html |
How to install Office 2000 (including FrontPage 2000) |
How to determine which version of FrontPage is installed |
How to install the HTML Tools toolbar in FrontPage |
How to add the Lotech Solutions style toolbar to FrontPage |
Using FrontPage to Create Glossary Popups |
Using FrontPage To Create Hidden Sections |
FrontPage Keyboard Shortcuts |
Tips and tricks for editing raw HTML | Lotech
Solutions' Tips, Tricks, and Procedures
Copyright Lotech Solutions. All rights reserved.