HEX
Server: Apache
System: Linux s198.coreserver.jp 5.15.0-151-generic #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025 x86_64
User: nagasaki (10062)
PHP: 7.1.33
Disabled: NONE
Upload Files
File: //usr/local/rvm/gems/ruby-3.0.2/doc/i18n-1.8.11/ri/I18n/Backend/Pluralization/pluralize-i.ri
U:RDoc::AnyMethod[iI"pluralize:ETI"+I18n::Backend::Pluralization#pluralize;TF:publico:RDoc::Markup::Document:@parts[
o:RDoc::Markup::Paragraph;	[	I"LOverwrites the Base backend translate method so that it will check the ;TI"Mtranslation meta data space (:i18n) for a locale specific pluralization ;TI"Lrule and use it to pluralize the given entry. I.e. the library expects ;TI"Dpluralization rules to be stored at I18n.t(:'i18n.plural.rule');To:RDoc::Markup::BlankLineo;
;	[	I"EPluralization rules are expected to respond to #call(count) and ;TI"Kreturn a pluralization key. Valid keys depend on the translation data ;TI"Jhash (entry) but it is generally recommended to follow CLDR's style, ;TI"Ci.e., return one of the keys :zero, :one, :few, :many, :other.;T@o;
;	[	I"IThe :zero key is always picked directly when count equals 0 AND the ;TI"Jtranslation data has the key :zero. This way translators are free to ;TI"Jeither pick a special :zero translation even for languages where the ;TI",pluralizer does not return a :zero key.;T:
@fileI"&lib/i18n/backend/pluralization.rb;T:0@omit_headings_from_table_of_contents_below000[I"(locale, entry, count);T@TI"Pluralization;TcRDoc::NormalModule00