- How is K2F different from Typst?
- Typst is a typesetting language that compiles to PDF (or other backends). You write Typst markup; Typst owns layout. K2F stores a semantic JSON tree (State A) and a compiled geometry lock (State C) in a ZIP. Agents edit nodes by stable id; they do not write Typst. Official viewers paint the lock and do not re-typeset.
- How is K2F different from LaTeX?
- LaTeX is a macro language a TeX engine expands into DVI/PDF. K2F’s agent-facing source is the semantic tree, not a macro language. Layout belongs to the reference engine. A `.tex` file is not a `.K2F` package, and K2F does not import TeX.
- How is K2F different from HTML?
- HTML+CSS reflows per viewport and user agent. K2F lock geometry is page-fixed, like PDF. This website’s chrome is HTML; document body pixels come from the WASM engine, not CSS flow. Do not preview a K2F tree by rendering it as HTML.
- Can I convert a PDF into K2F?
- No. `PDF_IS_NOT_A_SOURCE`. PDF export draws the published lock. Treat the PDF as a read-only rendering, not authoritative document state.
- Does K2F replace PowerPoint?
- Not in v0. Slide / infinite canvas is on the roadmap and is not shipped.