Ruby runtime methods for CLDR plural rules (see camertron/cldr-plurals).

Spanish Pluralizer is a gem for converting singular spanish nouns into plural. It works by adding the following methods to String: [:pluralize_spanish, :spanish_pluralizer_acute, :spanish_pluralizer_unacute, :spanish_pluralizer_is_acute?]. It can handle diphthong, hiatus and adding or removing acutes, but fails with monosyllables and rule exceptions like "régimen" => "regímenes" and "espécimen" => "especímenes".

A gem for basic English pluralization rules: Pluralizer.pluralize("scarf") => "scarves"

Rich-pluralization is a module of E9s (http://github.com/archan937/e9s) which provides localized pluralization in combination with i18n. Doing this enables you to only translate words in singular form as the module pluralizes the translation for you.

Ruby implementation of the ICU (International Components for Unicode) that uses the Common Locale Data Repository to format dates, plurals, and more.

Pluralize is a Liquid filter to make it easy to form correct plurals.

Pluralizr is a gem that takes a single word and returns the pluralized version of that word. It takes into account various rules including words that end with the letter 'y'—where 'y' is preceded by a vowel or consonant—and words of French, Greek and Latin origins.

A client for the PluralKit REST API

A gem to pluralize words.

Tokenizes and parses CLDR plural rules and provides a mechanism for emitting them as source code

A simple gem that extends the String class to allow pluralization of Portuguese nouns

To house and share a global rubocop configuration. Includes a default and strict default option

Javascript runtime methods for CLDR plural rules (see camertron/cldr-plurals).

Better pluralization for non-english languages

A gem to pluralize wordz with a z.

Pluralize sentences based on the number of objects

Add the missing :no_count_if_one option to the Rails pluralize helper

Diggr is a ruby wrapper for the Digg API. Diggr strives to remain consistent with the Digg API endpoints listed here: http://apidoc.digg.com/CompleteList. Endpoints are created in Diggr with method calls. Each node in an endpoint becomes a method call and each node which is an argument becomes an argument to the previous method. As an example, the following endpoint /user/{user name} in which the user name is "johndoe" would be created with this Diggr call: diggr.user("johndoe") To send the request to the Digg API and retrieve the results of the call, Diggr requests are terminated in one of two ways. 1. Using the fetch method. By ending your request with the fetch method, your result will be returned to you. If the request is singular, you will receive a single object as a response. If the request is plural, you will receive a collection of objects stored in an array. 2. Using any Enumerable method. This works only on plural requests. In this case, it is unnecessary to use the fetch method. See the synopsis for examples of each of these types of calls. Options such as count or offset can be set using the options method and providing a hash of arguments. See synopsis for more information. Note: In an effort to remain consistent with the Digg API, some method names do not follow the ruby idiom of underscores. Although somewhat ugly, this allows a user to read the Digg API and understand the exact methods to call in Diggr to achieve their desired results.

Convert Android plural XML resource file to iOS stringsdict file.

pluralize liquid filter for Jekyll