This release is first of all for resolving the set_manifest_issues introduced by release 20260421
typograph_document.set_manifest_data
async function now
set_manifest_data() returns a Promise, so it can be awaited, but it only needs to be if you want to wait for the font loading to complete before doing something afterwards (like reading the resolved font or checking the render).
If you call it without await, the fonts will still load and apply — it just happens asynchronously in the background. The canvas will redraw once the fonts finish loading regardless.
Use await when:
You need to inspect the result immediately after the call
You're chaining multiple set_manifest_data() calls and the second depends on the first completing
await is optional when:
You're just triggering a substitution and don't need to act on the outcome synchronously (e.g., a one-shot API call
from a host application) set_manifest_data() returns a Promise, so it can be awaited, but it only needs to be if you want to wait for
the font loading to complete before doing something afterwards (like reading the resolved font or checking the render).
If you call it without await, the fonts will still load and apply — it just happens asynchronously in the background.
The canvas will redraw once the fonts finish loading regardless.
image fitting/scale
default is now scale_to_fill H=Center, V=Center
if image is replaced by the user (select image in ContentBarImage) scale_to_fill H=Center V=Center Rotation = 0
if image is replaced while holding down the option key (alt-key) scale, H, V and Rotation unchanged
image browser
WATCH OUT STYLESHEET CHANGE style.css
wider so the 3 images fit side by side
native browser tooltip with full image name on hover
Page bar and Parameter bar
Show and hide wihtout scrambeld html during silde animation
Manifest remarks
Images in manifest
Before we started using a manifest the images lived as a url inside the PageElementImage Image now are part of the manifest and PageElementImage usess the id as a reference to the actual url. Below you will find the type of images typograph expects. The typograph converter pipeline (API) can/will create images for use with in a manifest, and converted the images for optiimal perfomace in the typograph-editor and viewer sre ceated.
In the manifest there can be 4 links for every image
original url:
not (yet) used by the editor is used by the typograph conversion pipe line
for diagnostics
all major raster file formats
all major vector file formats
editor url:
used by the editor for drawing on the HTML 5 Canvas
webp, jpeg, png for raster images
for performace use webp and lower resolution (max 1024px w or h)
svg for vector images
print url:
used for pdf creation
appopriate file type and resolution
png or jpeg
effective resolution 300 for raster images
effective resolution for vector imges 600dpi (digital printing max resolution)
thumbnail url:
used for ContentBarImages (image browser)
webp, jpeg, png for raster images
for performace use webp and lower resolution (max 256px w or h)
svg for vector images
Fonts in manifest
There are currently two places for the fonts in the template json in the fontdata part of the template json and in the manifest we are toward a solition that the none default fonts end up in the manifest only. At some point the fontdata in the template json will be removed. Font url's in the manifest should point to ttf fonts. The typograph converter pipeline (API) can/will
Fonts are in the manifest
Swatches in manifest
There are currently two places for the swatches in the template json in the swatches part of the json and in the manifest we are working toward a solution that the none default swatches end up in the manifest only. At some point the swatches in the template json together with the brandcolors will be removed.