Notification
Newbie
I’m having issues with client fonts displaying properly when published.
In Classic Captivate, I was able to add domains during publishing or link my fonts to Adobe fonts through the text selection tool so that I could use branded fonts for my courses. However, I cannot find any place in the New Captivate (12.6.0.63) to link my project to Adobe fonts. My courses are not showing up in my Web Projects and fonts are not displaying properly. This will be especially critical once I place translations for the courses and will need to select the language subsets from the Web Projects page.
How do I resolve this? What do I need to do to get New Captivate and Adobe Fonts communicating?
In Classic Captivate, I was able to add domains during publishing or link my fonts to Adobe fonts through the text selection tool so that I could use branded fonts for my courses. However, I cannot find any place in the New Captivate (12.6.0.63) to link my project to Adobe fonts. My courses are not showing up in my Web Projects and fonts are not displaying properly. This will be especially critical once I place translations for the courses and will need to select the language subsets from the Web Projects page.
How do I resolve this? What do I need to do to get New Captivate and Adobe Fonts communicating?
You must be logged in to post a comment.
- Most Recent
- Most Relevant
Hi hollyh23906224,
Thank you for your query. We also appreciate Shital Patil for their inputs.
We hope this information addresses your query. We also encourage you to submit your valuable feedback and suggestions directly in Captivate via Help->Provide Feedback. You may also contact the technical support team directly via phone (+1-800-833-6687) or chat (https://www.adobe.com/getsupport) for assistance.
Here to help,
Adobe Captivate Support
You’re right — **Classic Captivate** allowed direct integration with Adobe Fonts (formerly Typekit), especially when publishing HTML5 content. In **New Captivate (12.6.0.63)**, Adobe has redesigned the interface and publishing pipeline significantly, and unfortunately, **Adobe Fonts integration is not yet directly supported in the UI** as it was in Classic Captivate.
### ✅ Current State of Adobe Fonts in New Captivate (12.6.0.63)
As of now, **New Captivate does not offer built-in Adobe Fonts integration or domain linking at publish time**. That’s why:
* You’re not seeing your **Adobe Fonts Web Project** linked.
* Custom fonts are **not rendering properly** in the browser.
* You cannot assign **language subsets** to fonts from within Captivate.
—
### 🔧 Workaround to Use Adobe Fonts in New Captivate
You can still **manually integrate Adobe Fonts** by embedding them in your HTML wrapper after publishing. Here’s how:
#### 🔁 Step-by-Step Workaround
1. **Create a Web Project on Adobe Fonts:**
* Go to [Adobe Fonts Web Projects](https://fonts.adobe.com/my_fonts).
* Choose your fonts and create a **Web Project**.
* Copy the **embed code** (JavaScript snippet).
2. **Publish your Captivate project:**
* Export your course from New Captivate to **HTML5**.
3. **Edit the HTML Wrapper:**
* Locate the published folder.
* Open the `index.html` (or `index.htm`) file in a code/text editor.
* Paste the **Adobe Fonts embed code** in the `<head>` section of the HTML file.
Example:
“`html
<head>
<meta charset=”UTF-8″ />
<script>
(function(d) {
var config = {
kitId: ‘xxxxxxx’, // Your Adobe Fonts Web Project ID
scriptTimeout: 3000,
async: true
},
h=d.documentElement,t=setTimeout(function(){
h.className=h.className.replace(/\bwf-loading\b/g,””)+” wf-inactive”;
},config.scriptTimeout),tk=d.createElement(“script”),f=false,s=d.getElementsByTagName(“script”)[0],a;
h.className+=” wf-loading”;
tk.src=’https://use.typekit.net/’+config.kitId+’.js’;
tk.async=true;
tk.onload=tk.onreadystatechange=function(){
a=this.readyState;
if(f||a&&a!=”complete”&&a!=”loaded”)return;
f=true;clearTimeout(t);try{Typekit.load(config)}catch(e){}
};
s.parentNode.insertBefore(tk,s)
})(document);
</script>
</head>
“`
4. **Apply your fonts using CSS (if needed):**
* Inside the `index.html` or `style.css` (if present), define the CSS rules for font-family using the Adobe font.
Example:
“`css
body, .text-block {
font-family: “Your Adobe Font Name”, sans-serif;
}
“`
—
### 🌐 Important Notes
* You must **host your published Captivate course** on a domain that is registered in your **Adobe Fonts Web Project** settings.
* Some fonts may not display during preview mode but will work correctly when hosted.
* For **translated courses**, you can create separate Adobe Fonts Web Projects with proper **language subsets** and switch embed codes accordingly.
—
### 📢 Adobe’s Position (as of now)
Adobe has not yet reintroduced this feature in the New Captivate version (post-Classic). If Adobe Fonts integration is mission-critical for your team or branding, consider:
* Keeping Classic Captivate for certain branded deliverables until the new version catches up.
* Requesting Adobe to prioritize this feature through their **feature request portal**:
[https://tracker.adobe.com
