Automatic Text Capture should automatically be disabled in case of parameter mismatch

Not sure what category this belongs in, going with Engine Features but feel free to move it.

I recently ran into an issue that gunked up my localization table

image
Notice the partial strings of the exact same content.

The Cause

The issue was caused by weird parameter matching.

Aftermath

This parameter issue was caused by having an old localization table that had gone through many iterations of the tooling. To my knowledge it was not user error (but that’s neither here nor there).

I have since resolved the aforementioned issue, but not after several days of the Automatic Text Capture tool going nuts. I had no idea about this issue until my localization experts let me know about weird strings in the table.

It bloated my game’s localization table to contain over 1300 junk/corrupted entries. These entries were partial strings, mismatched parameters, and many more weird abnormalities. I had to manually go through my table for many grueling hours to check over 2600 strings to see what was valid.

Without a doubt, there’s still some junk strings remaining. Without a doubt, I likely deleted some valid strings too.

Proposed Solution

If the localization tool runs into weird parameter matching, disable Automatic Text Capture and notify the user. It’ll solve much future headache.

5 Likes

Thanks for your suggestion, @cloakedyoshi . We are aware of this issue and are looking into a few different options to fix this. Ideally we want to figure out a way to help users automatically correct it when things go wrong like this. We’ll keep you posted if there’s any update on this.

4 Likes