White Lotuz This is still required as some languages need to use different form of word depending on what exactly is being public. (at least in Russian, its "группа" vs "групповой"/"для группы" to be clear).

With this instance types can't be translated, they HAVE TO BE translated, and in exactly the same form as standalone group term.

Patroll kawashirov This is an interesting case I'd like to hear your thoughts on: so here "Group" as the string tied to an instance type is the same context as the notifications category because its not referring to a "group of people" directly per say but rather tying it instead to the "Group" concept/feature which is required to make that instance type. Any world instance of type "Group" is directly linked to a Group itself.

White Lotuz No, the problem there, at least in Russian, names of instance types to word "instance".

Word "group" by itself sure will have implicit meaning that it's related to the instances. But to be , word "group" (as well as other instance types) must have form of adjective, i.e. "group" - "группа", but "group instance" - "групповой инстанс". And even if we drop word "instance", word "group" still must "групповой" to be correct both grammatically and implicitly.

Also, adjectives as proper names are pretty OK in Russian (Even used in some brand names). So it should work for instance types too.

And also we decided to transliterate word "instance" as the closest literal "экземпляр" is too formal and abstract. The "instance" is uncommon word for Russian - new . To solve this, we trying to "pair" as many words and context to the "instance" to improve understanding of meaning (i.e. writing "instance of world" instead of just "instance" where it's possible), this is also related to instance types.

Another fun fact is that adjectives... "" in Russian. Ex. just "group" - "группа" is feminine, but "group" with implied "instance" - "групповой" is masculine, lol. This might be also problematic in future, if we meet other variants of phrases in UI.

This is applicable not only for "group", but for most instance types.

We can leave "group" as just proper name "группа", but that .

I goanna bring this topic in our discord channel for discuss, what we can do about it.

White Lotuz we need this separation for proper translation. we might not need to translate the instance type. but these words are found in other places in the interface and will look like a blank spot, like an unfinished translation among the translated words.

White Lotuz "Group" instance type (pl: "grupowa") is a feminine adjective in Polish, because it describes an instance, even without the accompanying word "instance", to better convey it's context. While Group (pl: "grupa") as the groups feature is a noun. These are different and thus need to be split. We want to keep the instance types translated, because how they work is complicated for users, and having it translated and be the specific word form helps it being more self-explanatory.

kawashirov like3ds Patroll Hmm I see, yeah even though in English "Group" is used in these cases more as an adjectival noun or noun itself I agree being able to have the option to translate/transliterate as an adjective form helps make it sound more natural from a grammatical standpoint for users of other languages.

The goal is helping people to easily understand what type of instance/notification/etc. they're seeing, if this is being localized to a Group (feature) and not just "any group of people" so users are not confused between a Group and Public/Friends+ types for example we should be ok to split strings for that adjectival use.