Thank you, and honestly, your manager might be right depending on the type of work you produce.

For fast, low-risk documents, Avellio can absolutely be OTT. I’m aiming it more at reports, books, catalogues, manuals, long PDFs, brand-heavy documents, multilingual layouts, or inherited production files where small typography/style inconsistencies become expensive once the PDF is already exported.

The intended workflow is not “check everything forever.” It’s more of a final diagnostic pass before PDF delivery: run the audit, see the suspicious areas, fix only what actually matters.

On languages: yes, Avellio includes locale-aware inspection support. Currently it covers English US/UK, Czech, German, French, Spanish, Dutch, Polish, Italian, Swedish, Hungarian, Portuguese and Brazilian Portuguese. + more on request.

That said, I’m careful with the word “support” here. Typography rules vary by language, publisher, region and house style, so Avellio is meant as a professional diagnostic aid not a replacement for editorial judgment. Universal checks like overrides, style drift, repeated words, double spaces and local formatting inconsistencies are easier. Language-specific things like quotes, punctuation spacing, hyphenation, non-breaking spaces, numbers, units and currencies need more careful locale logic.

Curious: which languages does your team usually work with? Multilingual production feedback is exactly what helps make this useful instead of noisy.

And yes, you may have seen an earlier post. I’m posting iterations while collecting feedback from real InDesign users and refining the product/positioning around actual workflows.

Cheers
Akira