snipe
commented
1 week ago but also forms doesn't match. It looks terrible and very amateurish.
You know you can open issues without being rude, right?
We re-use those language strings to prevent translators from having to re-translate what looks like the same thing over and over. As I'm sure you've noticed, we have been transitioning to using pluralized strings more often, but it's a process to update everything.
Is your feature request related to a problem? Please describe.
Don't use tags made from other tags because what works for English, doesn't work for majority of other languages. I'm focused on import at the moment, so I'll use it as example. In screenshot bellow, not only capitalization is wrong, but also forms doesn't match. It looks terrible and very amateurish.
Describe the solution you'd like
If product is multi-liungual, text strings should be language neutral and constructed in the way where it's easy to get proper sounding expression. If you can't rearrange order of words, you have a problem as translator.
Basically, it's 'view blade' titles for lists and individual items, plus strings in import forms. I would say, it's less than 50 extra strings and it wouldn't have impact on site load times and performance. Also, some strings need to have text line when there's only 1 item. For example, notification about items bellow threshold - even in English it doesn't sound or look OK.
Describe alternatives you've considered
No response
Additional context
No response