Microsoft maps their "private" symbol range U+F020..U+F0FF into the ASCII range U+0020...U+00FF to symbol fonts.
As this symbol range in the Unicode specification is Microsoft-specific, Apple and Linux don't do this mapping. SPS and IS don't do this mapping either. There is no error from SPS when uploading and displaying the font. However, if there are no valid characters at the real positions U+0020...U+00FF, IPS/IS doesn't display any characters.
Download the font from SPS and install to your fonts folder.
Then open the character map by choosing Accessories > System Tools > Character Map.
Select the font from the pop-up menu and make sure that all the characters are visible and look OK.
For more information, see http://www.vistax64.com/tutorials/93584-character-map.html.
Upload all font styles (bold, italic, bold/italic, and regular) into SPS if you plan to use the Text editor on the Template Authoring page. Doing so ensures that all styles are available to Image Serving when it processes requests. If you apply a font style that is not installed on your system, the text in the Text editor doesn't reflect that font style. If the corresponding style is not available to Image Serving, the layered image doesn't reflect that font style.
If the name or style of the font isn't derived correctly when the font is uploaded into SPS, double-click the font to correct any problems.
For more information, see http://help.adobe.com/en_US/scene7/using/WS0F37AB0B-B54A-411d-A92B-074265EEA926.html.
Scene7 uses the RTF Name for the attribute. That is, “fontFamily” as it appears in an s7fxg, which equates to RichText fontFamily in the Template Publishing Editor.
The authoring applications use “Font Family Name” as you see it in Detail View of SPS. However, it breaks down to actual separate font files in many cases, when the user specifies a style option.
These files have a filename that can also be different.
Furthermore, not all fontWeights are necessarily available with a given RTF name. In s7fxg, Scene7 restricts fontWeight to having two values: “normal” and “bold”. But, specifying either of these don't necessarily work whether the font file contains a “bold” or “normal” fontWeight character map or not. Similarly, specifying “italic” or “normal” for fontStyle using a given RTF Name doesn't necessarily work, and depends on these being in the file itself.
Many times when there are fonts listed using a particular “Font Family Name” in the authoring application, there are many font styles. For example, Myriad Pro has many, and they break down into separate files each with a filename, an RTF name, a PostScript Name (which Scene7 ignores in W2P workflow,) and a Font Family name. (This naming equates to Font Family as seen in the authoring application. It also lets the authoring application know how to group the font files for the interface.) With Myriad Pro fonts, as seen from the authoring application, all of these different styles have “Font Family Name” as common when seen from Detail View.
So “Font Style” in the authoring application has a different meaning than fontStyle as seen in Scene7 W2P workflow. In the authoring application, it is more of a general description of a font that falls under the given Font Family.
Scene7 is not the only place where these conventions are used. In fact, Microsoft invented RTF. It's used so different applications can have a common method of using fonts, while the “Font Family” themselves could have a multitude of different styles.
Some fonts with ornate glyphs include what is called a contextual ligature. SPS does not currently support this feature.
It is possible to render fonts correctly before that release by adding the following DOM manipulation to the appropriate ID:
*(replace the parenthesis with curly braces)