Weave Code
Typograph Bundle Laravel Package
it-blaster/typograph-bundle
Typograph Bundle integrates the Typograf typography engine into PHP projects, automatically correcting quotes, dashes, spacing, and punctuation in Russian and other texts. It cleans HTML output and delivers polished, professional-looking content with minimal setup.
The typograph bundle for Symfony based on E. Muravjev's Typograph
Frequently asked questions about Typograph Bundle
- Can I install it-blaster/typograph-bundle in a Laravel application?
- Not as a native Laravel package. It is a Symfony bundle that relies on Symfony's kernel and dependency injection container, so Composer installation in Laravel 9+ will likely conflict with PHP 8 and Symfony component versions. There is no Laravel service provider, facade, or package discovery support. Treat it as a reference implementation rather than a dependency.
- What does it-blaster/typograph-bundle actually do?
- It wraps the Typograph typography engine to automatically fix quotes, dashes, ellipses, and spacing in text. The processing is locale-aware for Russian, English, and other supported languages, and it aims to preserve HTML tags and attributes. It is Symfony wiring around the underlying engine, not a Laravel typography solution.
- Which Laravel and PHP versions does this package support?
- There is no documented Laravel support. The last release was in August 2015, and it likely targets PHP 5.x and Symfony 2.x, so Laravel 10 and 11 with PHP 8.1+ are not supported. Expect Composer resolution failures or forced downgrades if you try to add it to a modern Laravel app.
- Is the underlying Typograph engine usable without Symfony?
- The typography engine itself is PHP and can theoretically be used standalone, but this package only ships the Symfony bundle integration. For a Laravel project, evaluate the engine directly in a throwaway command or wrap it in a small service class. Do not bring the Symfony bundle into the codebase just to access the engine.
- How do I configure typography rules for Laravel if I use this package?
- The bundle's configuration is designed for Symfony bundle settings and does not map to Laravel's config publishing or service container. If you use the underlying engine directly, define options in a Laravel config file or service class and inject them where needed. There is no native Laravel configuration path for this package.
- Is it-blaster/typograph-bundle safe for production HTML typography?
- It carries high risk for production use. The package has been unmaintained since 2015, has no test suite or security patches, and may mishandle UTF-8 or malformed HTML. For a Laravel application, prefer a maintained typography library with tests and PHP 8 support.
- What are maintained alternatives for smart quotes and typography in Laravel?
- Evaluate maintained PHP options such as s9e/TextFormatter or the underlying Typograph engine used directly if it supports PHP 8.1+. A small Laravel-native service or helper wrapped behind a TypographyService interface is often safer than adopting an abandoned bundle. Choose a package with active maintenance, tests, and clear HTML-safety guarantees.
- Does it-blaster/typograph-bundle work with Laravel Blade templates?
- There is no Laravel Blade integration. You could theoretically call the underlying PHP engine from a Blade directive or service class, but the Symfony bundle itself will not register in Laravel. Test carefully how Blade escaping interacts with HTML-safe typography output before relying on it.
- How should I test typography output in a Laravel app if I use this approach?
- The bundle provides no test suite, so you must write your own tests around the engine or replacement. Cover quotes, dashes, ellipses, non-breaking spaces, locale rules, and HTML tag preservation using PHPUnit or Pest. Snapshot tests against representative content help catch silent typography regressions.
- Should I migrate from this Symfony bundle to a Laravel package?
- Do not migrate the bundle itself. If typography is a product requirement, fund a short spike to evaluate the underlying engine or a maintained alternative, then wrap it in a Laravel service provider with tests. Treat it-blaster/typograph-bundle as historical reference only and avoid the abandoned dependency risk.
Weaver
How can I help you explore Laravel packages today?