When working with i18n keys in code (e.g., i18n.key()), the FTL-EXTRACT tool currently generates translation files with placeholder values like key = key. This makes it difficult to identify which keys have been properly translated versus those that still have placeholder values, especially when dealing with multiple translation files across different locales.
This feature request proposes adding a new command that would analyze translation files to identify untranslated keys (where the value equals the key name), report their locations, and optionally provide translation examples from other available locales. This would enable developers to quickly identify and update all placeholder translations in their projects, significantly improving the i18n workflow efficiency.