Font size in a player and in powerpoint

Hi, Soogyung -- Thanks for your question and for sharing your file. Have you had an opportunity to test your published output in the intended environment? As stated in this article, If you view published Articulate Presenter content on your local hard drive or send it to someone else to view on their local hard drive, you'll encounter security restrictions from the computer, web browser, Flash Player, and network that'll cause various features to fail. 

Please let us know if issues persist, and if so, I will be happy to take a look at your file. :)

Hello Christie,

We uploaded the courses to LMS and checked the slides that have the issue. It happens in LMS as well.  Is there anything I can provide more?

Thanks,

Soo

Please let me know if the package would be better to look at. 

Soo

Hi, Soogyung -- Yes, if you could share your Articulate Package, that would be great! And as you are publishing for LMS, I'll go ahead and test your published output in the SCORM Cloud to see if I experience the same behavior you are describing in that environment.

Hello Cristie,

The package is attached. ;-)

Soo

Just wanted to touch base to let you know I have received your Articulate Package, Soogyung, and I will begin testing momentarily. I appreciate your patience. :)

Hi Soogyung,

Sorry about my previous post, odd copy/paste behavior! Anyway, I took your file and published it to SCORM Cloud and you can view it here. The font looked the same in the preview version compared to the Powerpoint set up and I took a screenshot to show that behavior below: 

Can you take a look at the version I published and let us know how it behaves for you and what browser you're viewing it through? 

Hi, Soogyung -- I wanted to let you know that I experienced the same outcome that Ashley illustrated above with her screenshots -- no discernible difference in font size/style that I can see. Please let us know what you experience with SCORM Cloud when you have a moment! :)

Hello Christie and Ashley,

I have the same output as on your screenshot. The first line font looks smaller than in Powerpoint. The slide I attached is just one of the examples. I see a lot of occurrences in my courses. In LMS, exactly same thing happens as in preview mode.

Soo

Hi Soo,

Thanks for clarifying - I think I see what you're describing but the difference was slight to me so I didn't notice it. I'm going to take a deeper look at this now and will be in touch shortly. 

Hi Soo,

Thanks again for your patience while I took a further look at this. I tested again and it seems to be connected to the ó within your word definición. I was able to replicate that in your file by adding a new single text box with that word, but oddly enough in your file once I placed that character in a large body of text it behaved normally. Similarly in a brand new file, that character, word and a large body of text all behaved normally on preview and publish. So it's something specific to that text box/character (which when I tested I was copying/pasting into new versions in your file). Can you confirm that you're working on files as described here? 

Are you seeing this on other characters or text boxes? Or just that one? 

Hi Soo,

Just a guess, is it possible that you upgraded also powerpoint since you created the courses?

If so ,it's a commonly known problem in ppoint, since powerpoint 13 (possibly also 2010), texts in text boxes are automatically adapted depending on the size of the text box.

In your example, for a very strange reason, powerpoint interpretes the 1st text box as to small, so he automatically reduces the font size while publishing.

I just increased the text box a little bit, and now the text seem to have te same size, see screen shot attached

Hello Ashley,

Thanks for investigating my file. I put my courses in D:. Since even if I have courses in C:, the issue happens same.

I see this issues all over the courses. 

I got the same result in the new file as you. If I make the text box bigger, it doesn't happen. But the problem is I need to do it for every single occurrence. These are already published before and they looked very fine. The issue only happens after I re-published. I understand Articulate will be always updated and I appreciate it. what I'd like to get some help is solving this issue easily if there is some way to fix them at once. As I mentioned I have a lot of courses and each of them is over 40 slides. It will make things really hard if I need to go through all slides...

Soo

Hi Soo, 

So in brand new files everything works normally? Perhaps you could look at the steps here to import it into a new file and see if that resolves the behavior and treats it as a new version and fixes the character issue? 

Hello Bruno,

Thanks for investigating the issue and your foundings. I suspected text box options but it seems it doesn't matter in my courses. The version of powerpoint is the same one I used for the old courses publishing. As you said if I make text boxes bigger, the font size looks fine. I would need to adjust one by one if what Ashley suggested is not working. I will try what Ashley suggested.

Thanks,

Soo

Hello Ashley,

Yes, it was okay if I paste it as a plain text. If I just copy and paste, the issue still happens.

Let me try what you suggested. Thanks for your help and supporting!

Soo

Hi Soo, 

Thanks for letting us know, and Bruno's suggestion is another good idea as well. Another thought (which I didn't try) is could you do a find and replace on that particular character, or are you seeing it on all accented characters? That replacement feature may help you at least quickly check each slide and get through the changes quickly. 

Hello Ashley,

Unfortunately, reusing slides and replacing problematic characters didn't work. Actually I cannot use reuse slides anyway because I have audio and timing already set for all slides. I did try it from my curiosity. I think that the best for now is adjusting the size of text boxes.

Thanks,

Soo

Thanks Soo for that update and sorry we weren't able to come to a better resolution for this issue and hopefully going forward in new files will allow it to work normally.