I am publishing a piece of responsive eLearning using a Typekit font 'Runda' and 'Nimbus Sans'.
When I upload it, the Typekit fonts disappear and the project reverts back to Times New Roman.
I'm entering the appropriate domains on publish.
What could I be doing wrong here?
This is my eLearning hosted on reviewmyelearning.com - the font has dropped off and is displaying as Times New Roman.
This is the eLearning within the Adobe Captivate program - I have under 10 type kit fonts with my free plan, which is under the quota.
(I just entered all of the variations that I could think of - in case!)
I'm new with using Typekit, any help would be appreciated.
Which type of Typekit account do you have? The free account with Captivate allows only one domain, which looks like 'localhost' in your ase.
For some reason I thought I had a free account, but turns out that typekit comes as part of my enterprise account - it doesn't look like it has any limits either.
I culled all domains to just *.reviewmyelearning.com - and the font still seems to appear as Times New Roman when I upload it.
Any thoughts would be much appreciated
Jumping on the back of an old post - think this is my first time posting so not sure if that's the done thing!
Having the same problems. I am uploading to our LMS which I have done hundreds of times before and my adobe fonts have always been published absolutely fine. Recently our IT people uninstalled captivate and reinstalled it (so should be up to date 220.127.116.116) and ever since, my projects have been publishing with Times New Roman.
https://caba.talentlms.com is my LMS address. I have been putting the domain in as *.caba.talentlms.com.
I have full Adobe Font access.
I have the same login for CC and Captivate.
Why the wildcard as first character? Do you have subdomains which have a name before caba? Did you test locally or after uploading to the LMS? Did you add localhost as domain? If yes, how was the local view immediately after publishing?
Are you talking about responsive projects with Fluid Boxes? Reason for that question: for non-responsive projects only the dynamic texts should be converted to Times New Roman.
Thank you for replying so quickly.
What do you mean by wildcard?
I only tested after uploading to the LMS. For a bit of background - we have rebranded. I have re-uploaded the old brand version which is showing with the Adobe fonts, it is the most recent version that isn't. The rebranded version is just an updated version of the course that is uploading correctly (saved as new file), so in theory should work completely the same - just has new pictures. As far as I can think, they will both have been published with the same domain. It is a responsive project but we still use breakpoints as a company rather than fluid boxes.
As the previous version is uploading correctly, it makes me feel like some setting has been lost in the uninstall/reinstall as the course that's uploading correctly was only published a couple of months ago.
You should also include the dot. For example, if you are uploading it to reviewmyelearning.com, you should enter it as *.reviewmyelearning.com instead of *reviewmyelearning.com. Lieve is correct though. If you have a full Creative Cloud account you would be fine but if you are using the free account you are limited in the number of domains you can send this project to and have your Typekit account work.
One suggestion might be to only include the domain that you are using for review purposes right now. Later when you are ready to produce a final publish, change the domain to the final location of your eLearning when you are ready to publish for your final audience.
I've looked in to this further and I actually do have full access to Adobe Fonts as park of my Creative Cloud 'enterprise' subscription. My mistake.
Regardless, I culled all domains to just *.reviewmyelearning.com - and the font still seems to appear as Times New Roman when I upload it.
I can't seem to find anyone who's experienced similar issues which makes it really strange.
Are there any other steps that I'm missing in the process? I synced the fonts, they're all active, they work fine in captivate, I publish and type in the domain.
Is there another step to it that I've missed?
If you have any thoughts please let me know
James Kingsley is the owner of Review My eLearning and a friend. He suggested that you should submit a trouble ticket to his company so they can look at that for you.
FYI - Just tried to upload a sample project with a Typekit font and it worked fine for me. I ran the course from my iPad which definitely doesn't have the font in question but it showed up fine. I used *.reviewmyelearning.com as my domain by the way.
Thanks Paul, I really appreciate your help.
How strange. I published my eLearning course just then with the below settings (same as your own?) and uploaded to reviewmyelearning and it still keeps on showing a project with times new roman.
I've just tried it in my LMS in the same result (Times New Roman takes over). So it seems it might not be the sites I upload to, rather the program itself or the way I've configured it.
The only thing I can think of is that I'm somehow missing something when I publish.
It may not be related but it's considered best practice to publish to a local drive instead of to a network drive. This is often the cause of file corruption both in your project file and the resulting published ZIP file. I usually publish to my desktop folder.
Gave this a shot (exporting to desktop) and it didn't seem to make a different unfortunately.
I haven't seen anyone that's had this issue before, which makes it really strange.
The Typekit fonts obviously work on my computer, because I can see then on my Typekit website. I must just be doing something strange on my end that's somehow having an impact.
If anyone has any additional expertise or ideas to add to the conversation your input would be much appreciated!
After contacting Adobe their only suggestion was to update Captivate. I work for government, so updating software is a far lengthier process for me and unlikely to happen anytime soon.
I'm currently Adobe 2017. Does anyone with Adobe 2017 have this issue - I'm on 10.0.0.193?
It seems strange that I need to update Captivate to utilise typekit.
Please try installing patch to 10.0.1.285. I never had Tk problems in your
version as you can see on my blog examples.
There's not really anything strange about having to install an update for a software app to resolve an issue. This happens with all software applications.
You're not currently on the latest build that was available for Captivate 2017. The Adobe support person would be trained to tell you to update because there's very little point wasting a lot of time trying to resolve an issue that might ONLY be able to be resolved by installing an update.
I understand the fact that updating systems for some organisations is not a quick and easy process. But there's actually no cost involved in this case to just install the update because it's only a MINOR dot-point update, not a MAJOR new release
All you'd really need is for some IT person with administrator privileges to log into your PC and install the update from the Help > Updates menu. If your organisation is not willing to even allow that level of support, then you may indeed be stuck.
I ended up having IT update Adobe Captivate to the 2018 version on a test computer with the same result on export - Adobe Typekit fonts drop off and don't appear in the published package on either scorm cloud, reviewmyelearning or our lms.
We also tried disabling our anti-virus software and running everything as administrator, with no change.
If there are any other thoughts or ideas feel free to throw them my way, I'd love to hear them.
Hello. I have the same problem with Adobe Captivate 2019 (v.11.5....) and now it's the adobe fonts domain. I have tried all the possibilities, with my website, with the clients website, but I always see Times New Roman instead of Effra. I just started using the Creative Cloud and I have Adobe for Teams.
As I mentioned it's my first time using Creative Cloud for fonts, so a beginner's mistake may happen too.
I have set *.enaspot.com as "adobe fonts domain" and uploaded it here: elearning.enaspot.com/Test/PWL335%20Advanced%20DVB%20Troubleshooting/index_scorm.html
Not sure what could be the problem. It's the first time I am using Creative Cloud and cannot even start using it.
I have logged into creative cloud, activated the whole font family, the desktop app showed the font as present, I was able to find the font under the Adobe Fonts subcategory in Captivate, entered my domain in the adobe fonts domain.. Im confused if there is something I did wrong...
Fonts are showing up in the CC app? You have to keep that app open while publishing. Which Adobe fonts plan do you have, because that defines how many fonts you can have for free.
Yes I keep it open and I use the business - creative cloud for teams. Dont know more details cuz it's from the company I work on. At the end it does not matter, cuz I need basically 2 fonts from the same family (regular and bold). That's all, even one of the family can do the job. The thing is that all my content is converted into Times New Roman.
Do you use the same Adobe ID for CC and for Captivate?
No. could that be an issue?
It is just sort of intution. Only Adobe can give you an answer, I'm just a user. Can you contact them?
I did that this afternoon and after a huge, more than 5 hours long conversation we realized that the different account IS actually an issue. At first, I thought it's impossible because you can actually use the fonts in any other authoring tool or software that supports Adobe Fonts, no matter about the login details, emails, subscriptions etc except in their own authoring tool.