Self-explanatory.
Details
Details
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Branch
- master
- Lint
Lint Passed - Unit
Tests Passed - Build Status
Buildable 8815 Build 10282: Run Core Tests Build 10281: arc lint + arc unit
Event Timeline
src/applications/config/view/PhabricatorSetupIssueView.php | ||
---|---|---|
296 | I started doing this but reverted it because the number isn't actually used: 'You can update these %s value(s) here:' => array( 'You can update this value here:', 'You can update these values here:', ), Although maybe it would be better to pass in an instance of PhutilNumber in case some translation wants to display 'You can update %s these values here:'? |
Comment Actions
OK sure.
Also, there were a bunch of strings that I couldn't change because I have no idea what this method does:
final public static function formatStatusCount( $count, $limit_string = '%s', $base_string = '%d') { if ($count == self::MAX_STATUS_ITEMS) { $count_str = pht($limit_string, ($count - 1).'+'); } else { $count_str = pht($base_string, $count); } return $count_str; }
Comment Actions
I think we have to split those out, it's just doing this (except in a junky, untranslatable way):
if ($count > 99) { return pht('You have 99+ notifications.'); } else { return pht('You have %s notification(s).', new PhutilNumber($count)); }
Comment Actions
In theory, but I'd guess some languages may want to represent "99+" in a different way than by adding "+" to the end of the number, and I think notification counts are the only place where we do that.