@pretextbook/pretext-html 0.17.0 → 0.18.1

package/dist/assets.d.ts

@@ -1,15 +1,19 @@
 /**
  * Retargeting the asset URLs PreTeXt emits.
  *
- * A portable build inlines `latex-image` and `prefigure` SVGs directly into
- * the page (pretext-html.xsl, mode="svg-embedded"), so those need nothing from
- * us — they are read at transform time through the fetch shim. Everything else
- * — author-supplied images and media, sageplot, asymptote — is emitted as a
- * *runtime* URL under one of two fixed prefixes:
+ * Every asset a preview shows — author-supplied images and media, and
+ * everything `pretext generate` makes (latex-image, PreFigure, sageplot,
+ * asymptote) — is emitted as a *runtime* URL under one of two fixed prefixes:
  *
  *     <img src="external/kitten.png">
+ *     <img src="generated/latex-image/diagram.svg">
  *     <img src="generated/sageplot/plot.svg">
  *
+ * (A portable build would instead inline the latex-image and PreFigure SVGs,
+ * reading them during the transform. The preview no longer builds portable,
+ * so those images reach the host here like the rest, and nothing has to read
+ * image files while rendering. See publication.ts.)
+ *
  * Those prefixes (`$external-directory` / `$generated-directory` in
  * publisher-variables.xsl) name directories a real build populates by copying
  * files next to the output HTML. The preview has no output directory, so the

package/dist/banner.d.ts

@@ -1,8 +1,8 @@
 /**
  * Dismissible "this is a live preview" warning banner.
  *
- * The preview forces `<html><platform portable="yes"/></html>` (see
- * {@link forcePortablePublication}) and skips the asset-generation step
+ * The preview forces a few publication settings of its own (see
+ * {@link forcePreviewPublication}) and skips the asset-generation step
  * entirely, so what an author sees while editing can genuinely differ from a
  * real build — different chunking, no locally generated images, etc. The
  * banner exists to say so, once, without nagging: it renders across the top