Closed faf closed 3 years ago
Actually, it looks like there are no ways better then existing ones (i.e. using build tools and through po-files import) to handle untranslated strings in the client side templates. While it is possible to send untranslated string missed in location.js
bundle to the server to store it in the database and make it available for manual translation, it posess a potential dangerous security treat.
One should not trust anything coming from a client side. Malicious visitor could emulate situation with huge amount of big "untranslated" strings, flooding the database with garbage, making location.js
too big to handle in browser, and thus effictievly make system unusable. That's too risky for a convenient handle of too rare situation.
At the moment there is no way to store untranslated strings encountered in the client side templates. So the only possibility to translated them is to create and import a custom PO-file. It should be corrected.
The roots of the issue are here: #215.