|
|
Embedding fonts with WEFT on an FTP server
When using WEFT to embed fonts on web pages by using an FTP server, you may
need to consider the following issues:
- Transferring the Web pages
WEFT transfers web pages during three different stages; pages are retrieved
when analyzing the usage of fonts within the pages, pages are downloaded
when WEFT inserts CSS font declarations, and pages may optionally be
uploaded back to a server.
An FTP server may be used to download pages from a remove server and when
uploading the modified pages back to a remote server. You may typically
allow WEFT to download web pages using a http URL. However, if the pages
contains server scripts or other non-static HTML that an HTTP server will
process before sending to a web browser, then you need a way to allow WEFT
to retrieved the *un-processed* page. For example, an ActiveX Server Page,
or a web page with a Netscape Server Side JavaScript contains scripts that
are executed to produce html code for a web browser. WEFT needs to access
these pages *after* they have been processed when it is doing the font
analyses, but will need the page *before* they are processed by the server
when adding the font declaration to them. In the latter case, you would need
to download the pages using FTP server to circumvent the processing that a
HTTP server would otherwise do on these pages.
- Accessing pages through FTP, compared to HTTP
An FTP server may provide a different naming scheme than what is used for
pages on a HTTP server. For example, the page
http://foo.company.com/user1/default.asp may be accessible as
ftp://foo.company.com/inetpub/wwwroot/users/user1/webroot/default.asp on an
FTP server. Note that the difference is most often that the parent
directories have different names, while the two specifications of the page
are same below that parent directory. In this example, the page is called
"/user1/default.asp" for both the FTP and the HTTP server, while the parent
directory is called "/" for the HTTP server and "/inetpub/wwwroot/users/"
for the FTP server. This should be self evident for anyone using FTP to
publish modified pages to a web server.
In order for WEFT to be able to access pages through FTP, it needs to know
how to map a HTTP url to an FTP url. This is done by telling WEFT what
directories on the http server are called when accessed through an FTP
server. Two dialogs exist for this purpose - one for downloads and one for
uploads. For server pages, you would typically only use the download dialog,
because the download settings can be used for the upload as well which is
what happens by default. You access this dialog by clicking on the
"Advanced" button in the "Create Font objects" stage of the wizard, or
through the "Tools/Create Font object" menu. If you are only working with
plain html pages, then you would only need to use the upload dialog as pages
can be downloaded directly from the HTTP server. You access this dialog
through the "Advanced" dialog of the "Publish Web Pages" dialog, or the
"Tool/Publish" menu.
The dialog is used by first selecting one of the directories on the HTTP
server, which are all illustrated in the dialog as a tree. Once select, the
dialog will update an input field with what the directory would be called on
the FTP server. Simply type in the correct directory path in this field if
it is not correct.
- User authentication
Another different could be that the page can be accessible to everyone
through an http server while FTP access to the pages are restricted to a
selected few. Also, the http server would allow for read-only access, while
the FTP server could allow both read and write operations to the pages.
Pages accessed through HTTP have a different authentication scheme than
using FTP, as this process uses parts of Internet Explorer 4.0. It will
bring up it's own user and password dialogs. The user name and password for
the FTP server is set during the first step of the dialog, by clicking on
the button labeled "Internet Access...".
Common problems
- WEFT may not be able to access your FTP server, for a number of reasons.
In such cases, you will get an error messages. If this message does not make
any sense to you, and you believe you should be able to access the pages,
then try to type in the FTP URL of one of the pages in Internet Explorer. If
it does not works there, then it will not work in WEFT either, for the same
reason. Contact your system administrators to resolve that problem. The
problem could be that the server is not running, the network may not be
available, the server is protected by a fire-wall etc.
- You may have forgotten to specify a user name and a password for the FTP
server (or given the wrong name or password), by clicking on the "Internet
Access..." button in the "User Information" stage of the wizard.
- Your FTP server may support a non-standard command set by default. When
using the FTP server manually, you may get a log on message that indicates
how to turn off these extra functionality. Doing that may solve your
problems.
- You have not specified where the pages should be uploaded to or download
from, in which case WEFT may have attempt to create or access the pages from
the wrong locations on the server. Clicking on the "Advance" button in the
"Create Font object" and "Publish pages" stages to rectify this problem.
Example
Assume that we have the following two pages, that are entered into WEFT
during the "Add Web Pages" stage of the wizard:
http://www.corp.se/foo/default.htm
http://www.corp.se/foo/bar/index.asp
Assume further that an FTP server is running on the same machine, and that
all web pages are stored at:
ftp://ftp.corp.se/inetpub/wwwroot
Also, assume that we need to provide a password for the FTP server.
During the "User Information" stage of the wizard, we clicking on the
"Internet Access" button and the type our user name and password for the FTP
server.
During the "Create Font object" stage, you will need to provide an access
method for at least "index.asp", because this is server page. We will do
this by telling WEFT where to find the root directory "foo" on the FTP
server. This will allow WEFT to located all the files under this directory
on the FTP server.
Do this by clicking on "Advanced". In the advanced version of "Create Font
Objects" dialog, select the "foo" directory. The "Font objects location"
field will be updated. Type the FTP URL of the directory, which is:
ftp://ftp.corp.se/inetpub/wwwroot/foo
You may now verify that WEFT is not able to find all the pages by selecting
the "default.html" page and the "index.asp" page.When doing that, the
"locations" field should be updated with the correct FTP URL.
During the "Publish Web Page" stage of the wizard, we may wish to verify
that WEFT knows where to publish the pages on the FTP server. We do this by
clicking on the "advanced" button, which brings up a dialog that looks much
like the advanced create font object dialog. Clicking on the pages should
update the "locations" field with the appropriate FTP URLs. If the
information is not correct, then simply type in the correct information.
You are all done!
this page was last updated 2 June 1998
© 1998 Microsoft Corporation. All rights reserved.
Legal Notices.
please e-mail comments to us via the e-mail address listed here.
|
|
