@shbernal/ts-pptx 4.0.1 → 4.2.0

package/dist/{slide-size-BalTjFuv.js → slide-size-SkScz1ig.js}

@@ -1,4 +1,4 @@
-//#region src/ooxml/slide-size.ts
+// src/ooxml/slide-size.ts
 /**
 * The slide size a presentation has when `presentation.xml` declares none.
 *
@@ -82,7 +82,6 @@ function presentationFormatLabel(widthEmu, heightEmu) {
 function slideSizeType(widthEmu, heightEmu) {
 	return standardSlideSize(widthEmu, heightEmu)?.type;
 }
-//#endregion
 export { presentationFormatLabel as n, slideSizeType as r, ABSENT_SLIDE_SIZE_EMU as t };
 
-//# sourceMappingURL=slide-size-BalTjFuv.js.map
+//# sourceMappingURL=slide-size-SkScz1ig.js.map

package/dist/{slide-size-BalTjFuv.js.map → slide-size-SkScz1ig.js.map}

@@ -1 +1 @@
-{"version":3,"file":"slide-size-BalTjFuv.js","names":[],"sources":["../src/ooxml/slide-size.ts"],"sourcesContent":["/**\n * The slide size a presentation has when `presentation.xml` declares none.\n *\n * `p:sldSz` is optional in `CT_Presentation` (`minOccurs=\"0\"`), and the schema says nothing about\n * what its absence means: `cx` and `cy` are required only when the element is there. So the answer\n * is PowerPoint's. A deck with `p:sldSz` removed opens at 720 × 540 pt, the 10in × 7.5in on-screen\n * 4:3 size (`ppSlideSizeOnScreen`), measured over COM against a control copy that kept its\n * 960 × 540 pt declaration. That is `LAYOUT_4x3`, not the write path's `LAYOUT_16x9` default and\n * not `LAYOUT_WIDE`.\n *\n * Anything that has to name a size for such a deck takes this one. The script converter and\n * `inspect` each had their own, and they disagreed.\n */\nexport const ABSENT_SLIDE_SIZE_EMU: Readonly<{ widthEmu: number; heightEmu: number }> = Object.freeze({\n\twidthEmu: 9144000,\n\theightEmu: 6858000,\n})\n\n/** The `ST_SlideSizeType` values a written deck can carry; `custom` is the schema default. */\nexport type SlideSizeType = 'screen4x3' | 'screen16x9' | 'screen16x10'\n\n/**\n * The standard slide sizes, each with the label PowerPoint shows for it, as `docProps/app.xml`'s\n * `<PresentationFormat>` spells it, and the `p:sldSz/@type` PowerPoint writes for it.\n *\n * The labels are PowerPoint's own, read back from decks it re-saved, and three of them follow\n * `@type` rather than the dimensions: a deck re-saved from `type=\"screen16x9\"` comes back\n * `On-screen Show (16:9)`, while the same dimensions set through `PageSetup`, which writes no type,\n * come back `Custom`. `LAYOUT_WIDE`'s 13.333in × 7.5in is recognised as `Widescreen` from its\n * dimensions alone, and PowerPoint writes it with no `type` at all. Anything else is `Custom`.\n *\n * One table for both, so the label `app.xml` states and the type `presentation.xml` declares\n * cannot disagree about a deck.\n *\n * Matched on exact EMU rather than on aspect ratio: the ratio of 10in × 7.5in and of\n * 13.333in × 10in is the same, and PowerPoint labels only the first of them 4:3.\n */\nconst STANDARD_SLIDE_SIZES: ReadonlyArray<\n\tReadonly<{ cx: number; cy: number; label: string; type: SlideSizeType | undefined }>\n> = Object.freeze([\n\t{ cx: 9144000, cy: 6858000, label: 'On-screen Show (4:3)', type: 'screen4x3' },\n\t{ cx: 9144000, cy: 5143500, label: 'On-screen Show (16:9)', type: 'screen16x9' },\n\t{ cx: 9144000, cy: 5715000, label: 'On-screen Show (16:10)', type: 'screen16x10' },\n\t{ cx: 12192000, cy: 6858000, label: 'Widescreen', type: undefined },\n])\n\nfunction standardSlideSize(widthEmu: number, heightEmu: number) {\n\treturn STANDARD_SLIDE_SIZES.find(({ cx, cy }) => cx === widthEmu && cy === heightEmu)\n}\n\n/**\n * `<PresentationFormat>` for a deck of this size, or `Custom` for one that matches no standard\n * size. `app.xml` used to say `On-screen Show (16:9)` whatever the deck.\n * @param widthEmu - the deck's slide width in EMU\n * @param heightEmu - the deck's slide height in EMU\n */\nexport function presentationFormatLabel(widthEmu: number, heightEmu: number): string {\n\treturn standardSlideSize(widthEmu, heightEmu)?.label ?? 'Custom'\n}\n\n/**\n * `p:sldSz/@type` for a deck of this size, or `undefined` where PowerPoint writes none: at the\n * widescreen size, and at any size that is not standard.\n *\n * Taken from the dimensions, not from the layout's name, so a `defineLayout` at exactly\n * 10in × 5.625in is typed as the on-screen 16:9 size it is, as its `app.xml` label already says.\n * @param widthEmu - the deck's slide width in EMU\n * @param heightEmu - the deck's slide height in EMU\n */\nexport function slideSizeType(widthEmu: number, heightEmu: number): SlideSizeType | undefined {\n\treturn standardSlideSize(widthEmu, heightEmu)?.type\n}\n"],"mappings":";;;;;;;;;;;;;;AAaA,MAAa,wBAA2E,OAAO,OAAO;CACrG,UAAU;CACV,WAAW;AACZ,CAAC;;;;;;;;;;;;;;;;;AAqBD,MAAM,uBAEF,OAAO,OAAO;CACjB;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAAwB,MAAM;CAAY;CAC7E;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAAyB,MAAM;CAAa;CAC/E;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAA0B,MAAM;CAAc;CACjF;EAAE,IAAI;EAAU,IAAI;EAAS,OAAO;EAAc,MAAM,KAAA;CAAU;AACnE,CAAC;AAED,SAAS,kBAAkB,UAAkB,WAAmB;CAC/D,OAAO,qBAAqB,MAAM,EAAE,IAAI,SAAS,OAAO,YAAY,OAAO,SAAS;AACrF;;;;;;;AAQA,SAAgB,wBAAwB,UAAkB,WAA2B;CACpF,OAAO,kBAAkB,UAAU,SAAS,CAAC,EAAE,SAAS;AACzD;;;;;;;;;;AAWA,SAAgB,cAAc,UAAkB,WAA8C;CAC7F,OAAO,kBAAkB,UAAU,SAAS,CAAC,EAAE;AAChD"}
+{"version":3,"file":"slide-size-SkScz1ig.js","names":[],"sources":["../src/ooxml/slide-size.ts"],"sourcesContent":["/**\n * The slide size a presentation has when `presentation.xml` declares none.\n *\n * `p:sldSz` is optional in `CT_Presentation` (`minOccurs=\"0\"`), and the schema says nothing about\n * what its absence means: `cx` and `cy` are required only when the element is there. So the answer\n * is PowerPoint's. A deck with `p:sldSz` removed opens at 720 × 540 pt, the 10in × 7.5in on-screen\n * 4:3 size (`ppSlideSizeOnScreen`), measured over COM against a control copy that kept its\n * 960 × 540 pt declaration. That is `LAYOUT_4x3`, not the write path's `LAYOUT_16x9` default and\n * not `LAYOUT_WIDE`.\n *\n * Anything that has to name a size for such a deck takes this one. The script converter and\n * `inspect` each had their own, and they disagreed.\n */\nexport const ABSENT_SLIDE_SIZE_EMU: Readonly<{ widthEmu: number; heightEmu: number }> = Object.freeze({\n\twidthEmu: 9144000,\n\theightEmu: 6858000,\n})\n\n/** The `ST_SlideSizeType` values a written deck can carry; `custom` is the schema default. */\nexport type SlideSizeType = 'screen4x3' | 'screen16x9' | 'screen16x10'\n\n/**\n * The standard slide sizes, each with the label PowerPoint shows for it, as `docProps/app.xml`'s\n * `<PresentationFormat>` spells it, and the `p:sldSz/@type` PowerPoint writes for it.\n *\n * The labels are PowerPoint's own, read back from decks it re-saved, and three of them follow\n * `@type` rather than the dimensions: a deck re-saved from `type=\"screen16x9\"` comes back\n * `On-screen Show (16:9)`, while the same dimensions set through `PageSetup`, which writes no type,\n * come back `Custom`. `LAYOUT_WIDE`'s 13.333in × 7.5in is recognised as `Widescreen` from its\n * dimensions alone, and PowerPoint writes it with no `type` at all. Anything else is `Custom`.\n *\n * One table for both, so the label `app.xml` states and the type `presentation.xml` declares\n * cannot disagree about a deck.\n *\n * Matched on exact EMU rather than on aspect ratio: the ratio of 10in × 7.5in and of\n * 13.333in × 10in is the same, and PowerPoint labels only the first of them 4:3.\n */\nconst STANDARD_SLIDE_SIZES: ReadonlyArray<\n\tReadonly<{ cx: number; cy: number; label: string; type: SlideSizeType | undefined }>\n> = Object.freeze([\n\t{ cx: 9144000, cy: 6858000, label: 'On-screen Show (4:3)', type: 'screen4x3' },\n\t{ cx: 9144000, cy: 5143500, label: 'On-screen Show (16:9)', type: 'screen16x9' },\n\t{ cx: 9144000, cy: 5715000, label: 'On-screen Show (16:10)', type: 'screen16x10' },\n\t{ cx: 12192000, cy: 6858000, label: 'Widescreen', type: undefined },\n])\n\nfunction standardSlideSize(widthEmu: number, heightEmu: number) {\n\treturn STANDARD_SLIDE_SIZES.find(({ cx, cy }) => cx === widthEmu && cy === heightEmu)\n}\n\n/**\n * `<PresentationFormat>` for a deck of this size, or `Custom` for one that matches no standard\n * size. `app.xml` used to say `On-screen Show (16:9)` whatever the deck.\n * @param widthEmu - the deck's slide width in EMU\n * @param heightEmu - the deck's slide height in EMU\n */\nexport function presentationFormatLabel(widthEmu: number, heightEmu: number): string {\n\treturn standardSlideSize(widthEmu, heightEmu)?.label ?? 'Custom'\n}\n\n/**\n * `p:sldSz/@type` for a deck of this size, or `undefined` where PowerPoint writes none: at the\n * widescreen size, and at any size that is not standard.\n *\n * Taken from the dimensions, not from the layout's name, so a `defineLayout` at exactly\n * 10in × 5.625in is typed as the on-screen 16:9 size it is, as its `app.xml` label already says.\n * @param widthEmu - the deck's slide width in EMU\n * @param heightEmu - the deck's slide height in EMU\n */\nexport function slideSizeType(widthEmu: number, heightEmu: number): SlideSizeType | undefined {\n\treturn standardSlideSize(widthEmu, heightEmu)?.type\n}\n"],"mappings":";;;;;;;;;;;;;;AAaA,MAAa,wBAA2E,OAAO,OAAO;CACrG,UAAU;CACV,WAAW;AACZ,CAAC;;;;;;;;;;;;;;;;;AAqBD,MAAM,uBAEF,OAAO,OAAO;CACjB;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAAwB,MAAM;CAAY;CAC7E;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAAyB,MAAM;CAAa;CAC/E;EAAE,IAAI;EAAS,IAAI;EAAS,OAAO;EAA0B,MAAM;CAAc;CACjF;EAAE,IAAI;EAAU,IAAI;EAAS,OAAO;EAAc,MAAM,KAAA;CAAU;AACnE,CAAC;AAED,SAAS,kBAAkB,UAAkB,WAAmB;CAC/D,OAAO,qBAAqB,MAAM,EAAE,IAAI,SAAS,OAAO,YAAY,OAAO,SAAS;AACrF;;;;;;;AAQA,SAAgB,wBAAwB,UAAkB,WAA2B;CACpF,OAAO,kBAAkB,UAAU,SAAS,CAAC,EAAE,SAAS;AACzD;;;;;;;;;;AAWA,SAAgB,cAAc,UAAkB,WAA8C;CAC7F,OAAO,kBAAkB,UAAU,SAAS,CAAC,EAAE;AAChD"}

