Last modified: 2014-02-12 23:35:33 UTC
Gerrit change #43982 is using an arrow because JS doesn't offer the Language::getArrow feature. For consistency, this feature should also be available in JS.
(In reply to comment #0) > Gerrit change #43982 is using an arrow because JS doesn't offer the > Language::getArrow > feature. For consistency, this feature should also be available in JS. The case of that change doesn't seem entirely appropiate. In core we also embed it in the message, looking for ← I find: 'backlinksubtitle' => '← $1' 'previousrevision' => '← Older revision', 'nextrevision' => 'Newer revision →', 'whatlinkshere-links' => '← links', 'previousdiff' => '← Older edit', 'nextdiff' => 'Newer edit →', 'imgmultipageprev' => '← previous page', 'imgmultipagenext' => 'next page →', Maybe we should implement this as a message, like we have 'ellipsis', 'parentheses', 'brackets', 'comma-separator' etc. Otherwise it is hard to use. Just prepending it can be confusing (I think you previously discouraged concatenating strings like that). If it is used in the interface, it is already taken care of by cssjanus (e.g. margin-left, padding-right).
