Hello! It's not planned to support this.
In fact, we should avoid the possibility to have other that Latin characters as Content-Type name (for now)
@petersg83 @alexandrebodin probably something easy to fix.

Hello! It's not planned to support this.
In fact, we should avoid the possibility to have other that Latin characters as Content-Type name (for now)
@petersg83 @alexandrebodin probably something easy to fix.

thx for answer
unstable, but worked on previous versions (last beta), maybe need to make another text field label without pluralization and regexp check, for good visualization in the sidebar post types multi-language.

@reslear i have made some investigations.
Actually issue not in cyrillic, any non-latin words will throw error.
pluralize library works well with english, but will made wrong plurals for other languages. For example Czech: kniha -> knihy, but pluralize will return knyhas, which is wrong.

I found a little workaround (but it's not ideal! you will see explanation at the end of comment):
pluralize library has addPluralRule which allows to add custom rules for pluralization.
So we can preconfigure pluralize lib:

1. edit config/functions/bootstrap.js file:

const pluralize = require('pluralize')

module.exports = () => {
  // add any rules. First argument is Regex, second is string to replace
  pluralize.addPluralRule(/я$/i, 'и')
  pluralize.addPluralRule(/мышь$/i, 'мыши')
};

UPD: methods addSingularRule, addIrregularRule, addUncountableRule can also be used here. See https://github.com/plurals/pluralize#usage for examples.

2. create collection type in content-type builder, but type in Article as display name(at this point i recommend use english, so stapi generate folders/files/rotes/etc with proper names).

3. open articles content type edit dialog and set статьи as display name. save it.

4. voila! we have properly names
   

But there is a bad thing i mentioned above: we have mis grammars in other places 😄

This method can be used for any language.

@Ashot-KR wow, good temporary solution 🎉
@lauriejim @alexandrebodin Please consider the idea of creating an additional field for the Label only for display in the admin panel

This is a very important issue: If you change "info.name" (to smth, that can't be pluralized) from the code at .json file, then you won't be able to add new fields to this content type.
Please, fix this asap.

I've tried one of the latest Strapi (3.2.3) and the issue is still there.

One of my project was on Strapi 3.0.0-beta.19. I got some free time and now want migrate for last and stable version. As code base was not large I started start from scratch, but I stuck with this problem. It would be nice to have extra field for side bar label.

Hello everyone, thanks for your feedback.
We have an RFC (Request For Comments) about the pluralization topic in general. If you want to take part in the discussion and share feedback and suggest ideas you can do it there too :)
strapi/rfcs#18