thanks for your reply. Unfortunately I am still not happy with this even though I appreciate your solution. It is not about localizing plural forms. I just don’t what to have ugly plural namings in my code. So to stay with the simple sample provided, I don’t want to have functions named like ‘getBuchs’ (wrong!) when it should be ‘getBuecher’ (= getBooks in english) . There are so many places in code where these not correctly generated plural forms appear that it is not very pleasing to work with! So, even when I indicate not to use pluralization, functions to fetch entities are still named with a wrong plural form. If you would provide a chance to provide a dictionary file or structure (json, csv, or whatever) with the structure singular:plural, you could just fetch the proper plural form for code generation. You don’t have to worry about localization as this is not the topic in this scenario.
And another suggestion:
“Pluralize or singularize database table/view names as page names” unfortunately doesn’t tell you now whether Radzen is going to pluralize or singularize the names. You have to find it out by trial and error (chances that you are right the first time are 50/50 ;-)) You should better only mention one of these two possibilities:
- “Pluralize database table/view names as page names” or
- “Singularize database table/view names as page names”