Create GrammaticalCase, GrammaticalGender and GrammaticalNumber as first class citizens about humanizer

[MehdiK]

@hazzik - could you please explain what you mean by this?

[hazzik]

Sorry for long being quiet a long time. I'll try to explain.

The idea was to bring that grammatical categories to the library to simplify localisation, Internationalisation and globalisation easier to languages with that categories.

As first example we could make a common mechanism to identify grammatical number category, and based on this rule select a correct resource key.

For English: 1 => singular; 2 => dual; 3 => plural, etc
For Russian: 1 => singular; 2,3,4=>paucal; 5 => plural.

Later I plan to implement localisation for Russian using that approach.

[mexx]

From what I saw by now I think that GrammaticalNumber should be a local concept of each language specific formatter, as different languages do have different cases for it and it only depends on the number being formatted. So I would not introduce it as public concept of the API.

Even if the cases of GrammaticalCase and GrammaticalGender also differ from language to language, these concepts need to be public to control the output of ToWords and ToOrdinalWords as parameters to this methods.

[mexx]

As mentioned in my previous comment I added GrammaticalCase and GrammaticalGender in #147.
GrammaticalGender is currently not used, but I'll be using it when implementing ToOrdinalWords in russian translation.

[thunsaker]

Awesome! I'll be integrating these into my #188 Spanish ordinal translation as well.

[MehdiK]

I think it's safe to close this now that #147 is in. You agree guys?!

[mexx]

👍 from me.

[MehdiK]

@mexx so how is the GrammaticalNumber going to fit into this (for ordinal localisations)?

[mexx]

For ordinal localisations only case and gender is needed. Grammatical number is determined by the number being formatted.

[MehdiK]

Thanks for the response. Closing this. This was a burden I had NO idea about and I'm glad it's sorted. Thanks a lot.