package/dist/{table-dom-BTDP3lEP.js → table-dom-BYga4FYY.js}

@@ -1,7 +1,7 @@
-import { t as genTableToSlides } from "./html-dom-Iuog2wdK.js";
-//#region src/families/table-dom.ts
+import { t as genTableToSlides } from "./html-dom-LZCgntnJ.js";
+// src/families/table-dom.ts
 /**
-* ts-pptx: the table family's live-DOM half
+* pptx-ts: the table family's live-DOM half
 *
 * `tableToSlides` reproduces a rendered HTML `<table>` as a PowerPoint table, resolving the element
 * id against the global `document`. It is the table family's, but it is composed separately because
@@ -15,7 +15,6 @@ const tableDomFamily = {
 		genTableToSlides(ctx.pres, eleId, options);
 	} }
 };
-//#endregion
 export { tableDomFamily as t };
 
-//# sourceMappingURL=table-dom-BTDP3lEP.js.map
+//# sourceMappingURL=table-dom-BYga4FYY.js.map

package/dist/{table-dom-BTDP3lEP.js.map → table-dom-BYga4FYY.js.map}

@@ -1 +1 @@
-{"version":3,"file":"table-dom-BTDP3lEP.js","names":[],"sources":["../src/families/table-dom.ts"],"sourcesContent":["/**\n * ts-pptx: the table family's live-DOM half\n *\n * `tableToSlides` reproduces a rendered HTML `<table>` as a PowerPoint table, resolving the element\n * id against the global `document`. It is the table family's, but it is composed separately because\n * it is the browser entry's alone: wiring it into `families/table.ts` would put `gen/table/html-dom.ts`\n * in the graph of every Node program that draws a table, and wiring it into the entry directly would\n * make it the one thing a browser tier could not drop.\n */\n\nimport { genTableToSlides } from '../gen/table/html-dom.js'\nimport type { ConstructFamily } from './shared.js'\n\nexport const tableDomFamily = {\n\tname: 'table',\n\tpresentationAuthors: {\n\t\ttableToSlides(ctx, eleId, options) {\n\t\t\t// @note `options.verbose` (a documented dev-only flag on TableToSlidesProps) is read\n\t\t\t// inside genTableToSlides to trace the auto-paging layout process.\n\t\t\tgenTableToSlides(ctx.pres, eleId, options)\n\t\t},\n\t},\n} satisfies ConstructFamily\n"],"mappings":";;;;;;;;;;;AAaA,MAAa,iBAAiB;CAC7B,MAAM;CACN,qBAAqB,EACpB,cAAc,KAAK,OAAO,SAAS;EAGlC,iBAAiB,IAAI,MAAM,OAAO,OAAO;CAC1C,EACD;AACD"}
+{"version":3,"file":"table-dom-BYga4FYY.js","names":[],"sources":["../src/families/table-dom.ts"],"sourcesContent":["/**\n * pptx-ts: the table family's live-DOM half\n *\n * `tableToSlides` reproduces a rendered HTML `<table>` as a PowerPoint table, resolving the element\n * id against the global `document`. It is the table family's, but it is composed separately because\n * it is the browser entry's alone: wiring it into `families/table.ts` would put `gen/table/html-dom.ts`\n * in the graph of every Node program that draws a table, and wiring it into the entry directly would\n * make it the one thing a browser tier could not drop.\n */\n\nimport { genTableToSlides } from '../gen/table/html-dom.js'\nimport type { ConstructFamily } from './shared.js'\n\nexport const tableDomFamily = {\n\tname: 'table',\n\tpresentationAuthors: {\n\t\ttableToSlides(ctx, eleId, options) {\n\t\t\t// @note `options.verbose` (a documented dev-only flag on TableToSlidesProps) is read\n\t\t\t// inside genTableToSlides to trace the auto-paging layout process.\n\t\t\tgenTableToSlides(ctx.pres, eleId, options)\n\t\t},\n\t},\n} satisfies ConstructFamily\n"],"mappings":";;;;;;;;;;;AAaA,MAAa,iBAAiB;CAC7B,MAAM;CACN,qBAAqB,EACpB,cAAc,KAAK,OAAO,SAAS;EAGlC,iBAAiB,IAAI,MAAM,OAAO,OAAO;CAC1C,EACD;AACD"}