Pseudolocalization #19630

Inspired by https://netflixtechblog.com/pseudo-localization-netflix-12fff76fbcbe and others.
I think this helps a lot during testing. Unlike the "dev" language it is not completely unreadable and one can test features with it. Untranslated text immediately sticks out and issues with non-ASCII character should be more noticable than with English text.

Expanding the text by a factor (e.g. by duplicating every chacter with an n% chance) could also be added.

This is just a rough draft to show that the idea works. Of course it should become its separate language from the existing "dev".

Review

• [ ] Functional review done
• [ ] Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• [ ] Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• [ ] Security review done
• [ ] Wording review done
• [ ] Code review done
• [ ] Tests were added if useful/possible
• [ ] Reviewed for breaking changes
• [ ] Developer changelog updated if needed
• [ ] Documentation added if needed
• [ ] Existing documentation updated if needed

If you don't want this PR to be closed automatically in 28 days then you need to assign the label 'Do not close'.

I like the idea. And we could even use it as replacement for the development language. That one is kind of useless, as it breaks most things due to missing placeholders.
Pushed a commit to avoid replacing stuff of the intl plugin, as otherwise the format strings are replaced and can be used anymore for number and date formatting...

That one is kind of useless, as it breaks most things due to missing placeholders.

That's true, but I feel like it has another very useful use case: You can very quickly find out how a translation string you see anywhere in Matomo is called. Especially for non-technical users and translators. So I would leave it as a separate thing.

I think there is just one larger issue with this code: It breaks HTML inside translation strings (which I think isn't that rare). And I can't think of a simple solution for that (I think laravel uses a full HTML parser with allowed attributes that get modified to solve the issue).

And semi-related, it would also be nice if we had a way to increase the length of strings to simulate (very often German) strings overflowing.

That's true, but I feel like it has another very useful use case: You can very quickly find out how a translation string you see anywhere in Matomo is called. Especially for non-technical users and translators. So I would leave it as a separate thing.

Even for that case it would need to be improved. The problem is, that all number formatting and date formatting won't work correctly anymore and in some places it might even cause php or javascript errors due to missing placeholders.
I actually never used it in the last years.

If you don't want this PR to be closed automatically in 28 days then you need to assign the label 'Do not close'.