There are some client-side font and OLE options that don't always convert as expected when published server-side. The best workaround is to use Adobe Presenter to publish PowerPoint files to Connect. Adobe Presenter takes full advantage of all client-side fonts and OLE. It eliminates any delta between what you see locally and what appears published remotely on the Connect server. If you do not use Adobe Presenter and rely on Connect server-side conversion of your PowerPoint, the following tips can help address some PowerPoint conversion challenges.
The first option is to embed fonts in a PowerPoint file before publishing it. This process has limited effects, as fonts don't cause many conversion deltas. Proprietary OLE software causes many of these issues.). Nevertheless, it is a good first step and it is easy to do and can help in some cases:
- In the Microsoft PowerPoint presentation, Choose File > Save As.
- In the Save As dialog box, choose Tools > Save Options.
- Select Embed TrueType fonts.
- Select either Embed Characters In Use Only or Embed All Characters. (If you choose Embed All Characters, the size of the PowerPoint file increases.)
- Click OK, and then click Save.
If embedding the fonts does not solve the problem, the second option is to make server-side changes on your Adobe Connect server. This option is easier if you have an on-premise deployment as you can install proprietary fonts or OLE software on your local server. If you have a deployment that Adobe hosts, open a support case to research the nature of the conversion delta and discuss any possible ways of fixing the problem. Since Adobe's hosted clusters are multitenancy, licensing factors around proprietary fonts and OLE options can be complex. They warrant opening a support incident to research and discuss.
It is important to identify the source of the delta. Here is a picture of some MathType output that is typical problematic with reference to server-side conversion. Adobe Presenter used client side closes this delta instantly by leveraging the client side Fonts and OLE. But if you upload this symbol-laden PowerPoint example file directly to a Connect hosted server, you get the following result:
See below that by embedding the fonts as described above, it does help somewhat, but does not close the delta:
To see the source of the delta within the PowerPoint file itself, see that with the math symbols, successful conversion always involves an embedded OLE server. Look in the PPTX>File>Properties>Advanced Properties>Contents Tab. You see the following screen, and it tells you what fonts (or OLE server) are in use on a given slide:
As mentioned above, a quick way out is to have a copy of Adobe Presenter handy. You can install it at a point of escalation for font and OLE publishing issues (every author does not need a copy) and have the problematic PPTX files published in Adobe Presenter by a specific author tasked with solving any deltas by publishing from Presenter to the Connect servers.
If you decide to install either proprietary fonts or OLE server software onto your on-premise Connect servers, test it thoroughly as well as be sure to stay in compliance with the licensing of the fonts and OLE server software. Research and investigation are warranted before installation to make certain that you are in compliance.