Translate font and render target error messages - #3324
Merged
Conversation
DirectWrite's two font-file errors were missing from TranslateText entirely, so every locale reported them as its own crash group. The render target message was already translated, but only for a few locales. Adds the localized variants observed in crash reports: - font file not found: de, es, fr, it, pt, ru, tr, zh-Hans - font file access denied: fr, ru - wrong render target: es, fr, ru Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
FrayxRulez
added a commit
that referenced
this pull request
Aug 10, 2026
DirectWrite's two font-file errors were missing from TranslateText entirely, so every locale reported them as its own crash group. The render target message was already translated, but only for a few locales. Adds the localized variants observed in crash reports: - font file not found: de, es, fr, it, pt, ru, tr, zh-Hans - font file access denied: fr, ru - wrong render target: es, fr, ru Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ExceptionSerializer.TranslateTextnormalises localized OS error messages to Englishso that one underlying failure forms one crash group. Two DirectWrite font errors were
missing from the table entirely, and the render target message only covered a few
locales — so the same failure is currently reported as a separate group per language,
which both hides its true size and buries the smaller locales far down the list.
What was missing
A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable.— not in the table at all.Reported separately in de, es, fr, it, pt, ru, tr and zh-Hans.
A font file exists but could not be opened due to access denied, sharing violation, or similar error.— not in the table at all. Reported separately in fr and ru.The resource was realized on the wrong render target.— already present with it, deand tr; es, fr and ru were reaching the dashboard untranslated.
Notes
Each string was taken verbatim from a reported message rather than translated by hand,
and checked back against the source so the case labels match byte for byte — the French
and Russian ones use a typographic apostrophe (
’) while the Italian one uses a straight', so they are easy to get subtly wrong. The two English strings the new cases returnare likewise the exact messages already reported by English-locale clients, so the
existing groups absorb the translated ones instead of a new group appearing alongside.
Only messages actually observed in crash reports are included; other locales will
surface over time and can be added the same way.
This changes reporting only — no behaviour change in the app.
Verification
Not built or run — a UWP/.NET Native build is not available in the environment this was
prepared in. The edited file was checked with Roslyn (
CSharpSyntaxTree.ParseText) andparses with no syntax errors; that confirms syntax only, not type checking. The file's
UTF-8 BOM is preserved and the diff is purely additive.
🤖 Generated with Claude Code