Guide · May 18, 2026 · 3 min read
Bilingual by Default: English and French OCR/ICR, Handwriting Included
In Canadian case files, French is not an edge case. Language detection per document, diacritics that carry meaning, handwriting recognition, and quality gates measured per language — not blended into a flattering average.
In Canadian public-sector work, bilingual processing is not a feature request. Files arrive in English and French — sometimes in the same file, occasionally in the same document — and a pipeline that handles one language well and the other badly has not solved the problem. It has solved the easier half and hidden the rest inside an average.
Detect language per document, not per file
Language detection belongs at the document and even the page level. A file may open with English correspondence, continue with a French clinical report, and close with a bilingual form. Pipelines that tag a whole file with one language mis-OCR everything downstream of the wrong guess. Detection is cheap and early; the cost of skipping it is paid in every later stage — embeddings built on garbled text, retrieval that cannot find what is plainly there, summaries that quietly skip the French evidence.
Diacritics are data
French OCR fails characteristically: accents dropped or misread, “côté” becoming “cote,” names losing the characters that make them findable. Post-processing dictionaries and language-aware correction help, but the deeper fix is treating diacritic accuracy as a measured quality dimension, not a cosmetic one. A search for a treating physician’s name that fails because the index stripped the accent is a retrieval failure with a paper trail. Names, places, and medical terms must survive OCR intact — and the golden dataset must include accented material so regressions are caught.
Handwriting is where bilingual gets hard
ICR — handwriting recognition — is the hardest stage in any language. Clinical notes, intake forms, and annotations are handwritten under time pressure, and French handwriting adds its own conventions and vocabulary. Honest engineering here means three things: handwriting is routed to models and settings specialised for it, confidence thresholds for handwritten material are set higher (more of it goes to human review), and accuracy is reported for handwriting separately. A vendor whose accuracy number blends typed and handwritten text is telling you the typed number.
Summarise in the file’s language; translate deliberately
Retrieval and summarisation must work across the corpus as it is: a query in English should find the French report, and a global summary should integrate evidence from both languages without silently favouring one. Producing the summary in the reviewer’s working language, with citations landing on the original-language source page, keeps verification honest. Translation, where it is needed, is a separate, visible step with its own quality bar — never an invisible side effect of summarisation, because a translation choice can change the meaning of a diagnosis.
Quality gates per language
The governing rule: measure everything per language. OCR error rates, classification accuracy, extraction accuracy, summary claim support — reported for English and for French, separately, against golden datasets in both languages. A blended average can hide a French pipeline that is failing the very files the institution is obliged to serve equally. Bilingual by default means bilingual in the metrics, the test data, and the review queues — or it does not mean anything.