To get started quickly, read this document carefully.
What is HexWeb Typograph?
HexWeb Typograph is a brand new extension to the well-known and award-winning web authoring tool BBEdit 4.x, used by thousands of online publishing professionals around the globe. With HexWeb Typograph Web designers and typographers can now bring true viewing of fonts (including multilingual fonts) to Web pages. HexWeb Typograph is also available as a stand-alone version for Macintosh & Windows 95/NT.
The integration of the TrueDoc Dynamic Font technology with the latest version of the Netscape Communicator allows Web publishing professionals to create stylish HTML documents by using different fonts and fonts styles (e.g. according to the Corporate Design of their customers). Netscape client software users will be able to view these Web pages excactly as the content designers intended them to be seen, across a variety of font and character set encoding.
Click here to read more about the Dynamic Font technology.
To get started:
1. Unpack the Typograph.sea.hqx file to your hard disk.2. Copy the HexWeb Typograph 2.0 extension to your BBEdit Plug-Ins folder
3. Copy the "Standard PFR Files"-Folder in the BBEdit Folder
If you wish to use centralized PFR files on your Web server, then you can scan the existing PFRs from here and place the font tags from the files located in this folder.
4. Start BBEdit by opening the "test.html" file.
The licensing dialog appears. If you have already purchased HexWeb Typograph, you should type in the license Name and Key Code into the two fields below. If you are only evaluating Typograph in demo mode, click the "Demo" button.
The following floating palette appears: In this palette you can compose the font tags and the PFR files visually, without needing to write the code.
The functions of the floating palette:
1. The File Popup:
If you wish to scan already existing PFR files from the "Standard PFR Folder", click the "File" checkbox. The PFR files then appear in the popup.
2. The Font Popup:
Here you will see the available fonts. If the "File" checkbox is selected, this popup will show the fonts containined in the individual PFR files.
If you have the "File" checkbox not selected, the fonts installed in your System are listed in the popup. Please notice that you need to have outline fonts installed in the System to be able to create PFR files.
3. The Size and colour selection:
The size and the colour for the font tag can be selected here. If you do not wish to use these parameters, just deselect the checkboxes.
As an alternative to the traditional <FONT SIZE=""> tags you can now use the new <FONT POINT-SIZE=""> tag, which allows you to scale up to as many points as you wish. Please note that other browsers than communicator will not support this tag.
4. The Direct Burning Button: This button opens a dialog for direct burning of Dynamic Fonts. You do not need to open any HTML document for direct burning.
5. The Alternative Fonts Button:
In this version of Typograph, you can define alternative fonts for your Dynamic Fonts. This makes your pages more compatible to older browsers.
6. The PFR Burning Button:
This button starts the PFR burning procedure. Before that a preferences dialog is opened.
7. The Insert Button:
The Font tags you composed using the popups, can be inserted direct to the page with this button.
When you have a piece of text selected, and click here, the font tags for the selected font is inserted.
After you have all your text formatted with font tags, you can create your Portable Font Resource. After clicking the button, you can do some settings in the following dialog:
Please note, that you have to type in the actual Domain of the project you are working on. The PFR files are copy protected, and can only be used under that domain. With this version of Typograph, you can edit the Domain to change the site you are creating Dynamic Fonts for.
If you have all your PFR files in one specific folder, you can set the path in the lower text field. The PFR documents are always saved in the same folder as the opened document.
If you wish to "burn" the whole standard ASCII table of characters, you can select that setting with the first radio button. English speaking sites might want to use only the lower 128 characters to make the PFR file smaller. It is also possible, to use only the characters used in the opened document.
Insert Link Tag means, that the link to the PFR document will be added to the beginning of the HTML document.
When you are ready, click the "OK" button. Now the PFR file will be created.
The Syntax of of the sample HTML file:
<HTML><HEAD><LINK REL="fontdef" HXBURNED SRC="test.pfr">
<TITLE>Test Document</TITLE>
<BODY BGCOLOR="FFFFFF"><FONT FACE="Trixie-Plain" SIZE="7" COLOR="#000000">
The big brown Fox is back to the business!</FONT>
</BODY>
</HTML>The "Link REL" tag will tell Netscape Communicator, in which PFR file the fonts are located, that are used in this HTML page.
The "Font Face" tag needs to have the name of the real font, this will be written by the Typograph extension, when you have selected the text you want to contain that individual font.
Please note that at the moment, only Netscape Communicator supports Dynamic Fonts. The HTML files are, although compatible with older browsers, there the PFR files are ignored, and the Font Face tags are interpreted as usual.
NOTE:
When you are moving the files and the PFR files to your Web Server, be sure, thet you have added the MIME-TYPE application/font-tdpfr with the suffix pfr to the MIME-Types.