The default language pack comes with several pages of “empty“ language strings, which have no original/English output.

So when filtering and monitoring untranslated strings (which can be added with every version) these empty strings become a little annoying, because it means there will always be “untranslated strings“, even when everything that can be translated meaningfully, is translated. And I always have to scroll past these empty strings (or use the table sorting options) to find potential new strings that can be translated.

So, my question is: what’s the best way to deal with this? I saw someone suggesting to just put spaces in there or something, but I don’t know if that is actually a good idea or if that can cause issues.

I also wonder if IPS could resolve this issue, so it wouldn’t come up to begin with. All it would take is to have two filter options instead of one. One for the “empty strings untranslated“ and one for the “non-empty strings currently untranslated“.

What is the point of having these empty strings anyways? Perhaps someone of IPS could explain this to us.

The empty strings are required for certain situations with the framework.

For example, a form field that has no title. If not added, the code will throw an error because of the missing (expected) language string, so in such cases, an empty string is added instead.

48 minutes ago, teraßyte said:

The empty strings are required for certain situations with the framework.

For example, a form field that has no title. If not added, the code will throw an error because of the missing (expected) language string, so in such cases, an empty string is added instead.

I think in this case there should be a little note next to it says something like this "used by system" or something else...

I know this might be a stretch, but why do you need so many of them and not just one default empty string which is used instead of throwing an error?

I’m still mostly curious about this:

On 5/6/2025 at 7:17 PM, opentype said:

So, my question is: what’s the best way to deal with this? I saw someone suggesting to just put spaces in there or something, but I don’t know if that is actually a good idea or if that can cause issues.

Any official word from IPS or suggestion from the people who offered language packs for years? What’s the best practice in this regard?

I plan to sell a “complete“ language pack for my local language soon, which at the moment, is not complete at all, as it comes with 5 pages of (empty) untranslated strings.

Edited May 7May 7 by opentype