# RichTextWeb
Reusable rich-text engine, flow documents, browser controls, document formats and Blazor components.
[](https://www.npmjs.com/package/@wieslawsoltes/richtextweb)
[](https://www.npmjs.com/package/@wieslawsoltes/richtextweb)
[](https://www.nuget.org/packages/RichTextWeb.Blazor)
[](https://www.nuget.org/packages/RichTextWeb.Blazor)
[](https://github.com/wieslawsoltes/RichTextWeb/actions/workflows/ci.yml)
[](https://github.com/wieslawsoltes/RichTextWeb/actions/workflows/blazor.yml)
## JavaScript and desktop adapters
```sh
npm install @wieslawsoltes/richtextweb
```
The [complete original guide](README.web.md) preserves JavaScript/React/MVVM usage, desktop adapters, architecture, tests, compatibility matrices and licensing. [Open the web demo](https://wieslawsoltes.github.io/RichTextWeb/).
## Rich page authoring — 0.5.0
Headers and footers now use the existing rich controls rather than plain-text forms: formatting, fields, tables, images and equations stay editable. Default, first-page and even-page stories have ribbon commands and double-click editing. The DOM-independent `DocumentStorySession` supports isolated drafts, cancel, conflict detection and a single parent undo step.
`SetPageSetup` validates margins, column count/gap, story distances, page numbering and variant flags before any mutation. WPF-style `ColumnWidth` and `IsColumnWidthFlexible` now affect measured columns; native DOCX preserves the resulting geometry. Vertical and MultiplePages views keep only viewport/overscan page containers plus the live page, instead of a placeholder per document page. The complete body is still measured; this is not full incremental typesetting virtualization.
```js
editor.Execute("SetPageSetup", {
PagePadding: { Left: 48, Top: 72, Right: 48, Bottom: 64 },
ColumnCount: 2,
ColumnGap: 24,
PageNumberStart: 7,
DifferentFirstPage: true,
DifferentOddAndEvenPages: true,
});
```
[Page-authoring APIs and supported limits](docs/PAGE-AUTHORING.md) · [PR #19](https://github.com/wieslawsoltes/RichTextWeb/pull/19). The feature candidate passed 404 unit tests and 112 Chromium groups plus native/Blazor qualification; the release adds a native DOCX column-geometry regression (405 tests). See the [verification report](docs/VERIFICATION.md) and release-commit CI for exact evidence.
## Paginated authoring and equations — 0.4.0
The recovered implementation is committed as actual source in [PR #15](https://github.com/wieslawsoltes/RichTextWeb/pull/15). [PR #16](https://github.com/wieslawsoltes/RichTextWeb/pull/16) adds structural equation editing and fixes page navigation, column-break continuation, equation draft conversion and immediate dialog reopening.
`RichTextPageEditor` supports Print Layout, Web Layout, Read Mode, Outline and Draft; single-page, two-page, vertical and multiple-page arrangements; page-width/whole-page fitting; physical page and column breaks; cached measurements; and printing of measured page ranges. The sample exposes these through the View ribbon and status bar.
`Equation` nodes retain editable LaTeX or presentation MathML and render to self-contained SVG. The reusable equation workbench includes 42 templates, token editing, fraction/root/script tools, matrix rows/columns, format conversion, alternative text and undo/redo. Insert/Edit Equation and Alt+= use the same toolbar and engine commands. Supported equations round-trip through native DOCX Office Math and export to vector PDF.
```html
```
```js
import {
registerRichTextWeb,
registerRichTextToolbar,
} from "@wieslawsoltes/richtextweb/web";
registerRichTextWeb();
registerRichTextToolbar();
const editor = document.querySelector("#document");
editor.Engine.InsertEquation(
String.raw`x=\frac{-b\pm\sqrt{b^2-4ac}}{2a}`,
"latex",
true,
);
```
See [authoring/equation APIs](docs/AUTHORING.md), [verified coverage](docs/VERIFICATION.md), and the [compatibility matrix](docs/COMPATIBILITY.md). Browser pagination is not Word-identical, finite-page layout still measures the complete document, and Word/WPF/math semantics are not exhaustive. The release candidate passed 379 unit tests and 105 Chromium groups, plus installed-package, Windows desktop and Blazor consumer checks.
## Blazor
```sh
dotnet add package RichTextWeb.Blazor --version 0.4.2
```
The .NET 8/.NET 10 RCL supports interactive WebAssembly and Server, with locally packaged native rich-text/PDF assets and worker. It includes `RichTextEditor`, `RichTextPageEditor`, read-only flow viewers, `RichTextInput` with EditForm integration, format services and `PdfEditor`. Consumers need neither npm nor a CDN; fonts are not implicitly downloaded.
```razor
@using RichTextWeb.Blazor
@code {
private string? html = "Edit this document.
";
}
```
See the [Blazor guide](blazor/README.md), [integration contract](blazor/INTEGRATION.md), [sample](blazor/sample/Demo.razor) and [release notes](blazor/RELEASE.md). Typed APIs are complemented by native object/function interop. Underlying document/pagination/PDF/collaboration compatibility limits remain unchanged; this package is not an exhaustive C# desktop-framework port.
```sh
git submodule update --init --recursive
npm ci
npm run build
node blazor/build.mjs
dotnet run --project blazor/sample/Sample.csproj
# Or: dotnet run --project blazor/server/Server.csproj
```
Source builds require the .NET 10 SDK with .NET 8 targeting support. The Server sample uses `/probe/`. CI tests actual NuGet consumers on both frameworks/hosts, including EditForm field notifications, full binding values, pagination, DOCX/PDF output, PDF search/view switching, streams, Razor callbacks and remounting.
NuGet versions are independent of npm in `blazor/Version.props`. Version-changing main merges publish after validation using `NUGET_API_KEY` (`NUGET_TOKEN`/`NUGET_KEY` aliases), verify public package payloads and create `blazor-v*` releases with symbols, samples and checksums. See [LICENSE](LICENSE), [NOTICE](NOTICE) and native compatibility documentation in the original guide.