import { t as PptRecord } from "./tree-Du_LXAF0.cjs";
import { CharacterProperties, MasterStyleLevel, MasterTextStyleAtom, ParagraphProperties, RgbColor } from "./text/style.cjs";
//#region src/document/master.d.ts
/** One master's own resolved facts: its text-style cascade table and its own colour scheme. Bundled together because both are keyed off the same masterIdRef a slide's SlideAtom names — a caller resolving one always needs the other too. */
interface MasterInfo {
  readonly styles: MasterStyleTable;
  readonly colorScheme: readonly RgbColor[];
}
/** One master's own resolved text styles, keyed by TextTypeEnum member (text/atoms.ts's own TEXT_TYPE_* constants). A type absent from the map states nothing of its own; resolveCharacterProperties/resolveParagraphProperties below fall through to a sibling type in the same family (BODY/CENTER_BODY/HALF_BODY/QUARTER_BODY; TITLE/CENTER_TITLE) or leave the property undefined. */
interface MasterStyleTable {
  readonly byType: ReadonlyMap<number, readonly MasterStyleLevel[]>;
}
/** Builds one MainMasterContainer's own MasterStyleTable from its direct-child TextMasterStyleAtoms, falling back to the document-wide default (the single OTHER-typed TextMasterStyleAtom [MS-PPT] states lives in the DocumentTextInfoContainer inside Environment) for any TextTypeEnum member the master itself carries no atom for. A real master this package's own writer produces always states TITLE/BODY/NOTES explicitly (master-write.ts's own comment), so the document default is realistically only ever consulted for OTHER-typed runs or a third-party master that omits one of the three — but [MS-PPT] 2.9.35 makes it the genuine fallback of last resort for every type, not a special case for OTHER alone. */
declare function buildMasterStyleTable(masterAtoms: readonly MasterTextStyleAtom[], documentDefault: MasterTextStyleAtom | undefined): MasterStyleTable;
/** Resolves a run's own ParagraphProperties (possibly stating nothing at all, when the run's paragraph itself carries no TextPFException of its own) against the master cascade — every field the run itself states wins outright; every field it doesn't falls through to the first master level that does. indentLevel is never itself resolved from the cascade: it is the run's own stated (or default-zero) outline depth, and is what selects which master levels apply in the first place. */
declare function resolveParagraphProperties(run: ParagraphProperties | undefined, table: MasterStyleTable, textType: number, indentLevel: number): ParagraphProperties;
/** The character-property counterpart of resolveParagraphProperties — see that function's own comment for the cascade this implements. `color` resolves to whichever RunColor (literal or still-unresolved scheme reference) the cascade finds first; converting a scheme reference to an actual RgbColor is document/color-scheme.ts's own concern, deliberately kept separate since it needs the slide's colour scheme rather than anything the text-formatting cascade itself touches. */
declare function resolveCharacterProperties(run: CharacterProperties | undefined, table: MasterStyleTable, textType: number, indentLevel: number): CharacterProperties;
interface SlideAtomInfo {
  readonly masterIdRef: number;
  readonly notesIdRef: number;
}
declare function readSlideAtom(record: PptRecord): SlideAtomInfo;
//#endregion
export { readSlideAtom as a, buildMasterStyleTable as i, MasterStyleTable as n, resolveCharacterProperties as o, SlideAtomInfo as r, resolveParagraphProperties as s, MasterInfo as t };