Finding text the first extractor missed
The extractor skipped localizable strings written with single quotes. I corrected that handling so the missing text could enter the localization workflow.
Problem
The earlier extraction rules missed localizable strings written with single quotes. The tool that gathered text for translation was skipping a valid way of writing that text in the source.
Context
The catalog only contained text the extractor recognized. Its apparent completeness hid a gap in how the source files were being read.
Solution
I corrected the extraction handling and checked the newly included strings against the source, rather than treating the original catalog size as the full scope.
Verification
I checked the source and extracted the text again. I also ran a round-trip check, taking the text through the delivery format and extracting it back, to confirm that the expanded catalog matched the integrated files.
Result
The previously skipped strings were included in the localization workflow.
This case study describes a past extraction fix. It does not establish that every later build is complete or has been tested in the game.
Private parser code and game excerpts are not reproduced here.