JavaScript $t() strings are not included in generated POT files

Hello,

I believe I found the root cause of the missing translation strings in Fluent Community.

After inspecting the plugin source, it appears that many interface strings are already correctly wrapped with the Vue translation function ($t()), so they are clearly intended to be translatable.

However, a number of these $t() strings are never extracted during the build process and therefore never make it into the generated POT file. Since they are missing from the POT file, they are also missing from all PO files and cannot be translated using Loco Translate or any other standard WordPress translation tool.

This is why translation files can show 100% translated, while parts of both the frontend and backend still remain in English.

eg. showing in the screenshot

From my point of view, the issue is not related to the translation files themselves, but to the JavaScript translation extraction/build process, which appears to miss some $t() definitions when generating the POT file.

Could you please check the JavaScript i18n extraction during the build process and verify that all $t() definitions are compiled into the generated POT file?

This issue has been mentioned by users several times over the years. For communities running in languages other than English, it creates an inconsistent user experience because parts of the interface remain untranslated despite a complete language file.

Thank you very much!