BUG-Font Substituted in PowerPoint Upload

Problem: When uploading a PowerPoint (PP) file to Proclaim, a font used in PP is replaced by another font in the images Proclaim displays.

Details: When a PowerPoint (*.docx) file is uploaded to Proclaim from a machine with Office 2010, the font "Alternate Gothic No3 D" is replaced by another similar looking font (Arial?) but with much wider characters and spacing. However when the same exact file is uploaded from a machine with Office 2016, the font is correctly represented in the Proclaim images. The template for the original file was originally created using PP 2016 and edited on a machine using PP 2010. However, when the file is opened or displayed using PP 2010, the desired font is correctly rendered, and when saved as images, the font is correctly rendered. The "Alternate Gothic No3 D" font is installed on both machines. I'm running Office 2010 under Windows 7 Pro. See attached screen shots. #1 is the original PP slide rendered as an image with the "Alternate Gothic No3 D" correctly rendered in the title (all caps). #2 is a screen shot of the Proclaim image uploaded from the Office 2016 machine with the font correctly rendered. #3 is a screen shot of the Proclaim image uploaded from the Office 2010 machine with the font incorrectly rendered.

Questions: Why does Proclaim behave differently with different versions of Office? Is there a Windows or PowerPoint setting or other fix available? Does Proclaim access the system fonts, or does it use only a limited set of fonts? Can the developers provide a list of legal fonts that Proclaim will recognize?

Find more posts tagged with

Comments

Glenn Gervais (Faithlife)

Questions: Why does Proclaim behave differently with different versions of Office? Is there a Windows or PowerPoint setting or other fix available? Does Proclaim access the system fonts, or does it use only a limited set of fonts? Can the developers provide a list of legal fonts that Proclaim will recognize?

Gene-

We use a third party plugin to handle importing of Powerpoint documents and this plugin has many issues with importing. As you have seen, mostly around fonts and font handling. Best we can tell is they are attempting to recreate the building blocks (fonts, colors, placement, images...) of each slide to generate an image, which is then uploaded into Proclaim. I believe it is failing to match the exact font and using a fallback font. We see more issues on Mac than Windows in this area, but both are not always correct. We have open tickets for them to fix these issues.

I do not have a list of legal fonts as this process uses the fonts installed on the computer, it will be different based on which version of office is installed and what fonts the user has downloaded and installed.

The best workaround is to use Powerpoint and export each slide as an image to a folder, then upload all those images into a Proclaim Image Slideshow service item.

Here is more information: http://support.proclaimonline.com/hc/en-us/articles/206296245-Why-doesn-t-my-PowerPoint-presentation-import-properly-

Glenn

Gene Heathershaw

https://community.logos.com/discussion/comment/809978#Comment_809978

Thanks for the quick answer. Looks like some work is in progress on it.

The font we want to use is loaded and installed on the system using Office 2010, so it puzzles me that the plugin didn't find it on that machine but did find it on the machine using Office 2016.

Besides taking longer to generate because creating images of the slides is an extra step, uploading images to an image slide show clutters up the media library because the individual slide images accumulate as individual images in the media library, and they have to be deleted from the library after each use, thus taking even more time.

Any idea when these font issues will be resolved with the plug-in developer?

Thanks.

Beaver Creek Baptist Church

https://community.logos.com/discussion/comment/810000#Comment_810000

I would like to add my two cents on the media library clutter, I too have images and backgrounds that are single use, and the idea of loading the image, using it and then deleting it seems opposed to the "ease of use" concept.