Reference

Reference pages document durable behavior: public APIs, catalog workflow semantics, and compatibility tradeoffs that should stay stable enough to build on.

If you are new to localization tooling, start with the Guide. This section is intentionally more technical and is meant for choosing APIs, checking exact behavior, or mapping existing catalog workflows to Ferrocat.

Available reference docs

• API Overview for choosing between PO core APIs, high-level catalog workflows, catalog audit reports, runtime compilation, and ICU parsing
• Gettext Task Landscape for advanced readers mapping familiar translation-catalog jobs to Ferrocat's product direction
• Ferrocat And Palamedes for the boundary between the catalog engine and the JS/TS i18n framework
• docs.rs crate docs for generated Rust API documentation