from https://bugzilla.mozilla.org/show_bug.cgi?id=390614#c53: finduri-AgeInDays-is=%S days ago finduri-AgeInDays-last-is=Last %S days finduri-AgeInDays-isgreater=Older than %S days finduri-AgeInMonths-isgreater=Older than %S months Are there any reasons that these strings don't use plural forms ( https://developer.mozilla.org/En/Localization_and_Plurals )? Without plural forms it's hard to translate them properly.
FWIW, some of these strings also present in http://mxr.mozilla.org/mozilla-central/source/toolkit/locales/en-US/chrome/global/history/history.properties finduri-AgeInDays-is=%S days ago finduri-AgeInDays-isgreater=Older than %S days They should use plural forms too. Should I file separate bug or it's fine to fix them here?
(In reply to comment #1) > FWIW, some of these strings also present in > http://mxr.mozilla.org/mozilla-central/source/toolkit/locales/en-US/chrome/global/history/history.properties mxr teels me that file is completely unused, in such a case it should be removed
and the strings in comment 0 are always intended to be plural, we can fix them for consistency though, but they won't be used with 0,1.
ok, due to the complex nature of plural forms in some locale we need a way to use plural forms in cpp. history.properties should be removed as well, but that's going in a new bug, Alexander could you file a new bug for removing the unused file please?
(In reply to comment #5) > ok, due to the complex nature of plural forms in some locale we need a way to > use plural forms in cpp. So this bug depends on Bug 477831, right? > history.properties should be removed as well, but that's going in a new bug, > Alexander could you file a new bug for removing the unused file please? Filed Bug 484838
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 3 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.